Side panels

The side panel sits right of the conversation. Terminal, Browser, Files and Diffs exist only in the desktop app (what each app has).

Open, resize and arrange the panel#

The app saves the layout (open tabs, tab groups, width, terminal drawer, file tree) per session. A new session starts from the last layout of its project. Open files and the terminal order are per session. Files filters are per project.

Artifacts#

Pull requests, branches, commits and recorded files from the session, plus kinds extensions add. Click one to open it. Settings › Interface › Conversation › Artifacts turns tracking off.

Diffs#

The left list shows every changed file (Hide file list folds it). Views are unified or split, with optional line wrap. Changed images, video and audio show Before and After side by side.

To review, select lines, then click the gutter + or right-click:

Command FF finds in the diffs. Command Shift FF searches across the changes.

Files#

The session's folder as a tree with git status. A file opens in a tab. A dot marks unsaved changes.

A changed file opens on its changes. Plain view shows the file alone. Editor and Finder open it in your editor or the system file manager.

Every option: Settings › Interface › Files & editor.

Files and Diffs read files where the session runs: a sandbox, a worktree or a server.

Terminal#

The session's terminals run where the session runs: this computer, its container or sandbox, or its server. The drawer under the conversation shows the same terminals.

Terminals run in the daemon, so they need Settings › Advanced › Experimental › Shared daemon runtime (Settings › Interface › Terminal & browser shows the connection state). They keep running after you close the window.

The header has no terminal button. Use the keys below, or Toggle terminal in the palette.

A session holds 12 terminals that you opened, plus the agent's task terminals. A tab shows starting, failed to start, disconnected or exited. Drag tabs to reorder them. Each session keeps its order.

Showing the drawer starts a shell when the session has none of yours. A drawer that is already open when you get to the session (a new session copies its project's layout, and the app restores it after a restart) starts none: it shows a New terminal button.

Archiving a session ends its shells, except those in a cloud sandbox (E2B, Daytona), which pause with the sandbox. A shell on this computer or on a server also ends after 30 minutes with no window showing it, no output and no typing, if nothing runs in it. A dev server, or a job you left in the background with &, keeps it running.

The host keeps the last 4 M characters of each terminal's output. A window that opens the terminal again shows that history, up to 5,000 lines of scrollback. The drawer and the Terminal tab each keep the last 3 terminals you looked at ready. An older one replays its history when you show it again. Only the focused terminal's cursor blinks.

URLs, localhost:5173 and file:line:col paths in the output are links. On macOS the usual line-editing keys work, such as Option Left Arrow to move by word.

With Settings › Agent › Agent tools › Agent can use your terminals, the agent reads your terminals and types in them after you approve. With Agent's background tasks in terminals (on by default), each background command that the agent starts gets a tab. Stop in that tab ends the task. Show terminal in Running work brings a task's tab up, focused, without opening a shell of your own. With Settings › Interface › Terminal & browser › Close terminals that exit cleanly (on by default), a clean exit closes the tab. A failed shell stays open.

Browser#

The Browser tab is a browser for the app you are building, with one page per session. The address bar takes a URL or a bare port (5173). Only http and https pages load. An empty tab shows the last 6 pages of the project that loaded as cards, with their icon, title, address and how long ago you visited them, and lists dev servers running on this computer. A page counts once per address and path: a different query or hash, or a route change inside your app, is the same page. An address that failed to load does not count. Right-click a card, or use its ⋯ button, to open the page in your usual browser or remove it from the list. Press Enter in an empty address bar to go back to it.

Each project has its own browser profile, so logins and local storage stay after a restart. The pages of the last 2 sessions that showed the browser stay loaded. Another session's page reloads at its last URL when you show it again. A crashed page reloads at its last URL, 3 times in 30 seconds at most. After that, the tab shows a reload button.

With Settings › Agent › Agent tools › Agent can use the browser, the agent opens, reads, clicks and types with the browser_* tools. A cursor shows where it acts. Your own click or typing interrupts it. Settings › Interface › Terminal & browser › Show the browser when the agent uses it opens the tab the first time in a run that the agent uses the browser of the session on screen.

Inbox and todos#

Inbox holds the plans and questions that the agent waits on in the open session. The current one shows as a card, and older ones stack under it. A new request opens the tab (where requests wait).

Todos shows the agent's live todowrite list and keeps it with the session after the run. Click a status to cycle it, click an item to edit it, add or remove items, or clear the list. The badge counts open items. The Todos badge of the composer also opens the tab.

Queue#

Queue lists the messages you sent during a run, in the order they go out when the run ends. The tab's badge and the composer's Queued badge count them.

Attachments show as one chip that opens them in a preview. While you edit a message, paste, drop or attach files to add one, or remove one.

Reference#

• Extensions: registerPanel and the panel content model.
• Terminals: how terminals run in each environment.