Per-Agent Review

  • Desktop app
  • All plans

What it does

When several agents work on the same project at once, AgentsRoom records which agent touched which file and lets you review and commit one agent at a time. The Changes tab and Review Mode gain a filter: All shows the full git diff, one tab per agent (avatar, name, file count) narrows the list to that agent's files, and the commit action then stages only those files. A file touched by two or more agents shows their avatars on its row in the Changes tab (hover for their names) and appears under each of their tabs. Switching to an agent's terminal auto-selects its filter (and, for an agent in its own git worktree, that worktree), so the panel follows the agent you are looking at. This can be turned off. The file list is shown as a tree by folder by default, and can be switched back to a flat list.

Where to find it

  • Right panel > Changes tab: the Filter by agent row above the file list (All, then one entry per agent; a Team entry when a team run is involved). Since 2026-10-28 All sits outside the scrolling strip, so it stays visible however many agents there are, and the two arrows sit beside the strip instead of floating over it: they stay on screen while the strip overflows and grey out at the end they reached.
  • Review Mode: the same tabs at the top of the file list, All files first.
  • The filter row can be hidden or restored in Settings > Interface elements > Right panel > Filter by agent.
  • Changes tab > View options (the sliders button next to Refresh): Flat list or Tree by folder, and Follow the selected agent. The same two choices are in Settings > Git > Changes tab.

How to use it

  1. Let the agents work; attribution is recorded as they edit.
  2. Open Changes and click an agent's tab: the file list, the diff and the progress bar shrink to that agent's files.
  3. Review the files (Review Mode works on the filtered set), then commit from the filtered view: only those files are staged, with their own message.
  4. Repeat for the next agent, or go back to All and commit everything together.

Right-click an agent's tab for Clear attribution for this agent when the record is stale.

Non-code changes (libraries, backlog, Idea Radar, commands, connections, settings…)

The Changes tab has two sections, Code changes and Non-code changes. They scroll as one list and both headers stay visible: Code changes at the top, Non-code changes just above the commit box until you scroll to it, so a long file list never hides it. Click a header to jump to its section. Each section has its own search behind the magnifier of its header: it only filters what you see, never what a commit or a review takes.

Agents also change things outside the code: a skill, a prompt, a memory note, a trigger, a ticket, an idea, a dev command, a connection, a setting. Those changes are saved on the server, so git never sees them. The Non-code changes section lists them, newest first.

Review changes walks the changed files first, then the non-code changes. A review with no file offers no commit: non-code changes are already saved.

A commit only ever contains files, but it takes the non-code changes along in its own way: their list goes in the body of the commit message (20 lines at most), and once the commit went through they leave the section and the tab's count, like the files it took. + 9 non-code next to Will commit says so before you commit; since 2026-11-12 a click on it opens the Commit message preview: your message, then the list it will add, updated as you type. Nothing is deleted: the entry's version history and the agent's journal keep them. The list follows the tab you commit from: on an agent's tab, only that agent's changes. Auto-commit and the phone's commit do the same for their agent, when this desktop has already read that project's changes. A commit message is shared with whoever reads the repository, so these names (a ticket title, a note name) become public in a public repository.

In the panel, the checkbox next to the count of the Code changes header selects every file, and Fetch, Pull, Merge and Push are icons next to the branch name (see Manual Git Actions).

A diff taller than its area shows a thin column of marks next to the scrollbar: green for added lines, red for removed lines, half red and half green for a rewritten block. Click a mark to go to that change. It appears in the Changes tab, the diff of a file preview or a commit, Review Mode, the Worktrees full diff and the non-code diffs. A library entry also opens on its first change.

Library entries (prompts, skills, memory notes, triggers, a ticket's text) come with a real diff:

  • One row per changed entry, read like a changed file: the kind (prompt, skill, memory note, trigger, ticket), its name (green when it was created, amber when it was modified) and the lines removed and added. As for files, the agent is not repeated on each row: the tab you picked says whose changes these are. An entry an agent created has no previous version to restore: its rollback is deleting it.
  • Hover a row and click the arrow icon (or Open in the Skills library, Open the ticket… in the diff) to open the entry itself in its library, its trigger or its board.
  • Under All: every change of the last 24 hours (the project's entries, your account library, the project's shared memory, the tickets of its board). Under an agent's tab: only that agent's changes since its console started. The tab then shows two figures, each behind the icon of its section: 31 next to the file icon (files), 2 next to the cubes icon (non-code changes).
  • Click a row to see the diff, like a code diff (red lines removed, green lines added); ← and → move to the next entry.
  • Roll back from the bottom of that diff: Restore the previous version for an entry that was modified, Delete this entry for one these changes created (no earlier version exists, and a deletion cannot be undone). An entry an agent or you deleted stays listed, struck through, with Restore this entry: it comes back as a new entry with its content, but not its folder, or a ticket's comments, status and number. The last 7 days at most; emptying a whole library is not covered.
  • An agent action shows Undo this action when a safe inverse exists: a moved ticket goes back, a setting returns to its value, a created ticket or todo is removed. The confirmation shows exactly what will run. What was already sent (a notification, a comment) or has no safe inverse (a merged idea, a team run) says it cannot be undone, as do actions from before this version.
  • A changed file has Discard changes under its diff and in Review changes, as well as in its … menu. It cannot be undone: git keeps no copy of uncommitted work.
  • On a project that is not a git repository, the Changes tab appears only when agents changed something in AgentsRoom, and shows only this section (last 24 hours, no agent filter). Nothing about git is shown.
  • Restore the previous version brings the entry back to its state before these changes, after a confirmation. Nothing is lost: the current state stays in the entry's history (its History button), and the restore itself shows up in the list, so you can undo it.
  • There is no checkbox: these changes are already saved and are not part of a commit.

Everything else an agent does in AgentsRoom through its tools is listed too, as an action: a ticket created, moved, commented or deleted, an idea created, merged, parked or rejected, a dev command created or started, an SSH / database / Kubernetes connection saved, an email inbox configured, a push notification sent, a setting changed, a team, an agent, a toolkit, a note or a todo saved. Click one to see what the agent sent (the new values; passwords, tokens and keys are masked) and, for a ticket or a library entry, open it. Commands run on your servers, SQL queries and kubectl calls stay in the Activity tab.

In an agent's conversation, next to "N files changed in this turn", a chip Changed <name> or N library entries changed opens the same diff for what the agent wrote during that turn.

Settings

  • uiElements.rightPanel.agentFilter (global, Settings > Interface elements): show or hide the filter row.
  • changesListView (account, Changes > View options or Settings > Git > Changes tab, desktop and phone): tree (default since v1.213.0, grouped by folder, single-child folders merged into one row like src/components, a file count per folder, a click on a folder folds it, its checkbox includes or excludes every file under it; a search unfolds every folder) or flat (one row per full path, the layout before v1.213.0). Synced to the account, so the phone and every computer show the same layout.
  • changesFollowAgent (account, same two places, label Follow the selected agent): on by default. Off, switching to an agent's terminal no longer changes the filter or the worktree of the Changes tab: it stays on what you picked (for example All on Main) until you click another filter or pick another worktree. Clicking an agent's filter keeps the worktree you picked, and picking a worktree keeps the agent's filter, so you can review one agent's changes in any worktree. On, an agent working in its own worktree still opens that worktree when you click its filter. On the phone, opening Changes from an agent's console then starts on All instead of that agent.

Agent tools (MCP)

None. Attribution is recorded automatically from the agents' file tools and command history.

Providers

Attribution uses two sources: a hook on the CLI's file-editing tools that records each file as it is written, and, for files written by shell commands, the timing of each agent's commands matched against file modification times. The agent tabs are offered for Claude Code, Codex, OpenCode, Grok Build, Cursor and oh-my-pi. Coverage differs: Claude Code, Codex and oh-my-pi get both sources, while OpenCode, Grok Build and Cursor report the files their editing tools write and leave shell-written files under All. For oh-my-pi, AgentsRoom loads a small extension of its own when it launches the agent (your own omp extensions keep loading), and the shell timing covers its bash and eval tools. For Claude Code 2.1.287 or newer, AgentsRoom also loads a small plugin of its own (--plugin-dir, your own plugins keep loading) that compares git status right before and right after each shell command: the agent is credited with exactly the files that command changed, deleted files included, and a read-only command (ls, grep, cat) never counts. Older Claude Code builds keep the timing method. For every other provider the panel shows the strip Per-agent file changes are not supported for ... yet with Use All to review the full git diff. and a Request button; selecting that agent's tab shows File attribution is not supported for <provider> with Show All changes and Request support. The provider is named as the app names it, so the message reads "Claude" and "Grok". The full diff is always reviewable under All.

Mobile

The phone has the same filter on its Changes screen. Open it from the project header for the whole working tree, or from an agent's console to start on that agent: the chips are All (with the total) and one per agent that has files, and the agent you came from keeps its chip even at 0. When that agent has no attributed file but git still sees changes, the list says "<agent> hasn't touched any file yet" and Show all files switches to All. The phone commits the ticked files (everything listed is ticked by default) and can push the result.

Attribution is computed on the computer: files written through a shell command, and everything a Codex agent writes, are attributed by a scan that only runs while the desktop's Changes tab is open. Until then an agent's chip can list fewer files than All on the phone.

A file written by two or more agents shows their avatars on its row, as on the desktop (a screen reader reads their names).

Long diffs on the phone have the same column of marks: tap anywhere on the strip to go to the nearest change. Library diffs are not on the phone.

The two icons at the top of the phone's Changes screen switch between the flat list and the tree by folder, the same account preference as the desktop. With Follow the selected agent off (set on a computer), opening Changes from an agent's console starts on All.

Limits

  • Actions show the new values the agent sent, not a before/after (only library entries have a real diff). Only agents' actions are listed: your own clicks in the app are not (except library entries). An agent console started before the update must be restarted to report its actions.

  • Library changes: the last 24 hours under All, up to 7 days for a long-running agent; a deleted entry is not listed (deletions are not captured); entries shared with a team (team:) have no history. The diff of a skill compares its SKILL.md body, not its bundled files. Desktop only for now: the phone's Changes screen does not list library changes.

  • Agent tabs appear only once two or more agents have attributed files.

  • A file written by a shell command is attributed only when a single agent can have written it: when two agents' commands ran while it changed, it stays under All. Before Claude Code 2.1.287, and for Codex and oh-my-pi, this is decided by timing, and a deleted file cannot be attributed. OpenCode, Grok Build and Cursor have no timing source: what they write through a shell stays under All. On oh-my-pi, a conversation switched with /new inside the CLI is no longer followed for shell timing until the agent is relaunched.

  • Grok Build only reports its writes in a git repository it has been trusted in, which is what AgentsRoom does when it launches the agent.

  • Cursor reports its writes through the same Claude Code hook file, which its CLI imports by default (Cursor Settings, Agents, Third-Party Imports); a user who switched that import off gets an agent tab that stays at 0.

  • Attribution is local to this machine and to the current working tree; it does not travel with the repository.

  • Committing from a filtered view stages only the filtered files: a shared file has to be committed with one agent or with All.

Common questions

  • What is the number on the Changes tab? Since 2026-11-05, the number of changed code files listed under All (nothing at zero, "99+" beyond). Prompts, skills and memory notes are not counted. While another tab is open it refreshes every 15 seconds, only while the window is visible. On the phone, the project's … menu shows the same kind of number on its Changes and Documents rows, read each time you open the menu.

  • A diff is very long. How do I find where the changes are? Use the colored marks next to the scrollbar: each one is a change, and a click takes you there. They only appear when the diff does not fit on screen.

  • I committed from a terminal and the non-code changes stayed listed. Fixed on 2026-11-02: once the project's working tree is clean, everything older than the last commit leaves the section, for all agents. The commit message stays as you wrote it, so these changes are not listed in it. A commit made in an agent's worktree does not trigger this.

  • An agent's tab said it had not touched any file, although it had. Fixed on 2026-11-02: when several agents ran commands at the same moment, a file written from the shell could be claimed by all of them and then went to none. The agent whose command names the file now gets it. If two of them name it, or a colleague's command is still running, the file stays under All only.

  • An agent changed my skill / my memory note / my ticket description. Where do I see what it changed? Changes tab, Non-code changes section under the files (or the chip under the agent's answer in the conversation). Click the row for the diff, and Restore the previous version if you want the old text back.

  • Why does an agent's tab show two numbers? The file icon counts the files changed, the cubes icon the non-code changes (library entries and agent actions).

  • Can I see everything an agent did in AgentsRoom, not only in the code? Yes: the Non-code changes section of the Changes tab (called AgentsRoom before), on that agent's tab, lists its library changes and every other change it made through its tools (backlog, Idea Radar, commands, connections, settings, notifications…), kept 30 days.

  • A library change is missing from an agent's tab. Only changes saved after the app update that added the section carry the agent that made them. Older ones are still in each entry's History. A change made on another computer is listed under All, not under the tab of an agent running here.

  • How does it know which agent changed a file? The agent's file tools report each write through a hook. For shell-written files, Claude Code agents report what each command changed (git status before and after it); other agents are matched by the time they ran their commands.

  • Two agents changed the same file. Its row shows both avatars and it is listed under both tabs; pick which commit gets it, or commit it with All. Hover an avatar to read the agent's name; since 2026-10-06 a click on it opens that agent directly (desktop).

  • Can I still commit everything at once? Yes, select All and commit.

  • The list of changes jumps every time I switch agents. Turn off Follow the selected agent in Changes > View options (or Settings > Git > Changes tab): the filter and the worktree stay where you put them.

  • Can I see the changed files grouped by folder, like VS Code? Yes, it is the default: each folder shows how many changed files it holds and can be folded.

  • I want the old flat list of paths back. Changes > View options > Flat list (or Settings > Git > Changes tab).

  • My project is a subfolder of a bigger git repository (a monorepo package) and commit or diffs failed. Fixed on 2026-10-18: the Changes tab now finds the repository above the project folder, and the diffs and the commit work from there.

  • The Changes tab says "Could not read the repository". Since 2026-10-18 the tab says so when git does not answer, instead of showing "Working tree clean" while files are changed. Check that git is installed and that the folder is a readable git repository, then click Refresh.

  • The banner says attribution is unsupported. That provider does not expose file-tool hooks yet; review under All, and click Request support to vote for it.