When five agents modify fifty files, reviewing everything at once is overwhelming. AgentsRoom tracks which agent changed which files. Filter by agent, review their work in isolation, and commit each contribution separately.
Real captures of the app, added as this feature evolves.
A real session filmed in the app: three AI coding agents, two on Claude Code and one on Codex, each change one file of the same project. The Changes list gives each agent its own tab, and a commit takes only that agent's files: three agents, three commits in the history.
Each agent's diff, file by file, with your comments on a line sent straight back to the agent.

Every tool you need to review multi-agent code changes without losing track of who did what.
When two or more agents have modified files, tabs appear at the top of the review panel. Each tab shows the agent's avatar, name, and file count. Click a tab to see only that agent's changes.
AgentsRoom attributes files two ways. A hook fires on every Edit, Write and NotebookEdit call and records the file as the agent writes it. For files written by a shell command, AgentsRoom knows when each agent ran its commands and matches that against the file's modification time.
When an agent filter is active, the commit action only stages that agent's files. Each agent's work gets its own commit with a clear message. Your git history stays organized by contributor, even when agents work in parallel.
Navigate through the filtered file list with arrow keys or j/k shortcuts. The progress bar updates to reflect only the files in the current filter. Mark files as reviewed one by one until the filtered set is complete.
Switch to an agent's terminal and the file list auto-filters to show that agent's recent changes. No need to manually select the filter. Override at any time by clicking a different tab, or turn auto-follow off in View options to keep the filter and worktree you picked.
A file written by one agent is already named by its filter tab. When two or more agents modified the same file, its row shows all their avatars side by side. Hover an avatar to see the agent's name, click it to jump straight to that agent.
Agents also change what git never sees: a prompt, a skill, a memory note, a trigger, a ticket. The Non-code changes section under the files lists them, each with a line diff and Restore the previous version. Once you have read them, Clear the list empties the section without a commit, and nothing is undone.
Four steps from multi-agent chaos to an organized git history.
Multiple Claude Code agents run simultaneously on your project. Each agent focuses on its assigned task and modifies the files it needs.
As each agent works, AgentsRoom records which files it touches, whether the agent used a file tool or wrote through a shell command.
Open review mode and click an agent's tab. The file list narrows to show only that agent's modifications. Review their diffs, ask questions about specific changes, and mark files as reviewed.
Once you have reviewed an agent's files, commit only their changes. The commit stages just those files. Repeat for each agent to build a clean, well-attributed git history, then click Create PR: the AI proposes the pull request's title and description from the branch diff, and you edit them before anything is sent.


Your agents write better code than half the pull requests you used to merge. So do you still read every line? The honest case for both sides, the 10 signals that tell you an agent messed up, and how much review each change actually deserves.
Anthropic now watermarks Claude's output. What it really marks, why generated code mostly escapes it, who can actually detect it, and why your SEO does not change.
A mod is a plugin whose JavaScript runs inside Claude Code. What it can do, the three files, how to load and test one, and the mod we ship in every agent.
Download AgentsRoom and see exactly what each AI agent changed in your codebase. Free for up to 2 projects.
Companion app: monitor your agents on the go
Bring your own: Claude, Codex, Antigravity CLI, or other AI provider.
Push bugs and requests straight to your public backlog.