Skip to content
Agent Fleet

See what a session changed

See the files a session actually touched as a list, and go straight to one. At review time it answers “what did this do to my working copy?” without reading the whole conversation back.

How it works

Section titled “How it works”
What you do What the agent does
Open the “Changed files” strip and open a file Edits files as usual. The list is built from the conversation and the repository together

It shows what actually happened, not what the agent said it would do.

Open the list

Section titled “Open the list”
How What happens
The “Changed files” strip under the conversation header Its heading folds it open or closed. The choice is remembered per session
Ctrl+P (⌘P on macOS), then Tab to “Changed files” The same list, searchable
  • With the strip open, a sort button beside the heading switches between Most recent and By path
  • The button next to it (Open source control) opens source control for the working copy

Read the badges

Section titled “Read the badges”

Each row carries a badge for the file’s state.

The "Changed files" strip, opened. Right of the heading are the "Most recent" sort and the source-control button; five files are listed with the badges Unstaged, Staged, Untracked, Committed and No diff
Where the file is Badge
In the working copy Untracked, Unstaged, Staged, Committed or No diff
In the session’s own scratch folder Session scratch (deleted with the session)
In the agent’s own memory folder Claude memory, Codex memory (for another agent, Agent’s own memory). It opens read-only
Anywhere else Outside working copy
  • The memory badges mean the agent kind’s own memory files. They are not Agent Fleet’s agent memory
  • A file in another working copy carries that working copy’s name. It is not part of this session’s working-copy diff
  • A file only a subagent edited carries a mark that says so
Section titled “Related”