Workspaces & grid

Workspaces

A workspace is a project folder with its agents. The sidebar lists all workspaces with their sessions; the number shows how many are running. Workspaces can be collapsed, renamed and told apart by color.

Starting agents

• + next to the grid / “Add terminals”: opens the one-page session start — pick a preset (e.g. “Pair programming”), an agent card (CLIs that are not set up are greyed out), how many, and see “Will launch” below (single seats and accounts can be changed), plus own worktree and focus view. A new folder becomes a workspace.
• Task bar (Ctrl+Shift+A): one sentence is enough, see Workflow.
• + on a workspace: new session in that project — as a terminal (the CLI as usual) or as a thread (conversation with approvals, see Threads).
• Set up several …: several agents at once, also with different accounts.

Handing over to another CLI

When a CLI's quota is used up or another one should take over: the Hand over button (share icon) at the top right of the session, pick the CLI, optionally add a wish (“Only fix the failing tests”). The new CLI starts in the same folder (also in the same worktree) and gets a handover with:

• the task — from the board or the latest instructions to the old session,
• the git state — branch and changed files with line counts,
• the old session's latest output (cleaned up, secrets redacted),
• the request to read git diff first and not to redo anything.

The old session stays open; a linked board task moves along. Handover always goes to another CLI, never to another account of the same one. Threads have a handover as well (see Threads).

Grid and focus

The grid shows every session as a tile you can type into directly. The All projects view puts the sessions of every workspace side by side. Double-click a session to open it in focus.

Each tile shows its state: working, waiting for you (question or approval) or exited. When an agent waits, you can get a notification.

Terminal panel

Ctrl+J opens a normal terminal at the bottom, in the folder of the current workspace — like in VS Code, independent of the agents. Several shells as tabs; drag the top edge to resize.

• Ports — every local server a terminal starts (e.g. npm run dev → localhost:3000), with a green dot while it runs: Open in browser, Copy, Stop.
• Problems — failing tests and crashed agents of the project, with Let it fix.
• Top right: new shell, split (two shells side by side), kill, maximize.

When the conductor starts a dev server, it lands here — the grid stays reserved for agents.

Status

Besides working, waiting for you and exited:

• not responding — you typed something but the screen hasn't changed for 10 seconds. Usually the CLI is stuck; close and restart it, the history is kept.
• provider overloaded — the CLI reports e.g. “429 · overloaded” or “529 overloaded_error”. That's on the provider, not you: wait a moment and send the message again.

Side panel

On the right are orchestrator, changes, agents, browser and editor. Drag the tabs to reorder them; the order is remembered.

Agent browser: Claude Code, Codex, Kimi Code and Gemini CLI can drive the built-in preview themselves — open a page, read it, click, fill in fields, take a screenshot, switch to phone view, read console errors. That way they check their work instead of launching their own browser. Above the preview you see which agent is driving it. Local pages only (localhost).

After a restart

Sessions continue after restarting the app: each CLI resumes its last conversation. Old threads can be archived; they leave the sidebar, the history stays.