Moving from T3 Code Orchestrator V1 to V2
T3 Code Orchestrator V2 is SOON (est. 3am UTC) out in nightly builds. This issue explains what happens to your data, what you need to update, and where to report problems. We'll keep it updated as V2 moves toward a stable release.
What happens to your threads
The first time a V2 server starts, it copies your V1 database (state.sqlite) to a new file (statev2.sqlite) in the same data folder and migrates that copy. Your threads appear on their own; there's nothing to import by hand. Large histories may fill in over a few moments while transcripts are imported.
Carried over:
- titles, projects, and provider and model choices;
- permission and interaction modes;
- branches and worktrees, archive, pin, snooze, and settled state, and linked pull requests;
- user and assistant messages, with timestamps and supported attachments.
Not carried over:
- the provider's live session;
- old checkpoints and diffs, tool activity, approval history, and proposed plans.
The conversation text is there, but those items won't appear in the migrated timeline.
Continuing an old thread: your first new message starts a fresh provider session. T3 Code hands the new session as much of the old conversation as fits the context budget, and the agent can look up the rest. For a long or important thread, skim the recent history and restate anything the agent must not forget, or start a new thread with a short summary.
V1 and V2 side by side: V1 keeps using state.sqlite, so you can keep it installed. The copy happens once. After that, new conversations in either version stay in that version. Settings, attachments, and project files are shared.
Update every app you connect with
A V2 server and a V1 app can't talk to each other. Whichever side is older refuses the connection and tells you which machine to update.
-
Desktop and web: update every machine that runs a T3 Code server, including background services and remote machines you connect to, and every desktop app you use.
-
Mobile: the App Store and Play Store releases are still V1 and can't connect to a V2 server. For a V2-compatible app:
Mobile store releases will move to V2 when V2 reaches stable.
Check your providers
T3 Code shows an advisory in Settings → Providers when a provider version is too old or untested.
| Provider |
V2 needs |
| Codex |
0.159 or newer |
| Claude Code |
2.1.280 or newer |
| Cursor |
a CLI build from 2026-05-09 or newer |
| Grok |
1.0.13 or newer |
| OpenCode |
2.0.18 or newer (1.x has limited support for new orchestrator features) |
| Pi |
0.80.5 or newer, 1.0 recommended |
| Antigravity |
1.1.1 |
OpenCode 1 → 2: OpenCode 2 is a separate package, @opencode/cli. It converts OpenCode's shared database the first time it runs, so don't run 1.x and 2.x side by side on the same machine.
What's new
See the release notes for everything. The big ones:
- OpenCode 2, Pi, and ACP Registry agents.
- Subagents and background work you can see, and that Stop actually ends.
- Steer or queue, with a server-side queue.
- Switching providers mid-thread, plus native fork and rollback.
- Threads without a project.
- MCP tools for agents.
- Scheduled tasks and usage-limit handling.
Moving from T3 Code Orchestrator V1 to V2
T3 Code Orchestrator V2 is SOON (est. 3am UTC) out in nightly builds. This issue explains what happens to your data, what you need to update, and where to report problems. We'll keep it updated as V2 moves toward a stable release.
What happens to your threads
The first time a V2 server starts, it copies your V1 database (
state.sqlite) to a new file (statev2.sqlite) in the same data folder and migrates that copy. Your threads appear on their own; there's nothing to import by hand. Large histories may fill in over a few moments while transcripts are imported.Carried over:
Not carried over:
The conversation text is there, but those items won't appear in the migrated timeline.
Continuing an old thread: your first new message starts a fresh provider session. T3 Code hands the new session as much of the old conversation as fits the context budget, and the agent can look up the rest. For a long or important thread, skim the recent history and restate anything the agent must not forget, or start a new thread with a short summary.
V1 and V2 side by side: V1 keeps using
state.sqlite, so you can keep it installed. The copy happens once. After that, new conversations in either version stay in that version. Settings, attachments, and project files are shared.Update every app you connect with
A V2 server and a V1 app can't talk to each other. Whichever side is older refuses the connection and tells you which machine to update.
Desktop and web: update every machine that runs a T3 Code server, including background services and remote machines you connect to, and every desktop app you use.
Mobile: the App Store and Play Store releases are still V1 and can't connect to a V2 server. For a V2-compatible app:
Mobile store releases will move to V2 when V2 reaches stable.
Check your providers
T3 Code shows an advisory in Settings → Providers when a provider version is too old or untested.
OpenCode 1 → 2: OpenCode 2 is a separate package,
@opencode/cli. It converts OpenCode's shared database the first time it runs, so don't run 1.x and 2.x side by side on the same machine.What's new
See the release notes for everything. The big ones: