The gap
Owner feedback (instance bd43f4de, 2026-08-15): there is no real-time, per-step observability into a running coding/agent loop from an external MCP client. While a run is in flight the only signal is coding_loop_status (status, iteration, lastProgressAt, and — once finished — a one-line detail). There is no way to see what the agent is actually doing mid-run: no per-iteration tool calls with their inputs/outputs, no reasoning, no partial output, no streaming progress. instance_activity records chat-session events only and shows nothing from loop runs, so during a run the instance looks idle even though work is happening.
Why it matters
When a run stalls or fails, the owner cannot tell whether it is mid-way through a legitimate long step, silently stuck, or doing something it was told not to do. In one case the only evidence of destructive behaviour was the phrase Acts: deleted files recursively in the post-hoc summary, with no way to see which files or why while it was happening.
Ask
Expose a live, per-step trace of a loop run to the owner — each iteration's tool calls with arguments and results, plus streaming/incremental output — through the same MCP surface that starts the run, queryable while the run is still in flight. agent_trace already does this for chat turns (chat.in/tool.call/chat.out); loop runs need the equivalent, not just a terminal detail after the fact.
Not a duplicate of
Filed from owner feedback fd60c895-bc18-4ee3-b4f1-de9b351ad4f7.
The gap
Owner feedback (instance
bd43f4de, 2026-08-15): there is no real-time, per-step observability into a running coding/agent loop from an external MCP client. While a run is in flight the only signal iscoding_loop_status(status, iteration,lastProgressAt, and — once finished — a one-linedetail). There is no way to see what the agent is actually doing mid-run: no per-iteration tool calls with their inputs/outputs, no reasoning, no partial output, no streaming progress.instance_activityrecords chat-session events only and shows nothing from loop runs, so during a run the instance looks idle even though work is happening.Why it matters
When a run stalls or fails, the owner cannot tell whether it is mid-way through a legitimate long step, silently stuck, or doing something it was told not to do. In one case the only evidence of destructive behaviour was the phrase
Acts: deleted files recursivelyin the post-hoc summary, with no way to see which files or why while it was happening.Ask
Expose a live, per-step trace of a loop run to the owner — each iteration's tool calls with arguments and results, plus streaming/incremental output — through the same MCP surface that starts the run, queryable while the run is still in flight.
agent_tracealready does this for chat turns (chat.in/tool.call/chat.out); loop runs need the equivalent, not just a terminaldetailafter the fact.Not a duplicate of
coding_timelineper-step token/cost/files summary) — post-hoc timeline, not a live in-flight feed.Filed from owner feedback
fd60c895-bc18-4ee3-b4f1-de9b351ad4f7.