How can I follow what my coding agents are doing in their worktrees?

When you run several coding agents on one repository, each usually works in its own git worktree. By the time they open a pull request you've lost the thread. DiffGuardian's Worktrees page lets you follow them while they work: every worktree with something in progress, what it has changed so far, and what that change touches, without waiting for a pull request or reading the diff line by line.

#What you get

1. Every agent's work in one list. Each worktree of your project that has commits ahead of its base or uncommitted changes appears as a row: the branch, how many files, the lines added and removed, and whether the work is committed, uncommitted or both. A worktree with nothing in progress isn't listed.
2. It follows along. While the page is open and the window is visible, DiffGuardian re-reads git every few seconds, so the counts move as the agent edits. It's local git only. Nothing is sent anywhere to do this.
3. The change, explained. Open a worktree and you get the same view you get for a pull request: the diff, split into the features it's shipping, with a summary of each.
4. Questions out loud. Ask what the agent is doing, what a function it just added calls, or whether a change is safe to keep, in text or by voice, and follow the answer on the code. Voice needs Pro.
5. The blast radius, as it grows. The dependency graph is drawn from the worktree's diff, with callers and implicit links added from your checkout. Open it to see what the agent's change reaches before the agent is finished. The open diff refreshes every few seconds, so the picture follows the work.

#Why this helps

You're not reading the agent's output as it scrolls past, and you're not waiting for a finished pull request to find out it went somewhere you didn't want. Glance at the Worktrees page, see which agent is touching a lot, open it, and ask. If a change is heading the wrong way you can tell the agent now, while it's cheap to redirect.

It also pairs with the plan the agent started from. If the project has the experimental Plans tab on, you can read the plan as a summary and diagrams first (understand an agent's plan), then watch the worktree to see whether the work matches it.

#Works alongside your agents and your review tools

DiffGuardian doesn't run, start or stop your agents, and it doesn't post comments on anything. Your agents write the code, and tools like CodeRabbit, GitHub Copilot and Greptile look at the pull request that comes later. DiffGuardian is for the part in between: understanding what's being written, quickly.

#Limits

• It lists local git worktrees of a project you've added with a local checkout. A project with no local path has no worktrees to show.
• The list refreshes only while the page is open and the window is visible.
• The blast radius graph is a heuristic, not an AI judgment of impact. See see what a pull request affects.
• Explanations and answers need an AI provider: your own key for Anthropic, OpenAI, Google Gemini or OpenRouter, or a local model.
• Voice answers need Pro.