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.
See every active workspace at a glance.
Open /remote-sessions to browse every active workspace and session, check status, and jump back into any of them without reopening your local terminal.
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.
YOLO mode needs a sandbox
Let the agent take full control in a clean, isolated workspace. Your local repo, credentials, and system state stay untouched.
Three steps. Then close the laptop.
Run /teleport
Kimchi provisions a sandbox pre-loaded with your tools, skills, and agent state. A progress bar shows setup status.
You're in the overlay
A fullscreen tabbed terminal wired to the remote session. It's already running in the cloud.
Exit any time
Ctrl+D drops you back to local. The sandbox keeps running. Come back via /remote-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.
Works inside Ferment
Running a multi-phase Ferment plan? /teleport hands off mid-phase. The agent keeps building from where it left off.
Run /teleport.
Close the laptop.
Ships with Kimchi Coding. No separate install required.