Sign in

Move Claude Code to the cloud mid-task

Updated

Move a running Claude Code conversation from your laptop to your box with one command, close the lid while it keeps working, and bring it back: the steps, what moves and what stays, and when it refuses.

On this page6

prized teleport moves the Claude Code conversation running on your laptop to your box, mid-task. Claude Code stops on your laptop and resumes on the box with its full history and your uncommitted edits, so it keeps working with the lid closed. prized teleport back brings it home.

1. Get a box

Sign up: the tour starts a box on $30 of free credit and gives you the command that installs the CLI (Quickstart). Teleport needs prized v0.21.12 or later on your laptop. Already have an older CLI? Update it:

prized update

2. Move the conversation

In the Claude Code session you want to move, press Esc to break off the step it is on (Claude Code holds a ! command until its turn ends), then type:

! prized teleport -y

Or run prized teleport from another terminal in the project folder; it asks before it syncs the folder. Claude Code on your laptop closes, and the conversation resumes on the box in a tmux session named claude, in the permission mode it was in, with the model and tool flags you started it with. Claude Code there is told it moved, checks what finished of the step it was cut off on, and carries on.

With the box awake, a move takes a few seconds, longer for a long conversation; a paused box wakes first, which usually adds 20 to 30 seconds. If the folder isn't synced yet, teleport also sets up its sync, which takes longer. If Claude Code isn't signed in on the box, teleport run from a terminal offers to copy your sign-in there (Credentials); inside Claude Code, run prized agents handoff claude first.

3. Close the lid

The box keeps working. Look in from your laptop:

prized ssh -s claude

Detach with Ctrl-b d. From any browser, your phone included, open the box on the dashboard and pick Claude Code (From your phone).

A question Claude Code asks, such as whether it may run a command, waits on the box until you reattach and answer it. A one-time Yes you gave on your laptop doesn't move, so in manual mode the box asks again, and teleport says so when it moves. Yes, and don't ask again does move: Claude Code saves it in .claude/settings.local.json in your project, which syncs. For a run you leave alone, switch to auto mode (Shift+Tab) before you teleport, or start Claude Code with the tools it needs allowed, such as claude --allowedTools "Bash(npm test *)" (permission modes).

Don't resume the conversation on your laptop with the claude --resume hint Claude Code prints as it closes: that starts a second copy. Bring it back instead.

4. Bring it back

In the project folder on your laptop:

prized teleport back

It stops Claude Code on the box, lets sync bring the box's last edits home, and resumes the conversation here, told it is back on your laptop, in the permission mode it was last in and with the tools you allowed when it left. A step it cut off on the box is checked and carried on.

What moves and what stays

MovesStays where it was
The whole conversation, not a summary: subagent and tool-result files, edit checkpoints, the folder's Claude Code memoryRunning processes: dev servers, background shells, MCP servers
Your files, through sync: uncommitted edits, untracked files, the git branchnode_modules, .venv and build folders (the box installs its own)
The permission mode the conversation was in, and the model and tool flags you started Claude Code with; folder trust; your git name and email, into the box's global git config, if git there has noneShell variables, and .env files unless you pass --sync-env
Rules you saved with Yes, and don't ask again, through syncA one-time Yes, and other answers that last only for the session

When it refuses

Teleport stops nothing and moves nothing when:

  • Claude Code on your laptop waits for your answer to a question, such as a permission prompt. Answer it, then teleport, or pass --wait to wait for your answer and the end of the turn.
  • The box is safe for third parties: the conversation holds whatever the agent read.
  • Claude Code was started with a flag teleport doesn't carry, such as --settings, --mcp-config, --add-dir or a system prompt: on the box it would run without it. Start Claude Code without it, or move the conversation by hand. Teleport carries --permission-mode, --model, --tools, --allowedTools, --disallowedTools and --dangerously-skip-permissions, and leaves flags like --resume, --name and --verbose.
  • The conversation already runs on the box.
  • The box's copy has turns yours lacks (--force replaces it and keeps the old copy).
  • More than one Claude Code has it open.
  • It is over 256 MB.
  • Claude Code isn't installed or signed in on the box.

prized teleport back refuses the same way when your laptop's copy has turns the box's lacks, and refuses a box safe for third parties: anyone it is shared with could have written the conversation, and on your laptop it would run with your credentials. It also refuses when Claude Code on the box was started with a flag teleport doesn't carry: on your laptop it would run without it. It doesn't run on Windows yet.

Every flag is in Agents.