Coming from Conductor
Conductor is joining Meta and winding down. Conductor Cloud shuts down on November 20, 2026, and the Mac app stops getting updates in early 2027. If you used it, you already know how Ouijit works. Each task gets a git worktree and an agent. Here's how the pieces line up.
Why Ouijit
The agent runs as its own CLI in a terminal, in the task's worktree, so Claude Code, Codex, Pi and OpenCode work exactly as they do anywhere else.
Every agent gets the ouijit command. Ask it to split a feature into
tasks and it starts them, each with its own agent. It can read the other agents' terminals, open its plan
beside itself, link you to the line it changed, and stage review comments for you to send.
A task can run in a sandbox, so an agent with permission checks off is held to its worktree. Ouijit is free, open source, and runs on macOS and Linux.
What maps to what
A hook is a command the project runs when a task changes status. The start hook runs in the new worktree
with the task's prompt in $OUIJIT_TASK_DESCRIPTION, and the done hook runs when the task is
marked done. Both live under Project Settings → Lifecycle Hooks.
| Conductor | Ouijit |
|---|---|
| Project | Project |
| Workspace | Task. Starting it creates the worktree. |
| Workspace name (a city) | Task number, such as T-42. It names the branch and the worktree folder. |
| Base branch | Branch from, in Project Settings → Worktree |
| Setup script | Start hook. It runs in the new worktree when the task starts, and usually launches your agent. |
| Actions and the Run button | Scripts, under Run Commands. Each runs in a runner panel beside the terminal. |
| Archive script | Done hook |
| Files to copy | Quick start, the default worktree mode, which copies every gitignored file into the worktree |
| .conductor/settings.toml | Project Settings in the app. Ouijit keeps them outside the repository. |
| CONDUCTOR_WORKSPACE_PATH | OUIJIT_WORKTREE_PATH |
| CONDUCTOR_ROOT_PATH | OUIJIT_PROJECT_PATH |
| CONDUCTOR_WORKSPACE_NAME | OUIJIT_TASK_BRANCH |
| CONDUCTOR_PORT | None. Pick ports in your scripts. |
| Diff viewer | Diff review, with notes the agent reads |
| conductor:// links | ouijit:// links |
| MCP server | The ouijit CLI, which every agent in Ouijit already has |
| Checks, Todos, Checkpoints | None |
| Conductor Cloud | Not yet. Ouijit runs on your machine today; hosted workspaces are on the roadmap. |
What you give up
- Conductor Cloud, shared workspaces and the iOS app, for now. Ouijit runs on your machine today; hosted workspaces and a phone app are on the roadmap.
- Cursor models. Claude Code, Codex, Pi and OpenCode get live status and the
ouijitcommand; any other CLI still runs in an Ouijit terminal. - Checks, Todos and Checkpoints. Review is the diff, the notes you leave on it, and the pull request.
- Ports per workspace. Pick ports in your scripts.
- Settings committed to the repository. Ouijit keeps a project's hooks and scripts itself.
Move a project over
- Install Ouijit and open the repository as a project.
- Under Project Settings → Lifecycle Hooks, put your setup script and your agent command in the start hook, for example
npm install && claude "$OUIJIT_TASK_DESCRIPTION". - Add each action under Project Settings → Run Commands.
- Under Project Settings → Worktree, set Branch from if your workspaces branched from something other than the checked-out branch, and leave the mode on Quick start if you relied on Files to copy.
- Press
⌘Nfor a task, give it a prompt and start it. The start hook runs in its new worktree.