Show live tool progress in the channel
iamnbutler opened ·
Pi emits live tool execution updates, but Ace's channel projection currently forwards message deltas/run state and completed tool results. A running build can therefore be opaque. Completed diagnostics and full-output spill paths already survive in tool text.
## Acceptance
- Project live tool progress through the shared protocol and show it against the correct tool call. - Bound retained output without hiding truncation, full-log references, or exit/error state. - Reconnecting and reopening must reconcile live state with the durable completed result without duplicate output. - With a real long-running build, see progress before completion, inspect a truncated result's full log, and reopen its final result.
Use existing pi events/history; do not add another tool-output store. Managed interactive/background process control is tracked in #53.
Dogfooding core/QOL: #5. [Review evidence](https://github.com/githubnext/ace2/issues/5#issuecomment-5986485157).
iamnbutlerreferenced this in Manage background and interactive jobs from channel tools #53last month on GitHub
iamnbutlerparent-issue-addedlast month on GitHub
iamnbutlerreferenced this in [Meta] Dogfood Ace end to end #5last month on GitHub
iamnbutlerreferenced this in [Meta] Help participants follow and understand agent work #98last month on GitHub
iamnbutlerreferenced this in Show a live, plain-language account of agent progress, outcomes, and blockers #99last month on GitHub
- IA
#99 builds a participant-facing, plain-language account of runs on top of this live progress (meta: #98).
iamnbutlerreferenced this in Show mixed or multi-file diff tool output as text instead of a blank "Invalid or empty patch" block #102last month on GitHub
- IA
Related rendering failure for completed tool results: #102.