Skip to main content
A workspace is the unit Conductor actually operates on.

Where repo reality meets the control plane

A clean workspace definition is what makes task routing, worktree isolation, review context, and retry behavior predictable. It is the difference between orchestration and a pile of disconnected shells.

Repository rootBoard pathAgent defaultBranch + review state
Conductor workspace board
It connects:
  • the repository root
  • the markdown task surface
  • project settings and agent defaults
  • runtime controls for sessions, diffs, and review

Setup and structure

Create, manage, and map workspaces to the correct repository roots and board files.

Execution and control

Move between the board, chat interface, command bar, slash commands, and active sessions.

Review and delivery

Inspect diffs, handle Git operations, and keep multi-repo work readable when a task crosses boundaries.

Remote-aware operation

Keep the browser UI reachable without breaking the local-first runtime model.

Why workspace boundaries matter

The better the workspace definition, the more reliable everything downstream becomes: worktrees, session routing, pull requests, and reviewer context.
Last modified on March 6, 2026