How to Continue Claude Code on Another Computer
Direct answer: For a real move between computers, bring the correct code checkout and a reviewed handoff of your decisions, progress and next step. Multiplist gives connected Claude sessions a shared place to retrieve that saved context. If you only need another screen for the same running session, Claude Code's Remote Control may already meet your need.
You finished the difficult part: understanding the problem, choosing an approach and figuring out what still needs work. Then you open your laptop and have to explain it all again. Having the files is useful. Having the reasons behind them makes it easier to continue.
Save those reasons in Multiplist, your portable memory vault. A short handoff gives your next connected session a source to consult before it starts making changes. Multiplist supports saving documents, finding saved sources and reading their content; choose what you want to carry forward. Multiplist tools
The link fills in the connector details in Claude. Complete sign-in and authorization, then enable it where you work. In Claude Code, check /mcp for the account connector when your active authentication is a Claude subscription login. An API key or another active authentication method can change availability. Team and Enterprise administrators manage account connectors, and some sessions, including Desktop WSL, do not support them. Follow the current Claude Code connection guidance if it is missing. Opening the link alone does not establish every terminal's connection.
# Save the handoff while the work is fresh
Imagine you are correcting a setup guide on your desktop and want to finish on your laptop. The wording is almost settled, but one command still needs checking. A useful handoff preserves that distinction: what is approved, what was actually tested and what remains uncertain.
Use a short note like this, replacing the examples with your own facts:
Project: Setup guide correction
Updated: Date and time, with timezone
Repository, branch and commit: Exact checkout to continue from
Goal: Help a new reader complete the connection successfully
Decision: Keep the existing sign-in steps; explain connector enabling separately
Completed: Revised the introduction and checked the linked documentation
Checks run: List commands and results, or say "not run"
Still open: Confirm the terminal setup command on the supported version
Next step: Verify that command before changing the example
Supporting sources: Relevant document links and file pathsThe note should make the next action clear without retelling the whole afternoon. Include enough evidence to check important decisions. Leave out credentials, tokens and material you are not authorized to store. Multiplist is a hosted service; review its privacy policy when deciding what to save.
# Continue on the second computer
- Review and save the handoff. Give the Multiplist source a recognizable title and date. Confirm the saved content includes the decisions and open questions you need.
- Bring the actual code separately. Use your normal reviewed version-control process to make the intended branch and commits available. Check for uncommitted work on the first computer; a handoff note does not transfer those file changes.
- Prepare the destination. Open the correct repository, check the branch and commit, and establish the tools and authorized access needed for the task. Confirm Multiplist is available in that Claude Code session.
- Retrieve before editing. Ask Claude to read the named handoff, identify its date and compare its claims with the checkout. Resolve any mismatch before proceeding.
- Keep the record current. After meaningful progress, save an updated handoff that clearly identifies what it supersedes.
For example:
Find my latest “Setup guide correction” handoff in Multiplist and read the supporting source. Tell me the intended branch, the unresolved check and the next action. Compare them with this checkout before editing. If the source is missing or conflicts with the files, explain the gap instead of guessing.
If Claude cannot find it, check the source title, saved content, account and connector status. A plausible recap is not proof that the right record was retrieved.
# Choose the native option that fits your move
Platform facts checked October 9, 2026.
| What you want to do | Useful starting point | What to check |
|---|---|---|
| Use another screen while work stays on the original computer | Remote Control | Original computer stays on and Claude keeps running |
| Run the project on a different computer | Correct checkout plus a saved handoff | Files, tools, access and retrieved decisions agree |
| Bring an existing cloud task into a local terminal | Cloud-to-local teleport | Account, repository, branch and working-state requirements |
| Reopen a conversation stored on this computer | claude --resume | The local history contains the session |
Remote Control keeps execution on the original computer. From an existing Claude Code session, /remote-control starts the connection flow; open its session link on your other device after the confirmation. It is available on Pro, Max, Team and Enterprise, with Owner enablement required for Team and Enterprise. API-key-only access and some organization configurations are not supported. If you want to keep using that machine's files and tools, this can be enough. Remote Control documentation
Teleport applies to an existing cloud session. claude --teleport brings it into a local terminal using the same Claude account and repository. The local working state must be clean and the cloud branch pushed. The resulting local continuation is separate; later local changes do not automatically appear in the cloud session. Check the eligible subscription and organization requirements before using it. Cloud session documentation
Resume uses local history. Signing into another computer does not by itself transfer the first machine's local conversation. Use /export if you need a readable transcript, and review it before saving or sharing it. A concise handoff can be easier to act on than a complete transcript. Session documentation
# Give project instructions and portable context different jobs
Project instruction files such as CLAUDE.md can travel with the repository. They are useful for lasting conventions, build commands and project guidance. Claude Code auto memory is stored locally and is not shared across computers or cloud environments. Claude Code memory documentation
Use the handoff for what changed today: why you chose this approach, which checks passed and where to begin next. Keep the durable project rules with the code, and the selected knowledge you want connected tools to retrieve in your vault. Native continuity may cover your immediate task; a saved Multiplist source gives you a record you can also return to when the session or tool changes.