跳转到主要内容

Cloud Agents

Cloud Agents let you run Kilo Code in the cloud from any device, without relying on your local machine. They provide a remote development environment that can read and modify your GitHub repositories, run commands, and auto-commit changes as work progresses.

What Cloud Agents Enable​

  • Run Kilo Code remotely from a browser
  • Auto-create branches and push work continuously
  • Use env vars + startup commands to shape the workspace
  • Work from anywhere while keeping your repo in sync

Prerequisites​

Before using Cloud Agents:

  • GitHub Integration must be configured
    Connect your account via the Integrations tab so that Cloud Agents can access your repositories.

Cost​

  • Compute is free during limited beta
    • Please provide any feedback in our Cloud Agents beta Discord channel:
  • Kilo Code credits are still used when the agent performs work (model usage, operations, etc.).

How to Use​

  1. Connect your GitHub account in the Integrations tab of your personal or organization dashboard.
  2. Select a repository to use as your workspace.
  3. Add environment variables (secrets supported) and set optional startup commands.
  4. Start chatting with Kilo Code.

Your work is always pushed to GitHub, ensuring nothing is lost.

How Cloud Agents Work​

  • Each user receives an isolated Linux container with common dev tools preinstalled (Node.js, git, gh CLI, etc.).

  • All Cloud Agent chats share a single container instance, while each session gets its own workspace directory.

  • When a session begins:

    1. Your repo is cloned
    2. A unique branch is created
    3. Your startup commands run
    4. Env vars are injected

  • After every message, the agent:

    • Looks for file changes
    • Commits them
    • Pushes to the session’s branch

  • Containers are ephemeral:

    • Spindown occurs after inactivity
    • Expect slightly longer setup after idle periods
    • Inactive cloud agent sessions are deleted after 7 days during the beta, expired sessions are still accessible via the CLI

Environment Variables & Startup Commands​

You can customize each Cloud Agent session by defining:

Environment Variables​

  • Add key/value pairs or secrets
  • Injected into the container before the session starts
  • Useful for API keys or config flags

Startup Commands​

  • Commands run immediately after cloning the repo and checking out the session branch
  • Great for:
    • Installing dependencies
    • Bootstrapping tooling
    • Running setup scripts

Perfect For​

Cloud Agents are great for:

  • Remote debugging using Kilo Code debug mode
  • Exploration of unfamiliar codebases without touching your local machine
  • Architect-mode brainstorming while on the go
  • Automated refactors or tech debt cleanup driven by Kilo Code
  • Offloading CI-like tasks, experiments, or batch updates

Limitations and Guidance​

  • Each message can run for up to 15 minutes. Break large tasks into smaller steps; use a plan.md or todo.md file to keep scope clear.
  • Context is persistent across messages. Kilo Code remembers previous turns within the same session.
  • Auto/YOLO mode is always on. The agent will modify code without prompting for confirmation.
  • Sessions are restorable locally and local sessions can be resumed in Cloud Agent.
  • Sessions prior to December 9th 2025 may not be accessible in the web UI.
  • MCP support is coming, but Docker-based MCP servers will not be supported.
Is this documentation incorrect or incomplete? Report an issue on GitHub