Your agent doesn't stop when you do.
Hand off an in-progress session to a cloud sandbox with /teleport and resume it from anywhere. The Kimchi console mirrors your session on your laptop, phone, or wherever you are.
curl -fsSL https://github.com/getkimchi/kimchi/releases/latest/download/install.sh | bashPlan local. Execute in the cloud.
Start working with Kimchi in your terminal. When the task is too long to babysit, run /teleport mid-session. Kimchi provisions a cloud sandbox, drops you into a persistent remote terminal, and the agent picks up exactly where it left off.
Start a remote session. Access from anywhere. Finish in your IDE.
Start a remote session
Type /teleport in Kimchi to spin up a sandbox and open a console session you can reach from any browser.
Access from anywhere
Open the Kimchi console from any browser to follow the session, or reattach on the fly with /remote-sessions — a tree of your workspaces and sessions, one Enter away. No setup, no machine tether.
Finish in your IDE
When you're back at your machine, pull changes with /sync — or run /ssh-config and reopen the workspace straight in VS Code via Remote Sessions.
Coding agents are useful. Until you're tied to one machine.
Sessions don't die
Close the laptop, lose WiFi, or restart. The agent keeps running in the cloud and you pick up exactly where you left off.
No more babysitting
Long tests, multi-step builds, and agent runs no longer need you staring at a terminal. Check in from anywhere when you want.
A real sandbox
Full autonomy in an isolated workspace. Your local repo, credentials, and system stay untouched.
When to /teleport
- Long-running work. Refactors, test suites, or builds that outlast your coffee break. Run it as a remote session and keep watching from anywhere.
- Switching devices. Start a remote session on your desktop, check status from your phone, finish on your laptop.
- Quick task offload. Hand a one-off task to the agent with
/teleport <task>and read the result when you get back. - Risky automation. Let the agent use full autonomy in an isolated sandbox, not on your main machine.
What happens in the sandbox stays in the sandbox.
Isolated from your machine
The cloud sandbox runs on Kimchi's infrastructure, not your machine. The agent can't touch your local files, credentials, or system state, no matter how hands-on it gets.
Nothing leaks out
Local SSH keys, tokens, and environment variables stay on your laptop. Only the files you choose to sync travel to the sandbox.
You control the sync
Pull changes back when you're ready. Skip gitignored files and secrets by default. Delete the workspace anytime and it's gone.