Remote sessions

    Your agent doesn't stop when you do.

    /teleport hands off your in-progress session to a cloud sandbox. Close the laptop. The agent keeps going.

    $curl -fsSL https://kimchi.dev/install | bash
    kimchi · teleport
    ~/myproject on main
    
     /teleport
    
      Provisioning sandbox...  ████████████████░░  82%
       Workspace ready · ws-f3a1b2c
       Synced 1,204 files
       Skills and tools loaded
    
      Dropping you in. Ctrl+D to exit any time — session keeps running.
    
      ┌─────────────────────────────────────────────────────┐
      │  1:main-task  ○ 2:shell                             │
      ├─────────────────────────────────────────────────────┤
      │   Running phase 2: implement auth middleware...    │
      │                                                     │
      └─────────────────────────────────────────────────────┘
    
      

    Coding agents are useful. Until they're not.

    Sessions die

    Close the lid or lose wifi. Whatever the agent was doing is gone.

    You babysit

    Long tasks mean keeping the terminal open, staying connected, waiting.

    You start over

    Come back to a half-finished task and no context about why it stopped.

    Three steps. Then close the laptop.

    01

    Run /teleport

    Kimchi provisions a sandbox pre-loaded with your tools, skills, and agent state. A progress bar shows setup status.

    02

    You're in the overlay

    A fullscreen tabbed terminal wired to the remote session. Your agent picks up mid-task. Open more tabs with Ctrl+B c.

    03

    Exit any time

    Ctrl+D drops you back to local. The sandbox keeps running. Come back via /sessions, the console, or VS Code.

    Everything stays connected.

    Persistent workspaces

    Workspaces stay alive until you delete them. Filesystem, git history, and installed dependencies are all there when you reconnect.

    Tabbed sessions

    Run multiple independent sessions inside one workspace. Switch with Ctrl+B n/p or jump directly with Ctrl+B 1–9.

    Push local changes

    Made edits locally after handing off? Run /sync to push them to the sandbox without restarting.

    VS Code via Remote SSH

    Run /ssh-config inside the overlay. Open VS Code → Remote Sessions. The workspace appears automatically. Full editor, no manual config.

    Email notifications

    Kimchi emails you when the agent finishes or needs input. Click the link to open the session's web terminal directly.

    Works inside Ferment

    Running a multi-phase Ferment plan? /teleport hands off mid-phase. The agent keeps building from where it left off.

    Kimchi console

    Check in from anywhere.

    The Remote Sessions page shows every active session and the phase each agent is in — planning, coding, reviewing, done. Open a web terminal and interact without touching the CLI.

    app.kimchi.dev / remote-sessions
    3 active
    SessionWorkspaceStatus
    auth-refactorws-f3a1b2cRunning
    add-dark-modews-a9b3d1eRunning
    fix-rate-limitsws-c1d8f2aComplete ✓

    Run /teleport.
    Close the laptop.

    Ships with Kimchi Coding. No separate install required.