Continue a Claude Code project with a local checkpoint

Save the state the next chat actually needs

A useful checkpoint is shorter than a transcript. Ask the current chat to record the objective, what changed, what was checked and what remains. Include the exact project folder so the next chat does not start in a similar-looking checkout.

Here is a suggested content checklist, not a required command or file format:

• The task and the intended outcome.
• The exact project folder and relevant branch, if the project uses branches.
• The files or decisions that matter for continuing.
• Checks already completed and any unresolved failures.
• The next concrete step and the checkpoint’s short name.

Keep the checkpoint focused on project state. Do not include passwords, API keys or browser cookies. A handoff should not become a way to move credentials between accounts.

Open the same folder, then continue by name

After saving the checkpoint, choose the account and start the next Claude Code chat yourself. Open the exact same project folder and ask the chat to continue from the saved checkpoint’s short identifier or name.

Before making changes, have the new chat confirm the current project state and the next step. Files may have changed after the checkpoint was written, so the checkpoint is context rather than a substitute for inspecting the project.

This workflow works independently of Conductor. It does not require a Conductor workspace, and it does not switch accounts or start the next conversation automatically.

Share useful definitions separately from credentials

A project handoff and a shared tool configuration solve different problems. A checkpoint explains what you were doing. A local skill, command, plugin or MCP definition describes a tool or capability the next environment may use.

Switch supports selective sharing of supported local Claude Code definitions. It does not copy credentials or override existing choices. Select the definitions you want to share instead of assuming every account should have the same setup.

Cloud connectors and reauthorization remain per account. A shared local definition does not mean the next account already has permission to use the corresponding remote service.

Know what a handoff leaves behind

There is no automatic transcript transfer. The next chat receives the compact context you saved, not an automatic copy of the full conversation. Switch also does not automatically choose an account or make model requests on your behalf.

A checkpoint is not a full backup or recovery system. Keep your normal project and version-control practices. Switch does not currently offer a complete import or recovery flow.

For a short task, a few clear notes may be enough. For a larger task, record the important decisions and the evidence behind them so the next chat can distinguish something verified from an assumption. Keep the checkpoint concise enough to read before acting.

See profile keyboard shortcuts for selecting the next account, or return to Switch setup.