Code panel

The window's Code tab sits in the Device panel, next to Inspector. It shows code next to the live screen. It is read only: it has no editor, and it never writes a file in your project. Open in editor sends the file to your own editor, as the Inspector's button does.

A file at a lineCopy Anchor Link

The Inspector's file link (for example src/screens/Home.tsx:41) and an error card's Open file:line open the file in the Code tab with the line highlighted. For an error, its text shows under the line. A file over 1 MB, or outside the project folder, is not opened, and the tab says why.

Whose changes these areCopy Anchor Link

The top of the tab names the session and its folder, for example Claude Code · my-app, and why that session was chosen. Its menu switches to any other session that has a folder. Without your pick the tab chooses, in this order:

1. the session of the card you pressed Show the diff for;
2. a session with an edit waiting for you;
3. the session the message box is aimed at;
4. the most recently active session.

Paths are relative to the repository root, and grouped by folder when more than eight files changed.

Changes in the folderCopy Anchor Link

For the chosen session, the tab lists the files changed in its folder, with +/− counts, and shows the diff of the selected file. Pick a scope:

• This session: everything since Parallax first saw the session.
• Last turn: what changed since your last prompt.
• Uncommitted: the working tree against HEAD, whoever made the change and in whichever session. Untracked files are in, ignored files are out.

The diff is inline. With the panel wider than about 900 px, Diff layout offers side by side. The list reads again when a turn ends, when you press Refresh, and a moment after a waiting edit is answered.

An edit before you approve itCopy Anchor Link

With answering from the window set up, an edit the agent asks about shows its diff before you answer. This works for Claude Code's Edit, MultiEdit and Write, and for Codex's apply_patch.

• The card in Approvals shows +n −m and Show the diff.
• The Code tab shows the same edit under an amber bar, Waiting for your approval · Deny · Allow, above the diff as it would be written. Answering on the card, on the bar or in the agent's own terminal clears both.
• The bar names its edit and offers Allow and Deny only while that edit's diff is on show. Its buttons wake 300 ms after it appears, so a click aimed at one edit cannot land on the next.
• An edit over about 64 KB of text is not shown before you answer. It shows in the list after it lands.

Undo and comments go to the agentCopy Anchor Link

The window does not undo a change. On a changed file, and on each hunk, Ask the agent to undo and Comment on this change put a reference (the file, the hunk's lines, this turn or this session) into the message box of the session the change belongs to. Nothing is sent until you press Send to agent, and nothing is written in your project.

What the tab hidesCopy Anchor Link

Every line the tab shows goes through the same secret rules as an approval card: an opened file, the hunks of a changed file and the diff of a waiting edit. Known token prefixes, key: value credentials, secret-looking parts of a URL and long runs of mixed letters and digits are masked. A private key block is replaced whole, and a line is cut at 2,000 characters. A token in an open .env does not show in the window or in a screenshot of it; the file itself is not changed. The rules reduce the risk and do not remove it, and they can hide a harmless long identifier.

LimitsCopy Anchor Link

• Claude Code in auto mode asks nothing, so there is no card and no diff before the edit. The change shows in the list after it lands.
• An edit made through a shell command shows in the changes, never as a card.
• Edits to files that git ignores are not shown.
• A folder that is not a git repository says so; the file view still works.
• A snapshot that takes too long, such as a very large first one, is abandoned and the tab says why. The list can then be incomplete, and says so.

See Privacy for what the snapshots write and what the window holds in memory.