Claude Code Teleport: What It Does and How to Continue a Cloud Session

What Claude Code Teleport does

Claude Code Teleport brings a cloud session into a terminal so you can continue the work locally. It is a Claude Code session workflow—not a model-selection feature or a production inference API.

The two command forms have different roles: /teleport is entered inside the cloud session to get the command for that session; claude --teleport <session-id> is then run from a checkout of the repository in your terminal. They are not interchangeable commands.

How to continue a cloud session in your terminal

1. Check access. Cloud sessions are available on Pro, Max, Ultra, and Team plans, and for Enterprise users with premium seats or Chat + Claude Code seats. Custom roles may also need the cloud sessions permission.
2. Start or open a cloud session. You can start one at claude.ai/code, from the Code tab in the Claude app, in the Desktop app’s Cloud environment, or from a terminal with claude --cloud.
3. Get the command for the session. In the cloud session, enter /teleport. Claude Code responds with the session-specific claude --teleport <session-id> command.
4. Run it locally. In a terminal, change to a checkout of that repository and run the command Claude provided. The documented result is that you can continue the cloud session’s work in the terminal. The documentation excerpt does not specify exactly which conversation or code state is restored.

The cloud-session environment must be running Claude Code v2.1.223 or later for this Teleport flow. The cloud workflow also requires the CLI to be signed in to the same Claude account as the cloud session. These details describe the documented cloud-to-terminal handoff; they do not establish that every repository host or session state is supported.

Teleport and production model APIs

Teleport moves a Claude Code session; it does not provide an inference endpoint or choose a model for an application. If you are selecting a production model API, evaluate that separately from Teleport.

For this cloud-session workflow, the documented requirement is that the CLI be signed in to the same Claude account as the cloud session. An API key alone is not identified as a substitute for that account sign-in. That is a workflow-specific distinction, not a general statement about API-key authentication in other Claude Code setups or the Claude API.

Reported Teleport problems

Users have reported different problems in separate GitHub issues. One report described a 400 error involving a tool_result without a matching preceding tool_use after running claude --teleport; another said /teleport did not display a remote cloud session. These are individual reports, not proof that Teleport generally fails or that either problem affects current versions. The issues’ closure after inactivity does not establish that a fix shipped.

A commenter on the first issue reported exporting the conversation and pasting it into a new session as a workaround. That is a user-reported workaround, not a guaranteed or official repair.

Bottom line: Use /teleport inside the cloud session to get its specific CLI command, then run that command from the repository checkout in a terminal. Teleport is for continuing Claude Code cloud-session work—not for choosing or calling a production model API.

Sources

Use Claude Code in the cloud — Claude Code Docs

Claude Code in der Cloud verwenden — Claude Code Docs

在云端使用 Claude Code — Claude Code Docs

Persistent API Error After Teleporting Session — Claude Code issue #11042

/teleport command not displaying remote cloud sessions — Claude Code issue #16999