Workspaces

A workspace is one tab holding everything a project needs at once: the conversation, a terminal already sitting in the right folder, and a browser pane. Switching tabs switches all of it together, which is the whole point.

Opening one

Open one from the command palette ("Open Workspace"), or from the button on a worktree row. A worktree is a second working copy of the same project, and it opens as a workspace of its own. A workspace with no session yet offers to start one.

It opens as the conversation and nothing else. The other panes appear when you ask for them. Avoiding the terminal is the reason the app exists, so a terminal you did not ask for is not a good opening frame.

Arranging panes

Drag a pane by its header:

• onto the left, right, top or bottom edge of another pane and it splits there
• into the middle of another pane and the two swap places

The layout is built from nested splits rather than a fixed frame, so it can express any arrangement. Dividers move only the two panes either side of them. Closing a pane hands its space back to its neighbours rather than collapsing the layout. Escape abandons a drag part way through.

Pane headers only appear once there is somewhere to drag to.

Focus mode (Cmd+Shift+Enter, or the command palette) folds the chrome away from around your work: rail, sidebar, right panel, tab bar and status bar all leave the frame until you toggle it back. The panes inside the workspace stay as you arranged them.

The terminal and the browser

Each workspace gets a stable suggested port, seeded into its terminal as $PORT. The browser pane watches that address and adopts it on its own once something is actually answering there. Until then it shows a neutral empty state rather than an error, because a workspace is not necessarily a coding workspace.

The terminal keeps running while you are on another tab, and whatever arrived while you were away is replayed when you come back. The browser pane is an iframe, so a site that refuses to be framed shows blank rather than loading. An agent can drive both panes through the MCP server: see the MCP server docs.

Worktrees

A worktree is your project checked out a second time, in a folder of its own, so two workspaces can exist side by side without fighting over the same files. Create one from the worktree list, then open it from the button on its row; it becomes its own workspace, with its own session, terminal and port. The worktree list appears once a project has more than one.