Agentic Dev Environments & orchestrators,
scored side by side.

Every session in the Code tab automatically runs in its own git worktree under `.claude/worktrees/`; location and branch prefix are configurable in Settings → Claude Code.

Codex App ships built-in worktree support so each agent thread can work on an isolated copy of the repo.

Visual Git management and worktrees supported natively.

Each Builder task runs in a dedicated Git worktree to isolate implementation from the main checkout.

OS-level sandbox: Seatbelt on macOS, native Windows sandbox under PowerShell (or bwrap under WSL2), bubblewrap on Linux.

Tool capabilities can be wired through Docker-based MCP servers, so external tools run inside their own container instead of on the host.

Desktop app grants supervised access to local filesystem, browser, and command line.

Multiple chat tabs per workspace; switching agents mid-chat opens a new tab.

Multiple chat tabs per workspace; switching agents mid-chat opens a new tab.

`chat.new` opens a new thread while preserving the active worktree state.

The session toolbar exposes a "worktree" toggle that can be unchecked to run the session directly against the original checkout without allocating a git worktree.

Worktrees are opt-in via the /worktree command — agents otherwise run on the current checkout.

Always operates in the current directory (or --working-dir); there is no worktree layer.

Workspace env mode is a toggle between "local" (no worktree, run inside the main repo) and "worktree".

Hooks went GA on 2026-05-14; lifecycle hooks include PreToolUse and pre/post-compaction, browsable from `/hooks`.

Three lifecycle scripts: setup (on creation), run (on demand), archive (before archival).

Three lifecycle scripts: setup (on creation), run (on demand), archive (before archival).

CONDUCTOR_PORT exposes the first of 10 ports assigned to the workspace, plus other workspace env vars.

CONDUCTOR_PORT exposes the first of 10 ports assigned to the workspace, plus other workspace env vars.

Every workspace ships with a .context directory for attachments, plans, and handoff notes. Plans authored in Plan mode can be picked up by later chats via "Hand off" and "Implement plan" actions.

Every workspace ships with a .context directory for attachments, plans, and handoff notes. Plans authored in Plan mode can be picked up by later chats via "Hand off" and "Implement plan" actions.

Integrated task tracking linked to files and session history.

Context handoff occurs via task-linked documents (spec, implementation plan, QA reports) stored in the Beads issue tracker metadata instead of a traditional .context folder.

Since 2026-05-14 the ChatGPT mobile app can connect to a Mac running the Codex app to drive sessions remotely; `codex remote-control` exposes a headless app-server.

Cursor exposes its Cloud Agent ADE surface from web, iOS PWA, Slack, GitHub, Linear, and API, so sessions can be started and managed remotely.

Works across Web, Slack/Teams, Linear/Jira and Mobile.

Mobile responsive UI via server mode.

Pair from a phone/tablet via QR code, pairing token, or hosted web app at app.t3.codes.

Model dropdown next to the send button (Cmd+Shift+I) swaps the Anthropic model mid-session; the selection persists.

Switching the agent mid-chat opens a new chat tab seeded with a summary of the previous one, allowing seamless continuation with a different model.

Switching the agent mid-chat opens a new chat tab seeded with a summary of the previous one, allowing seamless continuation with a different model.

The Desktop app ships two repo-less tabs alongside Code: Chat (standard Claude conversations) and Cowork (Dispatch-style agentic work), both detached from any worktree.

A one-shot prompt can be piped to any agent file without attaching the session to a repository.

`.worktreeinclude` (gitignore-syntax) copies untracked files like `.env` or `secrets.json` into each new worktree.

Glob-based "Files to copy" feature; defaults to `.env*` and can be shared via `.worktreeinclude`.

Glob-based "Files to copy" feature; defaults to `.env*` and can be shared via `.worktreeinclude`.

Worktree setup script exposes $ROOT_WORKTREE_PATH to copy files from the main checkout (typically .env).

No first-class UI, but documented as a setup-script pattern using `ln -sf "$CONDUCTOR_ROOT_PATH/…"`.

No first-class UI, but documented as a setup-script pattern using `ln -sf "$CONDUCTOR_ROOT_PATH/…"`.

Specifier and Planner roles are explicitly read-only and automatically reject mutating permissions.

Follows a strict Specifier -> Planner -> Builder -> QA loop based on task transitions.

The "Fork from here" button on hover over any past message creates a new session and worktree from that point. The chat history is preserved but all local and committed changes since the origin worktree's starting commit are reset in the new worktree.

Per-chat "Fork to new workspace" action clones the current workspace (worktree state + session history) into a new worktree, letting you branch off an alternative exploration.

Per-chat "Fork to new workspace" action clones the current workspace (worktree state + session history) into a new worktree, letting you branch off an alternative exploration.

Launch, resume, fork, and monitor sessions.

Since v0.50.0, an explicit Unarchive action restores an auto-archived workspace (typically archived after PR merge) back to the active list with its worktree and session history intact.

Since v0.50.0, an explicit Unarchive action restores an auto-archived workspace (typically archived after PR merge) back to the active list with its worktree and session history intact.

Agent Merge addresses review comments, fixes failing checks, and merges.

Kanban-style Dashboard view available behind an experimental flag (Settings → Experimental → Dashboard). Statuses are hardcoded (Backlog / In progress / In review / Done / Canceled), no customization.

Kanban-style Dashboard view available behind an experimental flag (Settings → Experimental → Dashboard). Statuses are hardcoded (Backlog / In progress / In review / Done / Canceled), no customization.

Kanban board for parallel session management.

Task-first workflow with a Kanban board as the main operational view.

Launch, resume, fork, and monitor sessions; no juggling terminal tabs.

Desktop app diff viewer shows changes file by file before creating a pull request.

In-thread diff view lets the user review the agent changes and comment before committing.

Built-in Diff Viewer renders agent-produced changes file by file, with inline comment and PR actions.

Built-in Diff Viewer renders agent-produced changes file by file, with inline comment and PR actions.

Red/green inline diffs with block-level approval.

Built-in tools to inspect diffs and track Git state for the worktree.

Shows file diffs and opens in a side panel (IDE Emulation).

Conductor 0.54 adds an ignore-whitespace toggle to the Diff Viewer so whitespace-only changes can be hidden or shown.

Pilcrow toggle in the DiffPanel shows/hides whitespace-only changes.

Ignore Whitespace toggle in the file tree hides whitespace-only changes.

Diff Viewer offers several selectable scopes: branch vs. target, uncommitted changes, per-commit, and per-turn (changes produced by a single agent discussion).

Diff Viewer offers several selectable scopes: branch vs. target, uncommitted changes, per-commit, and per-turn (changes produced by a single agent discussion).

Each agent turn exposes a footer listing the files it changed; clicking a file jumps straight to its diff scoped to that turn — no manual commit needed to delimit the per-turn diff.

Each agent turn exposes a footer listing the files it changed; clicking a file jumps straight to its diff scoped to that turn — no manual commit needed to delimit the per-turn diff.

Multiple themed completion sounds (SNCF jingle, Paris Métro chime, SF Muni, NYC MTA…) selectable from General settings with a Test button.

Multiple themed completion sounds (SNCF jingle, Paris Métro chime, SF Muni, NYC MTA…) selectable from General settings with a Test button.

Each thread can launch "repeatable project actions" and run commands directly from the UI.

Project scripts are user-defined shell commands launched from the UI (ProjectScriptsControl) and bindable to keybindings via `script.{id}.run`.

Click any line in the desktop diff to add a comment; Claude reads the comments and revises.

Users can comment on the diff inside the thread; comments are surfaced back to the agent.

Comments on changed lines are sent back to the agent as precise context.

Comments on changed lines are sent back to the agent as precise context.

Inline comments collected and sent to the agent in the next message.

Desktop app has an integrated terminal pane rooted in the session's working directory.

Multiple terminal tabs per thread, rooted in the thread workspace.

Multiple terminal windows can be opened simultaneously on the same worktree (Terminal 1, Terminal 2, ...).

Multiple terminal windows can be opened simultaneously on the same worktree (Terminal 1, Terminal 2, ...).

Supervised command line access.

Built-in Terminal to connect to running sessions or launch new ones.

Built-in terminal drawer with split, new, toggle and close commands; default `mod+j` binding.

The Files panel exposes a full project file-tree browser that lets you navigate and open any file in the project.

Sidebar exposes the project files with rich previews (PDF, spreadsheets, documents) since the April 2026 update.

Built-in file tree pane in the workspace; click a file to open it in the built-in editor, drag folders onto the Composer to attach.

Built-in file tree pane in the workspace; click a file to open it in the built-in editor, drag folders onto the Composer to attach.

Desktop file pane supports spot edits with Save, with stale-file detection.

Built-in file editor with full syntax highlighting and ⌘F.

Built-in file editor with full syntax highlighting and ⌘F.

Cursor is a full code editor — files can be edited and saved directly.

Desktop preview pane embeds a browser bound to `launch.json` dev servers; Claude can drive it (start dev server, hit API endpoints), read server logs, and act on the preview.

In-app browser added in April 2026 lets Codex operate local dev servers and navigate rendered pages — i.e. the orchestrator can both display and act on the preview.

Integrated browser with Design Mode lets the orchestrator drive a local web app (clicks, navigation) and "see" the rendered page (screenshots, accessibility audits) — full criterion met.

Built-in preview browser tied to the dev server script configured per repository.

The `AskUserQuestion` tool call is rendered inline in the Desktop chat as a structured dialog with multiple-choice options and a free-text fallback.

Conductor renders Claude's AskUserQuestion tool calls as an interactive, keyboard-navigable UI inline in chat; supports multi-select questions.

Conductor renders Claude's AskUserQuestion tool calls as an interactive, keyboard-navigable UI inline in chat; supports multi-select questions.

The system intercepts MCP pending permissions and pending questions to expose them to the user.

ClaudeAdapter detects `AskUserQuestion` tool calls and emits a `user-input.requested` runtime event; the composer renders a dedicated ComposerPendingUserInputPanel with keyboard-shortcut option selection and multi-select support.

Claude Code Desktop offers a "Rewind to here" button on hover over any past message, allowing the user to restore the conversation and/or file edits to that checkpoint directly from the UI.