Scape

Moving from Conductor

Moving off Conductor? Bring your setup to Scape.

Conductor is joining Meta. If you run your coding agents in Conductor, here’s what changes and when, and how to move your repos, workspaces and scripts to Scape.

What’s changing, and when

From Conductor’s announcement:

  • November 4, 2026: New users can no longer sign up or download the app. Existing Pro users keep Pro features for free.
  • November 13, 2026: Conductor Cloud goes read-only: you can read old chats and export data, but not send new messages. Active subscribers get a refund.
  • November 20, 2026: Conductor Cloud shuts down and deletion of cloud user data begins.
  • Early 2027: The local app gets new models and critical bug fixes until early 2027, then starts winding down. All Conductor user data is deleted when the app shuts down. No exact date has been announced.

Axios reported that the team will join Meta Superintelligence Labs.

If you use Conductor Cloud

Move or export it before November 13. Conductor’s announcement gives two ways: right-click a cloud workspace and choose Transfer to local to bring it and its chats to your Mac, or go to Settings → Account → Export data for an archive of everything. If you need help, Conductor asks you to write to support@conductor.build.

New downloads have stopped too, so Conductor can’t be reinstalled from their site. If you’re moving to a new Mac, their FAQ explains how to carry it over.

What carries over

The way you work now fits Scape without much change. Each agent gets its own git worktree, so parallel sessions never touch each other’s files. You keep your agents: Conductor ran Claude Code, Codex, Cursor and OpenCode, and Scape runs all four, plus Copilot, pi, omp and Kimi Code, on the subscriptions you already pay for (see harnesses). And it runs on your Mac: your code and sessions stay there, and notes sync through your own iCloud.

What Scape adds

Conductor gave each agent a workspace. Scape helps with the rest of the job:

  • Hand an Argus the whole job. Give it the goal and your guardrails. It starts your agents with the routine permissions already granted, checks on them, and only brings you the decisions that are yours to make.
  • Solve the problem in front of you. Ask your agents for a Custom App, a playbook or a table that does the job: a morning incident triage, a launch tracker that refreshes itself on a schedule, a report that lands in your notes. Code is only part of the work.
  • Let your agents talk to each other. Put Claude and Codex in one room to argue out a fix while you read along, or have one session hand work to another. Any agent, any model, on the subscriptions you already pay for.
  • Work with your team, privately. Bring your whole team and everyone’s agents into a Flight Plan. Each open question is a thread, the answers land in the doc as decisions and tasks, and a task can go straight to an agent. Talk in end-to-end encrypted rooms: messages aren’t stored on a server, and you can run the relay yourself.
  • Own your AI setup. Your apps, playbooks and tables live on your Mac, and your notes sync through your own iCloud. Switch the agent or model underneath them whenever you like, and everything you built keeps working.

After the 14-day trial, Scape needs a subscription. If you cancel later, the versions you had keep working, but Argus and triggers pause, and playbooks, tables, Flight Plans and Custom Apps become read-only.

Move your setup

There’s no importer. Your repos and branches are plain git, so there’s little to import. What needs moving is your setup: the scripts Conductor ran for you, and the list of workspaces you had open.

The quickest way is to let an agent do it. Pick one of the two prompts below. Either way, the agent does the setup and you check what it made. It runs on your own agent subscription.

Two steps are yours either way, because no agent tool can do them:

  1. Paste the hook script into Settings → Developer Tools → Worktrees: choose Add Override… and pick this repo. A hook is stopped after 120 seconds by default; raise the timeout there if your installs take longer.
  2. Save the dev server as a link in the sidebar (Add Link, or Save Link from its open tab) with the script, port and repo.

Option A: run it in Scape

  1. Download Scape and start the trial. 14 days free, no account, no card.
  2. Add your repo as a project, then start an agent session in it.
  3. Paste this prompt.
Paste into a Scape agent
I'm moving this repo from Conductor to Scape. Set up the Scape version of my Conductor setup, then tell me what you did and what's left for me.

1. Find my Conductor setup for this repo: first `.conductor/settings.toml` and `.conductor/settings.local.toml` in the repo, and `~/.conductor/settings.toml`; if there's no settings.toml, the older `conductor.json` in the repo root. Workspaces usually live in `~/conductor/workspaces/<repo>/<workspace>`. Read the setup, run and archive scripts if there are any. Don't change or delete anything of Conductor's. If you can't find a Conductor setup, tell me where you looked and stop.
2. Run `git worktree list`. For each worktree, tell me its branch and whether it has uncommitted or unpushed work. Don't remove any worktree.
3. Rewrite the setup script as a Scape worktree hook. The hook is a bash script I paste into Scape's Settings, not a file in the repo, so don't add it to the repo. Scape runs it inside each new worktree with WORKTREE_PATH, REPO_PATH and BRANCH set. CONDUCTOR_WORKSPACE_PATH becomes WORKTREE_PATH and CONDUCTOR_ROOT_PATH becomes REPO_PATH. The hook gets no port; anything that needs CONDUCTOR_PORT belongs in a dev server, which gets $PORT. If Conductor copied gitignored files into each workspace (such as .env.local), do that in the hook.
4. For each run script (Conductor calls them actions), start it with Scape's start_dev_server tool in this repo's folder. Use $PORT in the script instead of CONDUCTOR_PORT or a fixed port. Pass a different port for each action and its http://localhost URL; Scape sets $PORT to that port, or moves it if the port is busy. Check that each one comes up. Scape gives each dev server one port; if a script uses CONDUCTOR_PORT+1 or higher, tell me.
5. Make a Scape note called "Moving from Conductor" with: the hook script, each dev server's title, script, URL and port, the archive script if there is one (Scape has no archive hook, so I'll run it by hand), the worktree list, and what I still need to do by hand.

Ask me before anything that deletes files, pushes, or rewrites git history.

Option B: start it in Conductor

Your Conductor agent already knows your setup. This prompt has it write a handoff file, then open the repo in Scape with a Scape agent that finishes the move. The handoff goes in the repo’s git folder, so it can’t be committed by accident.

Before you paste it:

  1. Install Scape and start the trial.
  2. In Scape, choose Help → Install ‘scape’ Command in PATH. macOS asks for your password once, which is why the agent can’t do this step. The scape command is in beta.
  3. If you don’t use Claude Code, change claude-code in the prompt to your agent: codex, opencode, pi, omp, copilot, cursor, kimi. It has to be installed and signed in.
Paste into your Conductor agent
I'm moving this repo to Scape. Write a handoff for the Scape agent, then open Scape.

1. Collect my Conductor setup for this repo: first `.conductor/settings.toml` and `.conductor/settings.local.toml` in the repo, and `~/.conductor/settings.toml`; if there's no settings.toml, the older `conductor.json` in the repo root. Workspaces usually live in `~/conductor/workspaces/<repo>/<workspace>`. Copy the setup, run and archive scripts in full, and list every workspace with its path and branch (`git worktree list`). Note any workspace with uncommitted or unpushed work. Don't change anything. If you can't find a Conductor setup, tell me where you looked and stop.
2. Write all of that to scape-handoff.md in the repo's git directory (the path `git rev-parse --git-common-dir` prints), so git never tracks it. Leave out secrets and the contents of .env files.
3. Run this from the repo's main checkout (the first path `git worktree list` prints):
   scape open . --agent claude-code --prompt 'Read scape-handoff.md in the folder that git rev-parse --git-common-dir prints, and finish my move from Conductor: turn the setup script into a Scape worktree hook (CONDUCTOR_WORKSPACE_PATH becomes WORKTREE_PATH, CONDUCTOR_ROOT_PATH becomes REPO_PATH), start each run script with start_dev_server on $PORT, and put the hook, the dev server details and my to-do list in a Scape note called Moving from Conductor.'

If the scape command isn't found, tell me to choose Help → Install 'scape' Command in PATH in Scape. Exit code 3 means Scape didn't answer, so try once more. Exit code 4 means Scape refused to start the agent and printed why; tell me what it said.

Check what it made

Open the note called Moving from Conductor. Read the hook script before you paste it into Settings: it runs in every new worktree. Then make one new worktree and watch the hook run, and open the dev server from the sidebar to see it come up.

Or do it by hand

  1. Add your repos. Add each repo to a Scape project, or run scape ~/path/to/repo once the scape command is installed.
  2. Your workspaces show up. Conductor workspaces are ordinary git worktrees, usually in ~/conductor/workspaces/<repo>. Scape lists every worktree that git worktree list knows about, so they appear under the repo. Push the branches you care about, so your work doesn’t depend on that folder. New Scape worktrees go in .worktrees/<branch> inside the repo, which Scape keeps out of git for you.
  3. Setup script → worktree hook. Your setup script is in .conductor/settings.toml, or conductor.json in older repos. Paste it into Settings → Developer Tools → Worktrees, globally or as an override for one repo. It runs in the new worktree. Change CONDUCTOR_WORKSPACE_PATH to WORKTREE_PATH and CONDUCTOR_ROOT_PATH to REPO_PATH; BRANCH is set too. If Conductor copied gitignored files like .env.local into each workspace, copy them in the hook. See worktree hooks.
  4. Run actions → dev servers. Add one link per action with Add Link in the sidebar: URL, script, port and repo. Use $PORT where the script had CONDUCTOR_PORT. Each worktree gets its own port, so several can run at once. Conductor gave each workspace ten ports; a Scape dev server gets one. See dev servers.
  5. Archive script. Scape has no hook that runs before a worktree is removed. Keep the script and run it yourself when you clean up.
  6. Pick your default agent in Settings → Agents, or choose one per session when you press ⌘N.

Want the side-by-side? See Scape vs Conductor.