{ "manifest_version": "1", "slug": "kimi-code", "title": "Kimi Code", "headline": "Run Kimi Code CLI on a remote server", "description": "Kimi Code CLI with an exe.dev VM: use the VM as an SSH remote environment from your laptop, or run kimi web on it with Kimi K3.1 Pro and no API key.", "category": "ai-agents", "tags": [ "kimi code", "kimi code cli", "kimi", "moonshot ai", "kimi k3.1", "kimi web", "remote environment", "ai coding agent" ], "url": "https://exe.dev/deploy/kimi-code", "markdown_url": "https://exe-staging.dev/deploy/kimi-code.md", "upstream": { "website": "https://www.kimi.com/code", "source": "https://github.com/MoonshotAI/kimi-code", "docs": "https://www.kimi.com/code/docs/en/kimi-code-cli/guides/getting-started.html", "license": "MIT" }, "example_vm_name": "my-kimi-code", "time": "5 minutes", "stack": [ { "name": "Kimi Code CLI", "detail": "`kimi` 2.5.2, with `kimi web` managed by systemd", "port": 8627, "data": "~/.kimi-code" }, { "name": "Your project", "data": "~/project" }, { "name": "Kimi K3.1 Pro", "detail": "Connected through exe.dev's LLM integration" } ], "access": [ { "url": "https://my-kimi-code.exe.xyz:8627/", "who": "private", "what": "Kimi Code's web workbench, behind your exe.dev login and Kimi's server token" }, { "url": "ssh my-kimi-code.exe.xyz", "who": "private", "what": "your terminal, and Kimi on your laptop as a remote environment" } ], "delivers": [ "Kimi Code CLI 2.5.2 on a VM with Kimi K3.1 Pro and Kimi K3 through exe.dev's LLM integration, with no API key or Kimi account.", "Kimi's web workbench at `https://\u003cvm\u003e.exe.xyz:8627/`, behind your exe.dev login and Kimi's own server token, running when you close the tab.", "The VM as a remote environment for Kimi Code on your laptop, so commands and builds run on the VM while your login stays local.", "A project folder at `~/project` on persistent disk." ], "deployable": true, "deploy": { "new_vm_url": "https://exe-staging.dev/new?prompt=Set%20up%20Kimi%20Code%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe-staging.dev%2Fdeploy%2Fkimi-code.md%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-kimi-code.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-kimi-code.%20Skip%20the%20step%20that%20creates%20the%20VM%3B%20you%20are%20on%20it.%0A%0AYou%20are%20done%20when%20all%20of%20these%20are%20true.%20Check%20each%20one%20yourself%3A%0A-%20Kimi%20Code%20CLI%202.5.2%20on%20a%20VM%20with%20Kimi%20K3.1%20Pro%20and%20Kimi%20K3%20through%20exe.dev%27s%20LLM%20integration%2C%20with%20no%20API%20key%20or%20Kimi%20account.%0A-%20Kimi%27s%20web%20workbench%20at%20%60https%3A%2F%2F%3Cvm%3E.exe.xyz%3A8627%2F%60%2C%20behind%20your%20exe.dev%20login%20and%20Kimi%27s%20own%20server%20token%2C%20running%20when%20you%20close%20the%20tab.%0A-%20The%20VM%20as%20a%20remote%20environment%20for%20Kimi%20Code%20on%20your%20laptop%2C%20so%20commands%20and%20builds%20run%20on%20the%20VM%20while%20your%20login%20stays%20local.%0A-%20A%20project%20folder%20at%20%60~%2Fproject%60%20on%20persistent%20disk.%0A%0ARun%20the%20VM-side%20commands%20in%20%22Create%20the%20VM%22%20and%20%22Open%20the%20web%0Aworkbench%22.%20If%20~%2F.kimi-code%2Fconfig.toml%20already%20exists%2C%20merge%20the%0Aprovider%20and%20model%20tables%20into%20it%20instead%20of%20replacing%20it.%20Keep%0A%60kimi%20web%60%20on%20its%20default%20127.0.0.1%20address%2C%20never%20pass%0A--dangerous-bypass-auth%2C%20and%20never%20run%20share%20set-public.%20Verify%20with%20the%0A%60kimi%20-p%60%20command%20and%20check%20that%20%60systemctl%20is-active%20kimi-web%60%20prints%0Aactive.%20Finish%20with%20the%20workbench%20URL%20including%20its%20%23token%3D%20part%2C%20from%0Athe%20command%20in%20%22Open%20the%20web%20workbench%22%3B%20this%20conversation%20is%20private%20to%0Athe%20owner.%20Mention%20that%20%22Use%20the%20VM%20from%20Kimi%20on%20your%20laptop%22%20is%20set%20up%0Aon%20the%20owner%27s%20own%20computer%2C%20not%20here.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A", "terminal": "curl -fsSL https://exe-staging.dev/deploy/kimi-code/prompt.txt | ssh exe.dev new --prompt=/dev/stdin", "prompt": "Set up Kimi Code on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/kimi-code.md from top to bottom.\n\nThe recipe's example VM name is my-kimi-code. This VM's name is the output of `hostname`: use it wherever the recipe writes my-kimi-code. Skip the step that creates the VM; you are on it.\n\nYou are done when all of these are true. Check each one yourself:\n- Kimi Code CLI 2.5.2 on a VM with Kimi K3.1 Pro and Kimi K3 through exe.dev's LLM integration, with no API key or Kimi account.\n- Kimi's web workbench at `https://\u003cvm\u003e.exe.xyz:8627/`, behind your exe.dev login and Kimi's own server token, running when you close the tab.\n- The VM as a remote environment for Kimi Code on your laptop, so commands and builds run on the VM while your login stays local.\n- A project folder at `~/project` on persistent disk.\n\nRun the VM-side commands in \"Create the VM\" and \"Open the web\nworkbench\". If ~/.kimi-code/config.toml already exists, merge the\nprovider and model tables into it instead of replacing it. Keep\n`kimi web` on its default 127.0.0.1 address, never pass\n--dangerous-bypass-auth, and never run share set-public. Verify with the\n`kimi -p` command and check that `systemctl is-active kimi-web` prints\nactive. Finish with the workbench URL including its #token= part, from\nthe command in \"Open the web workbench\"; this conversation is private to\nthe owner. Mention that \"Use the VM from Kimi on your laptop\" is set up\non the owner's own computer, not here.\n\nFinish with the URLs I should open.\n", "prompt_url": "https://exe-staging.dev/deploy/kimi-code/prompt.txt" }, "updated": "2026-11-07", "verified": "2026-11-07", "related": [ "opencode", "zcode", "qwen-code", "deepseek-harness", "claude-code", "openclaw" ] }