Skip to content

Quick Start

This guide walks through a complete teleport: install CodeTeleport, log in, push a session from your laptop, pull it on your desktop, and resume the conversation.

Alice is building my-saas on her work laptop. She’s deep into a Claude Code session — refactoring the auth module — and needs to continue on her desktop at home. She’ll push the session from the laptop and pull it on the desktop.

  1. Install and log in

    Terminal window
    npm install -g codeteleport
    codeteleport auth login
    How do you want to log in?
    1) GitHub
    2) Email & Password
    > 1
    Opening browser for GitHub login...
    Logged in via GitHub
    Device: alices-laptop
    API: https://api.codeteleport.com/v1
    Config saved to ~/.codeteleport/config.json
  2. Push the session

    From the project directory where Claude Code is running:

    Terminal window
    cd ~/projects/my-saas
    codeteleport push
    Pushing session:
    1) 2026-03-31 14:22 abc123de "Refactor auth middleware" 12 messages
    Bundling...
    size: 847 KB
    Uploading...
    Confirming...
    Session teleported to CodeTeleport
    id : abc123de-f456-7890-abcd-ef1234567890
    size : 847 KB
    machine : alices-laptop

    You can optionally add a label and tags to make it easier to find later:

    Terminal window
    codeteleport push --label "auth refactor WIP" --tags "auth,refactor"
  1. Install and log in (first time only)

    Terminal window
    npm install -g codeteleport
    codeteleport auth login --github
    Opening browser for GitHub login...
    Logged in via GitHub
    Device: alices-desktop
    API: https://api.codeteleport.com/v1
    Config saved to ~/.codeteleport/config.json
  2. Pull the session

    Navigate to the same project (or any directory you want to anchor the session to):

    Terminal window
    cd ~/projects/my-saas
    codeteleport pull

    CodeTeleport shows your cloud sessions and lets you pick one:

    Your sessions:
    1) 2026-03-31 14:22 abc123de alices-laptop "auth refactor WIP"
    2) 2026-03-28 09:15 def456ab alices-laptop "Add billing page"
    Select session (1-2): 1
    Downloading...
    Installing...
    Session pulled
    id : abc123de-f456-7890-abcd-ef1234567890
    from : alices-laptop
    to : /Users/alice/projects/my-saas
    Resume with: claude --resume
  3. Resume the conversation

    Terminal window
    claude --resume

    Claude Code picks up exactly where you left off. All messages, file history, tool calls, and context are intact. File paths have been automatically rewritten from /Users/alice/projects/my-saas on the laptop to the correct path on the desktop.

  1. Push bundled the Claude Code session (the JSONL conversation, file history, paste cache, and shell snapshots) into a compressed archive and uploaded it to secure cloud storage.
  2. Pull downloaded that archive, unpacked it into ~/.claude, and rewrote all absolute paths so they point to the right locations on the new machine.
  3. Resume told Claude Code to load the session from ~/.claude as if it had always been running locally.

To learn more about what’s inside a session bundle, see Sessions.

  • Authentication — learn about login methods, API tokens, and configuration
  • Sessions — understand what gets bundled and why
  • Path Rewriting — how paths are translated across machines