> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orchestrahq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Move from Conductor

> Move from the Conductor app to Orchestra: keep your repos, bring your sessions, keep using the same agents

This guide is for people moving off the Conductor Mac app from conductor.build,
which [is winding down](https://www.conductor.build/changelog/0.93.0-conductor-is-joining-meta).

## The dates

| Date | What happens |
| - | - |
| November 4, 2026 | Meta acquires Conductor. New Conductor sign-ups close. |
| November 13, 2026 | Conductor Cloud goes read-only. |
| November 20, 2026 | Conductor Cloud shuts down, and its cloud data is deleted. |
| Early 2027 | The Mac app stops getting new models and critical fixes, and winds down. |

## What to do before November 13

**1. If you use Conductor Cloud, save your work**

In Conductor, right-click each cloud workspace and choose **Transfer to
local**. Then download your data at **Settings**, **Account**, **Export
data**. Do both before November 13, while you can still change things.
After November 20 the cloud copy is gone. Conductor's announcement has the
details.

**2. If you only use the Mac app, there is no rush**

The local app keeps working, with new models and critical fixes, until
early 2027. Move when it suits your team.

**3. Install Orchestra and turn it on**

Follow [Move your sessions](#move-your-sessions) below. It takes one
command and a free account, and your past Claude Code and Codex sessions
come with you.

**4. Know what does not move**

Read [What does not move](#what-does-not-move) before you remove anything
from Conductor.

## What Orchestra does today, and what is coming

Today, Orchestra Local turns your team's Claude Code and Codex sessions into
shared memory that cites where each piece came from, so every agent starts
with what the team already decided. It runs on your own machines by default.

Coming, and not shipped yet: cloud runs that open pull requests, a phone app,
and an importer for Conductor's own history. This page will say when each one
ships.

## Move your sessions

Claude Code and Codex keep their sessions in `~/.claude` and `~/.codex`, and
Conductor's docs say the same of the sessions it runs. Orchestra reads them from
there, so leave those folders in place.

**1. Install Orchestra**

Download [the desktop app](https://docs.orchestrahq.ai/install-desktop.md), or install the CLI:

```bash theme={null}
curl -fsSL https://get.orchestrahq.ai | sh
```

Then `orchestra login` signs you in, or creates your free account. See
[Install the CLI](https://docs.orchestrahq.ai/install-cli.md).

**2. Turn it on in your main checkout**

Run this in the repository's main folder, not in a folder under
`~/conductor/workspaces`:

```bash theme={null}
orchestra enable
```

It also brings in the last 30 days of sessions from that repository and its
worktrees, which is what a Conductor workspace is.

**3. Bring in older sessions**

See what it found, then bring it in:

```bash theme={null}
orchestra import --all
orchestra import --all --yes
```

`orchestra import --status` shows progress.

**4. Check it worked**

Ask for something you remember from an old session:

```bash theme={null}
orchestra recall "the retry limit"
```

## Keep working after you move

Use the same agents, from your main checkout or from worktrees. New sessions are
saved as they happen, Claude Code and Codex alike.

A worktree git creates after you ran `enable`, by you or by Conductor, gets the
same hooks as the main checkout, so its Claude Code sessions also start with your
team's context, and their commits name the session that made them. A workspace
Conductor made before that has no hooks; its sessions are still saved as they
happen, and with sharing on each one is published once it has been quiet for
three minutes. Running `orchestra enable` inside that workspace gives it the
hooks too.

## What moves

* Your repositories and branches. They are ordinary git, so nothing changes.
* Your past Claude Code and Codex sessions, from workspaces on disk and from
  workspaces you have since removed.
* Your agents' own logins and settings, which stay where they are.

## What does not move

* Chats that exist only in Conductor Cloud. Use **Transfer to local** first.
* Possibly Cursor and OpenCode sessions started inside Conductor. Run
  `orchestra import --all` to see what it found before you rely on them.
* Diff comments, workspace notes and other data held in Conductor's own app. Orchestra
  does not read it, or the export file.

Questions go to [contact@orchestrahq.ai](mailto:contact@orchestrahq.ai).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.