Terminal and Browser panes

The thread centre is a split of panes, not one transcript. Chat is the transcript. Terminal and Browser open from buttons in the thread header and sit beside the transcript rather than under it.

The Terminal pane is one long-lived shell per thread, started in that thread's worktree (the project root when it has none), so cd and exported variables survive between commands and you are never a directory away from what the agent is editing. It is pipes rather than a full TTY: interactive prompts and curses apps are out of scope, and closing the pane kills the shell and its scrollback.

The toolbar has Find (Enter searches up from the newest output, ⇧Enter down), Clear (the display only, the shell keeps running), Copy, and To composer, which adds the selected output to your draft as a chip you can review before sending.

When the terminal or a dev server prints a build error, a failing test or a merge conflict, a card appears at that line. Fix it asks this thread's agent to fix it, Edit prompt puts the fix prompt in the composer first, and Fork fixes it in a new thread.

The Browser pane is an embedded browser bound to the thread, with back, forward, reload and an address bar that suggests the thread's dev-server URL. It is restricted to loopback addresses: this is for looking at what you are building, not for browsing the web. The capture button screenshots the visible page and attaches the PNG to the composer. The agent on that thread can drive the same view through its own tool: navigate, reload, click and type by CSS selector, and take a screenshot it can actually see, which closes the loop between changing a page and checking it.

The agent can also read the page instead of only looking at it: a size-capped snapshot of the visible roles, names and states, whose refs it can click and type into, and diagnostics with the console messages and request results since the pane opened (no headers or bodies). The viewport picker switches between mobile, tablet, desktop and fill, and agents can switch it too. The Diagnostics toggle shows you the same console and network data, with a count of problems.

Inspect (⌖) lets you pick an element on the page: click it, or Tab to it and press Enter, with ↑ for the parent and Esc to cancel. The picked element goes to the composer as a chip with an optional comment and a cropped screenshot. The picker never reads text field values, redacts secret-looking attributes, and clicking a submit button does not submit the form.