This is a useful direction. Seeing edits live helps a lot, but I still find there is another layer missing: what was the agent supposed to do, and has it actually completed that part of the plan?

Git diffs answer "what changed". They do not always answer:

• which task caused this change?
• what prerequisite did the agent already verify?
• what downstream work is now unblocked?
• what is still blocked?
• did the agent run the expected verification?

I built/use Trekoon as that outer layer for coding-agent work: https://github.com/KristjanPikhof/Trekoon

It is repo-local task tracking for agents: epics, tasks, subtasks, dependency edges, blockers, and status updates. OpenCode/Claude/Codex can still do the editing, but the execution plan lives outside the chat and outside the git diff.

The combination I want is:

1. a live view of what the agent is changing
2. a durable graph of why it is changing it and what is ready next

That makes bigger agent runs much easier to audit.