# Claude Code teleport: pull cloud sessions to your terminal

> claude --teleport pulls a Claude Code cloud session and its branch into your terminal. It needs a clean tree, the same repo and the same claude.ai account.

Source: https://shuriken.sh/guides/claude-code-teleport-cloud-sessions

Run claude --teleport from a clean checkout of the same repository, signed in to the same claude.ai account, and pick the session: Claude Code fetches its branch and loads the whole conversation. The other way, claude --cloud "task" starts a new cloud session from your pushed branch.

By Shuriken Updated 27 October 2026 6 min read

**Contents**

Claude Code teleport pulls a cloud session into your terminal. Run claude --teleport (or /tp inside a session) from a clean checkout of the same repository, signed in to the same claude.ai account, and pick the session. Claude Code fetches the session's branch, checks it out and loads the whole conversation. The reverse, claude --cloud "task", starts a new cloud session.

The commands and error text below are copied from Anthropic's [cloud sessions page](https://code.claude.com/docs/en/claude-code-on-the-web), which we read on 24 October 2026.

## What claude --teleport actually moves #

A cloud session is Claude Code running on a VM, by default one Anthropic manages, with a copy of your repository. It keeps going when your laptop is shut. Teleport hands that session to your terminal: Claude Code checks that you are in the right repository, fetches and checks out the branch the cloud session worked on, and loads the conversation history.

It is a copy, not a link. Once the session is in your terminal, new work there stays local and doesn't show up in the cloud session on claude.ai or in the Claude app. If you still want to steer it from your phone afterwards, start /remote-control in the local session.

From the CLI the handoff goes one way. You can pull a cloud session down, but you can't push a running terminal session up. The Claude Desktop app is the exception: its Open in menu has Cloud, which continues a local session as a cloud session with the conversation carried over as a summary ([Desktop docs](https://code.claude.com/docs/en/desktop)). It doesn't work for sessions over SSH or in WSL. How the Desktop app compares with a harness is in [Shuriken vs Claude Code Desktop](https://shuriken.sh/compare/claude-code-desktop).

## Start a cloud session from your terminal with claude --cloud #

bash
claude --cloud "Fix the authentication bug in src/auth/login.ts"

The cloud VM clones your current directory's GitHub remote at your current branch. It does not copy your local checkout, so push first if you have local commits. Each --cloud command makes its own session, and several can run at once.

When the repository has no git remote, or is on github.com without the Claude GitHub App installed, Claude Code bundles your local repository and uploads it instead of cloning. CCR_FORCE_BUNDLE=1 forces the upload, which is also how a GitLab or Bitbucket repository gets in:

bash
CCR_FORCE_BUNDLE=1 claude --cloud "Run the test suite and fix any failures"

The bundle has to be a git repository with at least one commit and under 100 MB. A bigger one falls back to the current branch only, then to a squashed snapshot of the working tree, and fails if that is still too big. Untracked files are left out, so git add what the session should see. On macOS, Linux and WSL, uncommitted changes to files named like secrets (.env, *.tfvars, id_rsa, *.pem) stay on your machine; on native Windows they upload as they are. A session started from a GitLab or Bitbucket bundle can't push back to that remote.

To steer a running session without opening the browser, queue a message into it:

bash
claude -p "your message" --cloud <session-id>

It posts one message and exits. The ID is the session_... or cse_... value from claude.ai/code, or the session's URL. Without -p, the CLI refuses with Attaching to an existing cloud session is not enabled for your account.

## How to teleport a cloud session into your terminal #

There are five ways in, and they all end in the same place:

- Run claude --teleport for a session picker, or claude --teleport <session-id> to go straight to one.
- Inside a running Claude Code session, type /teleport or /tp for the same picker.
- Type /tasks, pick the session and press t.
- On claude.ai/code, open the session menu and choose Open in › Terminal. It copies a command to paste.
- Inside the cloud session, type /teleport. Claude Code replies with the exact claude --teleport <session-id> command for it (this needs Claude Code v2.1.223 or later in the session's environment).

If your working tree has uncommitted changes, teleport offers to stash them first.

## Teleport requirements #

Teleport checks four things before it resumes anything:

| Requirement | What Anthropic's docs say |
| --- | --- |
| Clean git state | No uncommitted changes. Teleport prompts you to stash them |
| Same repository | A checkout of the session's repository, not a fork. The wrong one gives an error naming both repositories |
| Branch pushed | The session's branch must be on the remote. Teleport fetches and checks it out |
| Same account | Signed in to the claude.ai account that owns the session |

The fetch never waits for input. If git or ssh would ask for a password, a key passphrase or confirmation of a new SSH host, the fetch fails, and the checkout only works if your clone already has the branch. Load your key into ssh-agent and run git fetch once by hand first.

Teleport also needs a claude.ai subscription sign-in. With an API key, run /login. Through Amazon Bedrock, Google Cloud or another third-party provider, cloud sessions aren't available at all.

Shuriken adds a server of yours with one command, and its chats sit beside your computer's.

[Download](https://shuriken.sh/download)

## Claude Code teleport not working: the errors #

| You see | What it means and what to do |
| --- | --- |
| Unable to get organization UUID , or Cloud sessions need a claude.ai sign-in | You're on an API key or stale account details. Run claude auth login , or /login in a session, then retry |
| Error loading Claude Code sessions in the picker | The same sign-in problem, seen from claude --teleport with no ID |
| Branch <name> is not on GitHub (from --cloud ) | The session started anyway, from a pushed commit or the default branch. Push the branch and start a new session if it needs your local commits |
| Remote Control session expired or Access denied | Teleport connects through the same Remote Control session infrastructure, so its errors use that wording. Run /login , and check you're on the account that owns the session |
| Remote Control may not be available for this organization | An Owner hasn't turned on cloud sessions for your organization |
| Session creation failed | No VM could be allocated. Check status.claude.com and retry after a minute |

When the error is about Remote Control on a session that runs on your own machine, not a cloud one, the fixes are different: they're in [Claude Code Remote Control not working](https://shuriken.sh/guides/claude-code-remote-control-not-working).

## Claude Code teleport vs --resume vs Remote Control #

The three get mixed up because they all "continue a session", but each one reopens something different:

| | Where the agent runs | What it reopens |
| --- | --- | --- |
| claude --teleport | A cloud session on Anthropic's VM, then your terminal | A cloud session and its branch, as a local copy |
| claude --resume | Your machine | A conversation from this machine's local history; it doesn't list cloud sessions |
| Remote Control | Your machine, the whole time | Nothing moves: claude.ai or the Claude app is a window into the local session, so the computer has to stay on |

If the session you want was started in your terminal, you need --resume, and [resuming a Claude Code session](https://shuriken.sh/guides/resume-claude-code-session) covers where those transcripts live and why one sometimes won't come back. If you want the agent to keep running on your machine while you watch from a phone, that's Remote Control, compared with the other phone options in [running Claude Code from your phone](https://shuriken.sh/guides/run-claude-code-from-your-phone).

## How Shuriken does it #

Shuriken doesn't use Anthropic's cloud. It runs Claude Code, Codex and the other agents on your own computers and servers, and moves chats between them. When you start a chat on its own branch, you can pick another of your computers or servers to run it. That machine clones the project's repository, or fetches it if it already has a copy, and the chat carries on there ([how running a chat somewhere else works](https://shuriken.sh/blog/run-chat-on-another-computer), with the Finish step that brings the branch home).

A chat that is already going can move too. Run on… in the chat's menu moves the chat, its uncommitted work and its history to another computer or server. It stays the same chat, in the same place in your list; only the computer it runs on changes. If it is mid-turn, it moves once the turn ends. For Claude Code the history is the CLI's own session transcript, so it picks up where it stopped. Unlike teleport, that works in either direction between any two of your machines. The trade is the one Remote Control has: the machine doing the work is yours, so it has to be on and online. Both need a git remote when the other machine has no copy of the project yet, because it gets the project from there; the chat's own uncommitted work comes across with it. A Shuriken server on an always-on box covers the hours your laptop is shut. You can [download Shuriken](https://shuriken.sh/download) for Mac, Windows or Linux.

Share

[X](https://x.com/intent/post?url=https%3A%2F%2Fshuriken.sh%2Fguides%2Fclaude-code-teleport-cloud-sessions&text=Claude%20Code%20teleport%3A%20pull%20cloud%20sessions%20to%20your%20terminal)[LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fshuriken.sh%2Fguides%2Fclaude-code-teleport-cloud-sessions)[Hacker News](https://news.ycombinator.com/submitlink?u=https%3A%2F%2Fshuriken.sh%2Fguides%2Fclaude-code-teleport-cloud-sessions&t=Claude%20Code%20teleport%3A%20pull%20cloud%20sessions%20to%20your%20terminal)[Reddit](https://www.reddit.com/submit?url=https%3A%2F%2Fshuriken.sh%2Fguides%2Fclaude-code-teleport-cloud-sessions&title=Claude%20Code%20teleport%3A%20pull%20cloud%20sessions%20to%20your%20terminal)[E-mail](mailto:?subject=Claude%20Code%20teleport%3A%20pull%20cloud%20sessions%20to%20your%20terminal&body=https%3A%2F%2Fshuriken.sh%2Fguides%2Fclaude-code-teleport-cloud-sessions)

## Sources

- [Claude Code docs: Use Claude Code in the cloud](https://code.claude.com/docs/en/claude-code-on-the-web) (accessed 24 October 2026)
- [Claude Code docs: Claude Code Desktop (Continue in another surface)](https://code.claude.com/docs/en/desktop) (accessed 24 October 2026)
- [Claude Code docs: Continue local sessions from any device with Remote Control](https://code.claude.com/docs/en/remote-control) (accessed 24 October 2026)

## Frequently asked questions

**Does teleport work when my git remote uses an SSH host alias?**

Yes. When Claude Code can't read a hostname from the remote, as with git@work:owner/repo.git, it asks you to confirm, and accepts the checkout if the owner and repository name match the session's repository.

**What happens to a cloud session that sits idle?**

After a period of inactivity its VM is reclaimed. Reopening it from claude.ai/code starts a fresh VM with the conversation history, but shell commands and subagents that were still running don't come back, so ask Claude to rerun or continue them.

**Is claude --remote the same as claude --cloud?**

Yes. --remote is the older spelling and still works as a deprecated alias for --cloud. --remote-control is a different feature: it lets you steer a session that runs on your own machine.

**Do Claude Code cloud sessions cost extra?**

Anthropic says they count toward your plan's usage limits along with the rest of your Claude and Claude Code usage, and there is no separate charge for the cloud VM. They are on Pro, Max and Team, and on Enterprise premium or Chat + Claude Code seats.

Servers

Your agents on your own servers.

Add a Linux, macOS or Windows server from the app with one command. It runs as a service and updates itself.

[Download](https://shuriken.sh/download)

[Other platforms](https://shuriken.sh/download#main)

## Keep reading

- [How to install Shuriken on Mac, Windows and Linux: Guide 27 Oct 2026 3 min read Install Shuriken from shuriken.sh on Mac, Windows or Linux. The Mac app is notarised by Apple; Windows may warn once, as its installer isn't signed yet.](https://shuriken.sh/guides/install-shuriken)
- [Claude Code in a dev container: setup, firewall and auth: Guide 27 Oct 2026 5 min read Claude Code in a devcontainer is one feature line. A named volume and one env variable keep your sign-in through rebuilds; skipping prompts stays unsafe.](https://shuriken.sh/guides/claude-code-devcontainer)
- [Claude Code in GitHub Codespaces: setup and sign-in: Guide 27 Oct 2026 7 min read Claude Code runs in GitHub Codespaces through Anthropic's dev container feature, and a personal Codespaces secret keeps each new codespace signed in.](https://shuriken.sh/guides/claude-code-github-codespaces)
- [Claude Code on a VPS: sizing, setup and staying safe: Guide 27 Oct 2026 7 min read Claude Code runs on a VPS with 4 GB of RAM, an x64 or ARM64 CPU and Ubuntu 20.04+ or Debian 10+, used from a supported country. How to size and secure it.](https://shuriken.sh/guides/claude-code-on-a-vps)
- [Run Claude Code on an always-on machine: Guide 27 Oct 2026 6 min read Run Claude Code on a home server, mini PC or VM that never sleeps: install, headless sign-in, tmux, remote access, or add it as a Shuriken server.](https://shuriken.sh/guides/claude-code-on-an-always-on-machine)
- [Run Claude Code on a remote server over SSH: Guide 27 Oct 2026 6 min read Run Claude Code over SSH the right way: sign in on a headless box, keep sessions alive with tmux, handle Git keys safely, and see what SSH alone can't do.](https://shuriken.sh/guides/claude-code-over-ssh)
- [Claude Code on a Raspberry Pi: what works: Guide 27 Oct 2026 8 min read Claude Code runs on a Raspberry Pi 4 or 5 with 4 GB of RAM or more and the 64-bit Raspberry Pi OS. Which boards qualify, the 32-bit trap, and the setup.](https://shuriken.sh/guides/claude-code-raspberry-pi)
- [Claude Code with VS Code Remote-SSH, WSL and containers: Guide 27 Oct 2026 8 min read In a VS Code Remote-SSH, WSL or dev container window, the Claude Code extension runs remotely: sign-in, ~/.claude, MCP servers and the CLI live there.](https://shuriken.sh/guides/claude-code-vscode-remote-ssh)
- [Install Claude Code on Linux: Ubuntu, Fedora, Alpine: Guide 27 Oct 2026 8 min read To install Claude Code on Linux, run curl -fsSL https://claude.ai/install.sh | bash, or add Anthropic's signed apt, dnf or apk repository.](https://shuriken.sh/guides/install-claude-code-on-linux)

## Free tools

- [Claude limit reset tracker](https://shuriken.sh/tools/limit-resets/claude)
- [Codex limit reset tracker](https://shuriken.sh/tools/limit-resets/codex)