From 55537091caa2e61e8e59c51912a5bb1e46948306 Mon Sep 17 00:00:00 2001 From: scgopi Date: Sat, 7 Nov 2026 21:18:34 -0800 Subject: [PATCH 1/4] Start Conductor alternative page Signed-off-by: scgopi From 82e600dc922e1e7cba5fd65c220cef756d1b9280 Mon Sep 17 00:00:00 2001 From: scgopi Date: Sat, 7 Nov 2026 21:21:30 -0800 Subject: [PATCH 2/4] Add a Conductor alternative page Signed-off-by: scgopi --- .gitignore | 1 + docs/conductor-alternative.html | 356 ++++++++++++++++++++++++++++++++ 2 files changed, 357 insertions(+) create mode 100644 docs/conductor-alternative.html diff --git a/.gitignore b/.gitignore index 7c86ed09a..22c25eb02 100644 --- a/.gitignore +++ b/.gitignore @@ -57,6 +57,7 @@ zig-out/ /docs/* !/docs/index.html !/docs/compare.html +!/docs/conductor-alternative.html !/docs/shortcuts.md !/docs/_config.yml !/docs/_layouts/ diff --git a/docs/conductor-alternative.html b/docs/conductor-alternative.html new file mode 100644 index 000000000..4c0310e8f --- /dev/null +++ b/docs/conductor-alternative.html @@ -0,0 +1,356 @@ +--- +title: A Conductor alternative for parallel coding agents on the Mac +description: Conductor is joining Meta and Conductor Cloud shuts down on 20 November 2026. What is changing, how Conductor's workspaces, agents, goals and routines map onto GraphCode's loops, and how to start a first loop in a few minutes. +--- + + + + + +{% seo %} + + + + +{% include head-custom.html %} + + + + + + +
+
+
+
For Conductor users · sourced 7 Nov 2026
+

Moving off Conductor? Run your parallel agents as a graph of loops.

+

Conductor is joining Meta. Conductor Cloud goes read-only on 13 November and shuts down on 20 November 2026, and new users can no longer download the app. GraphCode is a native macOS app that runs Claude Code, Codex, Copilot CLI, OpenCode and pi side by side, each in a live terminal you can step into, kept running by a local daemon.

+

Method: every statement about Conductor below quotes or paraphrases Conductor's own announcement, changelog or docs, fetched on 7 November 2026, and cites it. Every statement about GraphCode is checked against its README and source, linked at the bottom.

+
+
+ +
+

What is happening to Conductor

+

Conductor announced on 4 November 2026 that it is joining Meta.12 Its announcement sets out this timeline:1

+
    +
  1. 4 NovNo new sign-ups. "New users can no longer sign up for Conductor or download the app." Pro users keep Pro features for free, and active subscribers get a refund.
    2. +
  2. 13 NovConductor Cloud goes read-only: "You can still read old chats and export data, but you can't send new messages."
    3. +
  3. 20 NovConductor Cloud shuts down: "We begin deleting Conductor Cloud user data. Please export your data before this date."
    4. +
  4. Early 2027The local Mac app "will continue to receive new models and critical bug fixes until early 2027", then starts winding down.
    5. +
+
+

Before 20 November, Conductor's own guidance is to bring a cloud workspace and its chats to your Mac with right-click › Transfer to local, or to export everything from Settings › Account › Export data.2 Do that first; your branches and worktrees are ordinary git, so nothing below needs Conductor's data to get started.

+
+
+ +
+

Why GraphCode fits a Conductor workflow

+

The same job, running several coding agents at once on your own Mac, organised as a graph of loops instead of a list of workspaces.

+
+

Native macOS

A Mac app for macOS 15+ on Apple Silicon, Developer ID signed and notarized. Terminals render with GhosttyKit.
+

Live, steerable terminals

Each node on the canvas is a loop running inside a real agent CLI session. Click it to open that session's terminal and type into it mid-run.
+

Your choice of agent, per loop

Claude Code, GitHub Copilot CLI, Codex, OpenCode or pi. A Codex loop can hand off to a Claude Code loop; an edge never asks which agent is on either end.
+

Local daemon and CLI

graphcoded keeps loops alive with the app closed, fires edges and polls goal checks. The graphcode CLI drives the same daemon from a shell or from another loop.
+

Sessions that outlast the app

Every loop's terminal is a zmx session. It survives quitting the app; after a reboot the backend's saved session id is resumed rather than started again.
+

Source-available, free

The app and daemon are FSL-1.1-MIT, converting to MIT two years after each release. The CLI and GraphcodeKit are MIT. There is no paid tier.
+
+
+ +
+

Conductor concepts, in GraphCode terms

+

An honest mapping. Where GraphCode has no equivalent, the row says so.

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConductorWhat it is thereIn GraphCode
Workspace"An isolated copy of a project and repository for one task", one workspace to one branch, backed by a git worktree.34A loop: one node on the project's canvas, one live agent session. Its worktree is optional: in the create form pick none (run in the checkout), an existing worktree, or a new branch, which GraphCode creates and later offers to sweep.
Repository / projectThe repository a workspace is cut from.3A project in the sidebar: a local folder, a clone from a URL, or a repository on a remote host over SSH.
Several agents in one workspaceAgents on the same branch in separate tabs.56Several loops in one project sharing a checkout or worktree, or extra tabs and splits inside one loop's terminal workspace.
Agent pickerClaude Code, Codex, Cursor or OpenCode.6Chosen per loop: Claude Code, Copilot CLI, Codex, OpenCode or pi (--backend on the CLI). The CLI must already be on your PATH. No Cursor backend.
Chat panel and Big TerminalA chat panel per agent session plus a workspace terminal.6The agent's own terminal UI, live, with tabs and splits. graphcode node send types into any loop from a shell or from another loop.
Codex goals (/goal)Keeps a local Codex session working across turns.6A goal-based loop, on any backend. It resolves when the goal is met, optionally decided by a shell check that exits 0 (for example make test).
Plan ModeAn agent mode that plans before editing.6The backend's own modes stay available in its terminal. A turn-based loop additionally pauses for your review every turn, or only before writes.
RoutinesAgents on a schedule or from a GitHub Action, run in the cloud.7A time-based loop, run locally. Its cadence lives in its prompt (/loop 1h …); for Codex, OpenCode and pi, switch on the experimental Daemon heartbeat. No GitHub Action trigger.
Handoffs and .context notesA .context folder in the workspace for notes and handoffs.3Edges between loops (hand-off, message, spawn), a memory log per loop that a relaunched session reads first, and the Mailroom, a board every loop in the graph can post to. Nothing is written inside your project folder.
Cloud workspacesWorkspaces in Vercel sandboxes that keep running with the app closed; shutting down 20 November.18The local daemon keeps loops running with the app closed. To run on another machine, add a remote project over SSH; loops run there and this Mac steers them. No hosted cloud.
MultiplayerTeammates prompting a shared cloud workspace in real time.8No equivalent. GraphCode is single-user.
Setup scripts, files to copyGitignored files copied into each new worktree; setup scripts for the rest.4No equivalent. GraphCode creates the worktree; ask the loop's prompt to run your setup.
+
+
+ +
+

Migration quickstart

+

About five minutes from install to a running loop. Your existing repositories, branches and worktrees work as they are.

+
    +
  1. Export from Conductor first. Before 13 November if you still want to send messages in the cloud, and before 20 November at the latest: right-click a cloud workspace › Transfer to local, or Settings › Account › Export data.
    2. +
  2. Install GraphCode. macOS 15+ on Apple Silicon, with at least one of claude, codex, copilot, opencode or pi on your PATH. GraphCode bundles none of them, so the CLIs you used under Conductor carry over with their logins. +
    $ brew install --cask scgopi/graphcode/graphcode
    + Or drag GraphCode to Applications from the latest .dmg.
    3. +
  3. Add your repository. The sidebar's ⊕ menu: a local folder (the repo you had in Conductor), a clone from a URL, or a remote repository over SSH.
    4. +
  4. Create your first loop. ⊕ on the canvas. Write the prompt, pick the agent, choose Goal, and give it a done check; the Test button runs the check exactly as the daemon will. To mirror a Conductor workspace, set the worktree to a new branch. From a shell, the same loop is: +
    $ graphcode node create ~/code/my-repo --title FixBuild --type goal \
+    --goal "the test suite passes" --predicate "make test" --backend codex
    5. +
  5. Open it and steer. Click the node to attach to the live session. Add a second loop and drag an edge between them to hand work on when the first resolves. Close the app; the daemon keeps both running.
    6. +
+
+ +
+

Sources

+

Fetched on 7 November 2026. If Conductor's pages change, its own pages win; open an issue on the GraphCode repo and this page gets corrected. The full comparison covers Conductor alongside Vibe Kanban, Claude Squad, Superset, Emdash and Sculptor.

+
    +
  1. conductor.build/announcement, "Conductor is joining Meta", timeline and FAQ.
    2. +
  2. conductor.build/changelog, 0.93.0 "Conductor is joining Meta", 4 November 2026; see also AI Weekly, 4 November 2026.
    3. +
  3. conductor.build/docs/concepts/workspaces-and-branches.
    4. +
  4. conductor.build/docs/concepts/git-worktrees.
    5. +
  5. conductor.build/docs/concepts/parallel-agents.
    6. +
  6. conductor.build/docs/concepts/agent-modes.
    7. +
  7. conductor.build/changelog, 0.85.0 "Sections, routines, and a new model picker", 9 September 2026.
    8. +
  8. conductor.build/pricing, plans and the Cloud FAQ, as cited on the comparison page (12 September 2026).
    9. +
+
+ The GraphCode statements are drawn from the shipped code and the README: + +
+
+ +
+
+
+

Bring your agents. Keep your Mac.

+

Add the repo you had in Conductor, write a goal, pick the agent. Then close the app; the loop keeps going.

+
+ ⬇ Download .dmg + ★ View on GitHub +
+
$brew install --cask scgopi/graphcode/graphcode
+
+
+
+ + + + + From 7686cef41f5a76c5daad321933e75943dc7b259a Mon Sep 17 00:00:00 2001 From: scgopi Date: Sat, 7 Nov 2026 21:28:46 -0800 Subject: [PATCH 3/4] Rewrite the Conductor page as a first-person article Signed-off-by: scgopi --- docs/conductor-alternative.html | 174 ++++++++++++++------------------ 1 file changed, 77 insertions(+), 97 deletions(-) diff --git a/docs/conductor-alternative.html b/docs/conductor-alternative.html index 4c0310e8f..a07018146 100644 --- a/docs/conductor-alternative.html +++ b/docs/conductor-alternative.html @@ -1,6 +1,6 @@ --- title: A Conductor alternative for parallel coding agents on the Mac -description: Conductor is joining Meta and Conductor Cloud shuts down on 20 November 2026. What is changing, how Conductor's workspaces, agents, goals and routines map onto GraphCode's loops, and how to start a first loop in a few minutes. +description: Conductor Cloud shuts down on 20 November 2026. I build GraphCode, a native Mac app for running coding agents in parallel, and this is how Conductor's workspaces, goals and routines map onto it, what it does not do, and how to start. --- @@ -130,25 +130,21 @@ .cta-inner h2 { font-size: 26px; } .brew { font-size: 11.5px; } } - .timeline { list-style: none; margin: 0; padding: 0; display: grid; gap: 12px; max-width: 860px; } - .timeline li { display: grid; grid-template-columns: 120px 1fr; gap: 18px; padding: 16px 18px; border: 1px solid var(--line3); border-radius: 12px; background: var(--card); font-size: 14.5px; line-height: 1.6; color: var(--ink-soft); } - .timeline .when { font-family: var(--mono); font-size: 12px; letter-spacing: .04em; color: var(--amber); padding-top: 2px; } - .prose { max-width: 760px; font-size: 15px; line-height: 1.65; color: var(--ink-soft); } - .prose p { margin: 0 0 14px; } - .fit { display: grid; grid-template-columns: repeat(auto-fit, minmax(260px, 1fr)); gap: 14px; } - .fit div { padding: 18px 20px; border: 1px solid var(--line3); border-radius: 12px; background: var(--card); font-size: 14px; line-height: 1.6; color: var(--ink-soft); } - .fit h3 { margin: 0 0 6px; font-size: 15px; font-weight: 600; color: var(--ink); } + .article { max-width: 760px; } + .article p { font-size: 16px; line-height: 1.7; color: var(--ink-soft); margin: 0 0 18px; text-wrap: pretty; } + .article h2 { margin-top: 0; } + .article .quiet { color: var(--ink-mid); } + figure.shot { max-width: 1180px; margin: 40px auto 0; padding: 0 28px; } + figure.shot img { display: block; width: 100%; height: auto; border: 1px solid var(--line3); border-radius: 14px; } + figure.shot figcaption { margin-top: 10px; font-size: 13px; line-height: 1.55; color: var(--ink-faint); max-width: 760px; } table.map { min-width: 760px; } table.map tbody td { width: 42%; } - .steps { margin: 0; padding-left: 0; list-style: none; counter-reset: step; max-width: 860px; } - .steps li { counter-increment: step; position: relative; padding: 0 0 22px 44px; font-size: 15px; line-height: 1.6; color: var(--ink-soft); } - .steps li::before { content: counter(step); position: absolute; left: 0; top: 0; width: 28px; height: 28px; border: 1px solid var(--line4); border-radius: 50%; font-family: var(--mono); font-size: 12px; color: var(--amber); display: flex; align-items: center; justify-content: center; } - .steps strong { color: var(--ink); } - pre { margin: 10px 0 0; padding: 14px 16px; background: var(--bg); border: 1px solid var(--line3); border-radius: 10px; font-family: var(--mono); font-size: 12.5px; line-height: 1.65; color: #d6d6d2; overflow-x: auto; } + .steps { margin: 0 0 18px; padding-left: 22px; font-size: 16px; line-height: 1.7; color: var(--ink-soft); } + .steps li { margin: 0 0 10px; padding-left: 4px; } + .steps code { white-space: normal; overflow-wrap: anywhere; } + .steps li::marker { font-family: var(--mono); color: var(--amber); font-size: 13px; } + pre { margin: 6px 0 18px; padding: 14px 16px; background: var(--panel); border: 1px solid var(--line3); border-radius: 10px; font-family: var(--mono); font-size: 12.5px; line-height: 1.65; color: #d6d6d2; overflow-x: auto; white-space: pre; } pre .prompt { color: var(--green); user-select: none; } - @media (max-width: 720px) { - .timeline li { grid-template-columns: 1fr; gap: 4px; } - } @@ -174,43 +170,46 @@
-
For Conductor users · sourced 7 Nov 2026
-

Moving off Conductor? Run your parallel agents as a graph of loops.

-

Conductor is joining Meta. Conductor Cloud goes read-only on 13 November and shuts down on 20 November 2026, and new users can no longer download the app. GraphCode is a native macOS app that runs Claude Code, Codex, Copilot CLI, OpenCode and pi side by side, each in a live terminal you can step into, kept running by a local daemon.

-

Method: every statement about Conductor below quotes or paraphrases Conductor's own announcement, changelog or docs, fetched on 7 November 2026, and cites it. Every statement about GraphCode is checked against its README and source, linked at the bottom.

+
For Conductor users · 7 November 2026
+

Conductor Cloud shuts down on 20 November. Here is where your agents can go.

+
+

If you run your coding agents in Conductor, you have probably seen the news. Conductor is joining Meta, and its cloud stops accepting new messages on 13 November. The Mac app keeps working for a while longer, with only new models and critical bug fixes until early 2027, so you need a new home for your agents before long.

+

I'm Srinivasa Chaitanya, and I build GraphCode. It is a native Mac app for the same job Conductor does: running several coding agents in parallel on your own machine. I wrote this page for people deciding where to go next. What I say about Conductor comes from its own announcement and docs, linked at the bottom. What I say about GraphCode I checked against its code.

+
-

What is happening to Conductor

-

Conductor announced on 4 November 2026 that it is joining Meta.12 Its announcement sets out this timeline:1

-
    -
  1. 4 NovNo new sign-ups. "New users can no longer sign up for Conductor or download the app." Pro users keep Pro features for free, and active subscribers get a refund.
    2. -
  2. 13 NovConductor Cloud goes read-only: "You can still read old chats and export data, but you can't send new messages."
    3. -
  3. 20 NovConductor Cloud shuts down: "We begin deleting Conductor Cloud user data. Please export your data before this date."
    4. -
  4. Early 2027The local Mac app "will continue to receive new models and critical bug fixes until early 2027", then starts winding down.
    5. -
-
-

Before 20 November, Conductor's own guidance is to bring a cloud workspace and its chats to your Mac with right-click › Transfer to local, or to export everything from Settings › Account › Export data.2 Do that first; your branches and worktrees are ordinary git, so nothing below needs Conductor's data to get started.

+
+

What Conductor announced

+

On 4 November 2026 Conductor announced that it is joining Meta.12 New sign-ups and app downloads stopped that day. Existing Pro users keep Pro features for free, and active subscribers are being refunded.

+

The cloud goes first. From 13 November, Conductor Cloud is read-only. In Conductor's words, "You can still read old chats and export data, but you can't send new messages." On 20 November it shuts down and Conductor begins deleting Cloud user data. The local app "will continue to receive new models and critical bug fixes until early 2027", and then starts winding down.1

+

So export before you do anything else. Conductor documents two ways to do it: right-click a cloud workspace and choose Transfer to local, or use Settings › Account › Export data.2 Your local branches and worktrees are plain git and stay exactly where they are.

-
-

Why GraphCode fits a Conductor workflow

-

The same job, running several coding agents at once on your own Mac, organised as a graph of loops instead of a list of workspaces.

-
-

Native macOS

A Mac app for macOS 15+ on Apple Silicon, Developer ID signed and notarized. Terminals render with GhosttyKit.
-

Live, steerable terminals

Each node on the canvas is a loop running inside a real agent CLI session. Click it to open that session's terminal and type into it mid-run.
-

Your choice of agent, per loop

Claude Code, GitHub Copilot CLI, Codex, OpenCode or pi. A Codex loop can hand off to a Claude Code loop; an edge never asks which agent is on either end.
-

Local daemon and CLI

graphcoded keeps loops alive with the app closed, fires edges and polls goal checks. The graphcode CLI drives the same daemon from a shell or from another loop.
-

Sessions that outlast the app

Every loop's terminal is a zmx session. It survives quitting the app; after a reboot the backend's saved session id is resumed rather than started again.
-

Source-available, free

The app and daemon are FSL-1.1-MIT, converting to MIT two years after each release. The CLI and GraphcodeKit are MIT. There is no paid tier.
+
+ The GraphCode window: a sidebar of projects and loops, and a canvas of loop cards joined by edges, each showing its type, age and status. +
One of my own projects in GraphCode. Each card is a loop running its own agent session, and the lines between cards are edges.
+
+ +
+
+

How GraphCode works

+

Conductor organises work as workspaces, one per branch. GraphCode organises it as a graph. Each node is a loop: a real agent CLI running in a terminal, with a job and a rule for when it is finished. Edges connect loops, so one loop can hand its work to the next when it finishes, send it a message, or spawn a new loop.

+

You choose the agent per loop. GraphCode drives Claude Code, GitHub Copilot CLI, Codex, OpenCode and pi, using the CLIs you already have installed and signed in. It bundles none of them. A Codex loop can hand off to a Claude Code loop, and the edge between them does not care which agent is on either end.

+

Clicking a node opens that agent's actual terminal, rendered with Ghostty's engine. You are typing into the live session, the same interface you would get by running claude or codex yourself, so you can correct it halfway through a task. From a shell, graphcode node send types a message into any loop, and loops use the same command to steer each other.

+

Behind the app sits a small daemon, graphcoded, running under launchd. It keeps loops alive while the app is closed and fires an edge when a loop resolves. Each loop's terminal is a zmx session, so it survives quitting the app, and after a reboot each loop resumes its saved agent session instead of starting over. The graphcode CLI talks to the same daemon. That is how I script it, and how one loop creates another.

+

The app and daemon are licensed FSL-1.1-MIT, and each release becomes plain MIT two years after it ships. The CLI and GraphcodeKit are MIT from the start. GraphCode is free, with no paid tier.

+

Some things it does not do. It needs macOS 15 or later on Apple Silicon. There is no hosted cloud; to run agents on another machine, you add a remote project over SSH and steer it from your Mac. It is single-user, with nothing like Conductor's multiplayer. There is no Cursor backend and no setup scripts for new worktrees. It also has no screen for reviewing a branch's diff and does not open pull requests for you, so that part stays with the agent and your usual git tools.

-

Conductor concepts, in GraphCode terms

-

An honest mapping. Where GraphCode has no equivalent, the row says so.

+
+

Conductor's concepts in GraphCode terms

+

Where GraphCode has no equivalent, the row says so.

+
@@ -224,17 +223,17 @@

Conductor concepts, in GraphCode terms

- + - + - + - + @@ -243,100 +242,81 @@

Conductor concepts, in GraphCode terms

- - + + - + - + - - + + - + - - + + - + - - + +
Workspace "An isolated copy of a project and repository for one task", one workspace to one branch, backed by a git worktree.34A loop: one node on the project's canvas, one live agent session. Its worktree is optional: in the create form pick none (run in the checkout), an existing worktree, or a new branch, which GraphCode creates and later offers to sweep.A loop: one node on the canvas, one live agent session. The worktree is optional. In the create form you pick none (it runs in the checkout), an existing worktree, or a new branch, which GraphCode creates and later offers to clean up.
Repository / projectRepository The repository a workspace is cut from.3A project in the sidebar: a local folder, a clone from a URL, or a repository on a remote host over SSH.A project in the sidebar: a local folder, a clone from a URL, or a repository on a remote host over SSH.
Several agents in one workspace Agents on the same branch in separate tabs.56Several loops in one project sharing a checkout or worktree, or extra tabs and splits inside one loop's terminal workspace.Several loops in one project sharing a checkout or worktree, or extra tabs and splits inside one loop's terminal.
Agent picker
Chat panel and Big TerminalA chat panel per agent session plus a workspace terminal.6The agent's own terminal UI, live, with tabs and splits. graphcode node send types into any loop from a shell or from another loop.A chat panel per agent session, plus a workspace terminal.6The agent's own terminal interface, live, with tabs and splits. graphcode node send types into any loop from a shell or from another loop.
Codex goals (/goal) Keeps a local Codex session working across turns.6A goal-based loop, on any backend. It resolves when the goal is met, optionally decided by a shell check that exits 0 (for example make test).A goal-based loop, on any backend. It resolves when the goal is met, optionally decided by a shell check that exits 0, such as make test.
Plan Mode An agent mode that plans before editing.6The backend's own modes stay available in its terminal. A turn-based loop additionally pauses for your review every turn, or only before writes.The agent's own modes stay available in its terminal. A turn-based loop also pauses for your review every turn, or only before it writes files.
RoutinesAgents on a schedule or from a GitHub Action, run in the cloud.7A time-based loop, run locally. Its cadence lives in its prompt (/loop 1h …); for Codex, OpenCode and pi, switch on the experimental Daemon heartbeat. No GitHub Action trigger.Agents run on a schedule or from a GitHub Action, in the cloud.7A time-based loop, run on your Mac. The cadence lives in its prompt (/loop 1h …); for Codex, OpenCode and pi, switch on the experimental Daemon heartbeat in Settings. No GitHub Action trigger.
Handoffs and .context notes A .context folder in the workspace for notes and handoffs.3Edges between loops (hand-off, message, spawn), a memory log per loop that a relaunched session reads first, and the Mailroom, a board every loop in the graph can post to. Nothing is written inside your project folder.Edges between loops (hand-off, message, spawn), a memory log per loop that a relaunched session reads first, and the Mailroom, a board any loop in the graph can post to. Nothing is written inside your project folder.
Cloud workspacesWorkspaces in Vercel sandboxes that keep running with the app closed; shutting down 20 November.18The local daemon keeps loops running with the app closed. To run on another machine, add a remote project over SSH; loops run there and this Mac steers them. No hosted cloud.Workspaces in Vercel sandboxes that keep running with the app closed. Shutting down on 20 November.18The local daemon keeps loops running with the app closed. For another machine, add a remote project over SSH; its loops run there while your Mac steers them. No hosted cloud.
MultiplayerTeammates prompting a shared cloud workspace in real time.8Teammates prompting a shared cloud workspace together.8 No equivalent. GraphCode is single-user.
Setup scripts, files to copyGitignored files copied into each new worktree; setup scripts for the rest.4No equivalent. GraphCode creates the worktree; ask the loop's prompt to run your setup.Gitignored files copied into each new worktree, with setup scripts for the rest.4No equivalent. GraphCode creates the worktree; put your setup steps in the loop's prompt.
-
-

Migration quickstart

-

About five minutes from install to a running loop. Your existing repositories, branches and worktrees work as they are.

-
    -
  1. Export from Conductor first. Before 13 November if you still want to send messages in the cloud, and before 20 November at the latest: right-click a cloud workspace › Transfer to local, or Settings › Account › Export data.
    2. -
  2. Install GraphCode. macOS 15+ on Apple Silicon, with at least one of claude, codex, copilot, opencode or pi on your PATH. GraphCode bundles none of them, so the CLIs you used under Conductor carry over with their logins. -
    $ brew install --cask scgopi/graphcode/graphcode
    - Or drag GraphCode to Applications from the latest .dmg.
    3. -
  3. Add your repository. The sidebar's ⊕ menu: a local folder (the repo you had in Conductor), a clone from a URL, or a remote repository over SSH.
    4. -
  4. Create your first loop. ⊕ on the canvas. Write the prompt, pick the agent, choose Goal, and give it a done check; the Test button runs the check exactly as the daemon will. To mirror a Conductor workspace, set the worktree to a new branch. From a shell, the same loop is: +
    +
    +

    Moving over

    +

    From install to a running loop takes a few minutes. Your repositories, branches and worktrees work as they are.

    +
      +
    1. Export from Conductor. Do it before 13 November if you still want to send messages in the cloud, and before 20 November at the latest.
      2. +
    2. Install GraphCode with brew install --cask scgopi/graphcode/graphcode, or drag it to Applications from the latest .dmg. You need at least one of claude, codex, copilot, opencode or pi on your PATH; the ones you used with Conductor carry over with their logins.
      3. +
    3. Add the repository you had in Conductor from the ⊕ menu in the sidebar.
      4. +
    4. Click ⊕ on the canvas to create a loop. Write the prompt, pick the agent, choose Goal and give it a done check. The Test button runs the check the same way the daemon will. If you want the Conductor habit of one branch per task, set the worktree to a new branch.
      5. +
    5. Click the node to attach to the live session.
      6. +
    +

    The same loop from a shell, once the project is added:

    $ graphcode node create ~/code/my-repo --title FixBuild --type goal \
-    --goal "the test suite passes" --predicate "make test" --backend codex
    5. -
  5. Open it and steer. Click the node to attach to the live session. Add a second loop and drag an edge between them to hand work on when the first resolves. Close the app; the daemon keeps both running.
    6. -
+ --goal "the test suite passes" --predicate "make test" --backend codex +

Then add a second loop, drag an edge from the first to it, and close the app. The daemon runs the first loop to its goal and hands off to the second without you.

+

Sources

-

Fetched on 7 November 2026. If Conductor's pages change, its own pages win; open an issue on the GraphCode repo and this page gets corrected. The full comparison covers Conductor alongside Vibe Kanban, Claude Squad, Superset, Emdash and Sculptor.

+

Fetched on 7 November 2026. If Conductor's pages change, they win; open an issue on the GraphCode repo and I will correct this page. The full comparison covers Conductor alongside Vibe Kanban, Claude Squad, Superset, Emdash and Sculptor.

  1. conductor.build/announcement, "Conductor is joining Meta", timeline and FAQ.
    2. -
  2. conductor.build/changelog, 0.93.0 "Conductor is joining Meta", 4 November 2026; see also AI Weekly, 4 November 2026.
    3. +
  3. conductor.build/changelog, 0.93.0 "Conductor is joining Meta", 4 November 2026. Reported by AI Weekly the same day.
  4. conductor.build/docs/concepts/workspaces-and-branches.
  5. conductor.build/docs/concepts/git-worktrees.
  6. conductor.build/docs/concepts/parallel-agents.
  7. conductor.build/docs/concepts/agent-modes.
  8. conductor.build/changelog, 0.85.0 "Sections, routines, and a new model picker", 9 September 2026.
    9. -
  9. conductor.build/pricing, plans and the Cloud FAQ, as cited on the comparison page (12 September 2026).
    10. +
  10. conductor.build/pricing, plans and the Cloud FAQ, as fetched for the comparison page on 12 September 2026.
-
- The GraphCode statements are drawn from the shipped code and the README: - -
-
- -
-
-
-

Bring your agents. Keep your Mac.

-

Add the repo you had in Conductor, write a goal, pick the agent. Then close the app; the loop keeps going.

-
- ⬇ Download .dmg - ★ View on GitHub -
-
$brew install --cask scgopi/graphcode/graphcode
-
-
+

The GraphCode statements come from the README and the source: backends in CLISessionBackendKind.swift, loop types in LoopType.swift, edges in EdgeKind.swift, the per-loop worktree choice in ProjectFeatureState.swift, and the licence in LICENSE.