Conductor is joining Meta. Conductor Cloud goes read-only on November 13, 2026, and shuts down on November 20, when Conductor begins deleting cloud user data. This guide moves your team into Coshell: save your work first, then set up a drive and bring your repositories and branches over.
Updated . Dates from Conductor's announcement and changelog 0.93.0.
Cloud workspaces go read-only on November 13, and Conductor begins deleting cloud data on November 20. Do the git work first, while workspaces still take new messages.
In each cloud workspace, commit what's in progress to a branch, even if it's half done, and push it to your own remote: git add -A && git commit -m wip && git push -u origin HEAD. Check git stash list too, because a stash doesn't travel with a push.
To move a cloud workspace and its chats to your Mac, right-click it and choose Transfer to local. To download an archive of all your Conductor data, go to Settings → Account → Export data. Export still works while workspaces are read-only; Conductor asks you to export before November 20.
Copy each repository's setup script, and its run and archive scripts if it has them. Unless the repo has a .conductor/settings.toml, they live in Conductor's settings, not in git, and so do the install script and environment variables under Settings → Cloud computer. Conductor hides secret values once they're saved, so take those from wherever you keep the originals.
Sign up, then choose New drive on Home. It asks where the drive should run. Both kinds run the same Coshell: several people prompt the same live agent session, and a drive runs as many agents and sessions as your team wants.
Nothing to install: Coshell runs the machine. Your team opens the drive from a browser, the CLI, VS Code, or a phone.
Run the two commands the dialog shows on a laptop, a Mac mini, a VM, or a container: the installer, then coshell host init. The drive connects out, so there are no inbound ports to open.
This is the manual path, and it works today. Connect GitHub once, then repeat the project steps for each repository.
To let drives clone and push, an org admin installs the Coshell Drives app on your GitHub organization from Settings → GitHub. Then each teammate connects their own account under Settings → Profile, so their commits carry their name and pull requests open as them.
On Home, open the drive's … menu and choose Add project, then Clone from GitHub. Pick the repository and click Clone. Coshell clones it onto the drive and opens it as a project, with every branch you pushed in step 1.
On Home, open the project's … menu and choose Rename project. In the Edit project dialog, paste your Conductor setup script into Workspace startup script and click Save. Coshell runs it with bash in each new worktree, from that worktree's folder.
Coshell doesn't set the CONDUCTOR_* variables, so for now, edit any line that uses them. For $CONDUCTOR_WORKSPACE_PATH, use the current folder, $PWD. For $CONDUCTOR_ROOT_PATH, the project's main checkout, add ROOT="$(git worktree list --porcelain | head -n1 | cut -d' ' -f2-)" and use $ROOT. Coshell assigns no port range, so give anything that read $CONDUCTOR_PORT a port of its own.
Start a new session in the project, then open the branch picker under the prompt. Pick a branch you pushed and turn on Run in a new worktree, so the session gets its own folder the way a Conductor workspace did. The startup script runs there. If you pushed after cloning, run git fetch in a session's Terminal first.
Model keys go in the drive's Manage drive dialog, from its … menu on Home: on the Providers tab, connect a provider or add the key under Custom variable (this drive only). Put other variables your app reads in a .env file in the project's main folder, keep it out of git, and add cp "$ROOT/.env" .env to the startup script so each worktree gets a copy. On a self-hosted drive, you can instead run coshell host env <slug> KEY=VALUE on the host, which sets the variable for the whole drive and restarts it.
In Settings, go to Organization → General and click Invite. Enter each teammate's email, then choose their role and drives. To let anyone with the link join instead, click Create join link on the same page.
To show the work to someone outside the team, open the … menu next to the session's title and choose Share, then Publish. Anyone with the link sees a read-only copy until you click Unpublish.
| Conductor | Coshell | |
|---|---|---|
| Workspace | Its own worktree and branch, one per task | A session on its own branch; Run in a new worktree gives it its own folder |
| Cloud computer | Conductor's cloud machine, set up with an install script | A drive on Coshell Cloud, or on a machine you run |
| Setup script | Runs after a workspace is created | Workspace startup script, which runs in each new worktree |
| Run script | Starts the app from the Run button | No equivalent yet. Start the app in a session's Terminal. |
| Archive script | Runs before a workspace is archived | No equivalent yet |
| Environment variables | CONDUCTOR_* variables, plus your own in Cloud computer settings | Model keys under Manage drive → Providers; app variables in a .env on the drive. No CONDUCTOR_* variables. |
| Share link | Copy link opens a cloud workspace for anyone in your organization | Teammates open the same session, as its Visibility allows; Share → Publish makes a read-only public link |
| Multiplayer prompting | Cloud workspaces are shared with your organization, and chat updates live for everyone | Several people prompt the same live session, and every prompt carries who sent it |
| Checkpoints | Revert the chat and files to an earlier turn | /undo and /redo roll the session and the agent's file changes back and forward |
| Diff comments | Line comments in the diff viewer | Comment on lines in the Changes tab; the comment goes to the agent with your next prompt |
| Archive | Archiving deletes the workspace's folder | Archive hides a session or project from your own lists; nothing is deleted |
| Mobile | iOS app | The web app, in a phone's browser |
| Harnesses and models | Claude Code, Codex, Cursor, and OpenCode, on your keys | 70+ models on your keys, including a Claude Pro or Max subscription |
A few habits change when the whole team works on the same drive. For the longer comparison, read Coshell vs Conductor.
Parallel work runs as sessions on the same drive, each on its own branch, and a drive runs as many agents and sessions as your team wants. Turn on Run in a new worktree when two tasks shouldn't share a folder.
A teammate opens your session and prompts the same live agent, and every prompt carries who sent it. To keep a session to yourself or a few named teammates until it's ready, change its visibility.
When two sessions take on the same concern, the overlap layer flags it while the work happens. It holds the second edit until an arbiter has read both changes and told that agent how to proceed.
Sessions and their history stay on the drive between visits, so a teammate in another time zone resumes the session itself instead of starting over. A Coshell Cloud drive sleeps when idle and wakes when someone opens it.
Conductor Cloud goes read-only on November 13, 2026, and shuts down on November 20, 2026, when Conductor begins deleting cloud user data. The dates are from Conductor's announcement.
Not if it's pushed to your own git remote. Uncommitted files and unpushed branches exist only inside the cloud sandbox, and Conductor begins deleting cloud data on November 20. Push every branch before November 13, when workspaces go read-only.
The setup script does, once it's in the project's Workspace startup script and any CONDUCTOR_* variables are replaced as step 3 describes. Coshell has no run or archive scripts yet, so start your app from a session's Terminal.
Yes. A drive holds as many sessions as you want, each with its own agent, and a session can start on its own branch or in its own worktree. The difference is that teammates can be in the same session at once, and overlapping work is watched across sessions while it happens.
For now, yes. Conductor says local Conductor keeps working and gets new models and critical bug fixes until early 2027, when it starts winding down. New users can no longer sign up or download it.
No. Coshell runs in the browser, and you can also attach from the CLI, VS Code, or a phone. A self-hosted drive can run on your Mac, so the code stays on the machine it already builds on.
Yes. A drive can run a Claude Pro or Max subscription through the Claude Code binary, alongside 70+ models on your own keys.
Self-hosting is free, with no seats, and Enterprise is paid. Coshell Cloud, where Coshell runs the machine for you, is a paid plan you can choose when you create a drive.
Your code lives in your own git repositories, so nothing is locked inside Coshell. Self-hosted drives run on machines you control, and their files stay there.
Push your branches and export your Conductor data, then start a drive on Coshell Cloud or your own machine.