Source control and history

3 min read

Agents edit real files in a real repository, so the Director keeps the answer to "what did it actually change?" one tab away. The Source Control tab shows the state of the session's git repository; for the conversation that produced it, the History button and the Cockpit's Chat tab are covered below.

The changes badge

A session card can carry an amber "N chg" badge - a count of uncommitted changes in that session's working tree, staged and unstaged together, so a file staged and then edited again is counted in both. The badge is absent, never "0 chg", when the tree is clean or the count is unknown - absence is not proof of a clean tree. And the number is the last count a probe produced: when a later probe fails or the folder goes missing, the Director keeps that number rather than reporting zero, so it can be stale. It is still the earliest honest signal of progress: an agent that claims to be done with no changes reported, or one that has quietly touched forty files, both deserve a look before you move on.

The Source Control tab

Select a session and open Source Control. At the top, the branch bar shows the current branch and how it relates to the rest of the world: a green ^N badge counting commits not yet pushed, an orange vN for commits not yet pulled, a blue badge naming the main branch when yours has fallen behind the main line, and a small "no upstream" note when the branch has no upstream yet. Below it, the Changes file tree lists what the agent has modified, with a count in its header; a second tree, Staged Changes, appears above it only while something is staged. When the working tree is clean it says so: "No changes detected".

Note

The Source Control tab is a review surface, not a git client. When you are happy with the changes, commit them the way you always do - ask the agent to commit, or use your own git tools. Open in VS Code and Open in Explorer on the card menu drop you into the repository directly.

Conversation history

The History button on the action bar above the prompt bar opens the agent's own in-terminal history picker - for Claude Code, the same picker its double-Escape opens - so you can jump back through the live conversation right in the terminal. Esc closes it.

For a readable transcript - every message between you and the agent, with Show filters for Tool calls, Results, and Thinking so you can read just the conversation or audit exactly which actions the agent took and what came back - open the session in your browser: that is the Cockpit's Chat tab, on Working in a session.

Tip

When a diff surprises you, read the Cockpit's Chat tab with only Tool calls turned on. The list of file edits and commands, in order, is usually the fastest way to see where the agent went off the path you intended.

Past sessions

The Resume Session tab in the New Session dialog lists past Claude Code conversations - each with a summary, its message count, and how long ago it ran. See starting and steering agents.