Migrate an entire T3 Code environment to another machine

[jayb029]

Problem

I want to move my entire local T3 Code environment to a different machine or T3 environment and continue working there with my existing setup. Moving one thread or copying one project is not enough. I mean all projects, conversations, settings, and the supporting state needed to keep using them.

For example, I might replace my laptop or move my local setup to an always-on server. Today I cannot find a supported workflow that transfers the whole environment and explains what will carry over, what needs reconfiguration, and whether the destination is ready to use.

Proposed workflow

Add an Export / migrate environment action, with a matching import flow on the destination. A direct transfer between connected environments would also be useful.

The workflow should:

• Inventory all projects and threads, conversation history and attachments, project and environment settings, provider configurations, schedules, and other persistent T3 state. Explain what can be transferred and what cannot.
• Include project files and Git/worktree state when requested, including uncommitted changes and untracked files. Let the user choose how to handle ignored files such as .env and regenerable dependencies.
• Map source workspace paths to destination paths and update references, so imported projects and conversations point to usable checkouts.
• Preserve provider-native conversation state where supported. Clearly identify threads that require a fresh provider session using their existing conversation history instead.
• Check destination compatibility and report missing provider CLIs, tools, MCP configuration, dependencies, or authentication. Offer explicit choices for sensitive configuration; do not silently copy credentials or assume machine-bound secrets will work elsewhere.
• Capture a consistent snapshot after active work has paused or stopped. Running processes and live services do not need to migrate, but their limitations should be clear.
• Import into a fresh destination environment initially, avoiding accidental overwrites or merging unrelated histories. Handle environment identity and connections explicitly so the two machines are not accidentally treated as the same live server.
• Show progress, validate the imported state, and give a final report of transferred items and anything requiring attention. Keep the source intact until the user has verified the destination, with a clear final handoff step.

The intended outcome is that I can retire the old environment and continue from the new one without manually rebuilding every project and conversation. A first version could support offline export/import into a fresh environment on the same OS, with unsupported items reported rather than silently skipped.

Related discussions

• #7838: Cross-device continuity discusses shared workspace identity and state across machines.
• #6874: Transfer a provider-native session focuses on an individual session.
• #10828: Set up a project on another machine focuses on project files and settings.

This proposal asks for a complete, one-time environment migration. Ongoing synchronization and live process migration can remain outside the initial scope. This is a feature proposal; no implementation or verification results are being claimed.

Disclosure

Proposed with GPT 6.1 Sol in T3 Code.