Working in a space
Files, changes and search
The right panel — browsing the space's files, reading its diff, and finding your way around a checkout.
The panel on the right of a space is how you check the agent’s work without leaving the conversation. It has three tabs, each scoped to that space’s checkout — so what you see is the branch you’re on, not the project root.
⌘. shows and hides the panel. ⌘⇧. expands it into a wide reading pane and back.
Files
A file tree for the space’s checkout, with a reader beside it. ⌘E jumps here.
When the agent mentions a file, clicking through opens it in this tree with its parent folders expanded. In the expanded pane you can hide the tree column entirely and let the reader fill the space, which is what you want for reading a long file rather than browsing.
Changes
Everything uncommitted in the space, as a diff. ⌘D jumps here.
This is the review surface: after a turn finishes, open Changes and read what actually happened. Expand it (⌘⇧.) to read the diff at full width. The sidebar keeps a running count of commits ahead of and behind your home branch, so you can see a space’s shape without opening it.
Context
The project’s context library — background docs the agent can read. ⌘⇧E jumps here. It has its own reader, separate from the Files tab, so opening a context doc doesn’t lose your place in the tree.
Go to file
⌘P opens fuzzy file search across the space’s checkout, which is usually faster than the tree.
Search skips a list of directory names you control in Settings › General › System › File search — that’s how node_modules and friends stay out of the results. The list only affects search; the file tree still shows everything.
Reading a diff before merging
The habit that makes parallel agents work is a short one: when a space lands in your inbox, open Changes, read the diff, and either send it back with a note or ship it. The pull request control is the other half of that — it’s the same review, just with checks attached.