← Back to Claude Code Tutorial

Learn Teleport

Move your Claude Code sessions between terminal and web. Start anywhere, continue everywhere.

What is Teleport?

Session mobility for Claude Code

Teleport is a feature in Claude Code that lets you seamlessly move work between your local terminal and the web interface at claude.ai/code. It transfers your full conversation history, code changes, and branch state in one step.

Terminal
claude.ai

This is useful when you want to:

Key idea Teleport is about moving sessions between environments. Send work to the web with &, then pull it back to your terminal with /teleport when it's done.

Quick check: What does Teleport let you do?

Getting Set Up

What you need before you can teleport

Before using Teleport, you need three things ready:

  1. Install the latest Claude Code
    Make sure you have an up-to-date version of the CLI.
  2. Connect your GitHub account
    Visit claude.ai/code and complete onboarding. Connect GitHub so Claude can access your repos.
  3. Install the Claude GitHub app
    Grant access to the repositories you want to work with.
Terminal
$ npm install -g @anthropic-ai/claude-code added 1 package in 12s $ claude --version 2.1.x $ cd my-project $ claude Claude Code v2.1.x Type your request, or /help for commands. claude> _
Why GitHub? Teleport works by pushing code changes to a branch on your GitHub repository. When you teleport a session, Claude fetches that branch into your local checkout. This is why GitHub access is required.

Quick check: Why does Teleport require a GitHub connection?

Sending Tasks to the Web

The & prefix — your gateway to cloud execution

To send a task from your terminal to run on the web, start your prompt with the & character. This creates a new web session on claude.ai that runs in the cloud.

Terminal
claude> & Fix the authentication bug in src/auth/login.ts Task sent to claude.ai/code Session ID: ses_abc123 Monitor at: https://claude.ai/code/ses_abc123

The task now runs autonomously in the cloud. You can close your terminal, shut your laptop, or keep working on other things.

Alternative: claude --remote

You can also start a web session directly from the command line without entering Claude Code first:

Terminal
$ claude --remote "Refactor the logger to use structured output" Task sent to claude.ai/code

Running tasks in parallel

Each & command creates its own independent session. Send multiple and they all run simultaneously:

Terminal
claude> & Fix the flaky test in auth.spec.ts Task sent to claude.ai/code claude> & Update the API documentation Task sent to claude.ai/code claude> & Add input validation to the signup form Task sent to claude.ai/code
One-way transfer Session handoff is one-way: you can pull web sessions into your terminal, but you cannot push an existing terminal session to the web. The & prefix creates a new web session.

Try it: Write a background task command

Type a command that sends a task to run on the web (start with &):

Monitoring Background Tasks

Keep tabs on what's running in the cloud

Once you've sent tasks to the web, you have several ways to check on their progress.

Using /tasks

Inside Claude Code, run /tasks to see all your background sessions:

Terminal
claude> /tasks Your background sessions: 1. Fix auth bug completed 2m ago 2. Update API docs running 1m ago 3. Add form validation running 30s ago Press t to teleport into a session

On the web

Visit claude.ai/code to see all your sessions in the web interface. You can also interact with them directly — ask questions, give feedback, or steer Claude while it works.

On mobile

The Claude iOS app also shows your active web sessions, so you can monitor tasks from your phone.

Interactive monitoring Web sessions are not just fire-and-forget. You can open any session on claude.ai and steer Claude, provide feedback, or answer questions — just like any other conversation.

Quick check: How do you view background sessions from within Claude Code?

Teleporting Sessions to Your Terminal

Pull web sessions back to local — four ways

When a web session is done (or you want to continue it locally), you can teleport it into your terminal. There are four ways to do this:

Terminal
claude.ai

1. The /teleport command

From within Claude Code, run /teleport (or the shorter /tp) to see an interactive picker of your web sessions:

Terminal
claude> /teleport Select a session to teleport: > Fix auth bug completed Update API docs completed Add form validation completed Teleporting session... done Switched to branch: claude/fix-auth-bug-xyz Conversation history loaded.

2. The --teleport CLI flag

From the command line, without entering Claude Code first:

Terminal
$ claude --teleport Interactive session picker opens... Or specify a session directly: $ claude --teleport ses_abc123

3. From /tasks

Run /tasks, then press t to teleport into a selected session.

4. From the web interface

On claude.ai, click "Open in CLI" to copy a terminal command you can paste locally.

Try it: Type the teleport command

What command would you type inside Claude Code to teleport a web session?

Teleport Requirements

What Claude checks before teleporting

Before teleporting a session, Claude automatically verifies several conditions. If any requirement isn't met, you'll be prompted to resolve the issue.

RequirementDetails
Clean git state No uncommitted changes in your working directory. Claude will prompt you to stash if needed.
Correct repo You must be in a checkout of the same repository used on the web (not a fork).
Branch available The web session's branch must be pushed to the remote. Claude auto-fetches it.
Same account You must be logged into the same Claude.ai account used in the web session.

What happens during teleport

When you teleport, Claude handles the complexity automatically:

🔍 Verify repo Confirms correct project
Fetch branch Pulls remote changes
📄 Load context Restores conversation
Resume Continue working
Common gotcha: dirty working directory If you have uncommitted changes, teleport will ask you to stash them first. Get in the habit of committing or stashing before teleporting.

Quick check: What happens if you have uncommitted changes when teleporting?

Advanced Patterns

Pro workflows for getting the most out of Teleport

Plan locally, execute remotely

For complex tasks, start in plan mode to collaborate on the approach, then send the plan to the web for execution:

Terminal
$ claude --permission-mode plan Claude Code (plan mode - read only) I can explore your code but won't make changes. claude> Let's plan a migration from REST to GraphQL Here's my proposed approach: 1. Create GraphQL schema from existing routes... 2. Build resolvers mapping to current services... 3. Add Apollo Server middleware... claude> & Execute the migration plan we discussed Task sent to claude.ai/code

Review with diff view

On claude.ai, you can review changes in a diff viewer before creating a PR. Click the diff stats indicator (e.g., +12 -1) to see exactly what was changed, file by file, and leave comments to request modifications.

Scenario matching

Match each scenario to the right command:

You want to run a task in the cloud while you're away
You want to pull a completed web session into your terminal
You want to see the status of all background sessions
You want to start a web task from the command line without entering Claude Code

Cheat Sheet & Summary

Everything you need at a glance

Quick Reference

ActionCommand
Send task to web& your prompt here
Send task to web (CLI)claude --remote "prompt"
View background tasks/tasks
Teleport a session/teleport or /tp
Teleport from CLIclaude --teleport
Teleport specific sessionclaude --teleport <session-id>
Teleport from /tasksPress t in task list
Choose remote env/remote-env

The Teleport Flow

Terminal & task
Cloud Runs autonomously
Review Web or /tasks
Teleport /tp

Remember

Final quiz: What is the shorthand for /teleport?