🚀 Kilo Code Call for Engineers

Kilo Code is looking for engineers to help us build our ambitious roadmap, described below. Some stats about us:

Apply to join our team using the form below. Requirements:

👉 Apply here

Applications are due by 8pm Pacific Time on Monday, October 20th, 2025. For any questions please email adam@kilocode.ai.

Projects described below.

Project Spec: Cloud Agents

1. Introduction

Cloud agents enable running Kilo Code CLI agents in the cloud, offloading computation from the user's local machine and providing easy isolation.

For a minimum-viable product, upload a snapshot of the local repo's main branch HEAD to the cloud, execute the agent task there, and automatically download results as a patch/commit to apply locally on a new branch.

No GitHub integration or token is required in v1, simplifying auth and setup.

Status during agent execution is streamed to the developer’s local Kilo Code CLI, displaying status within the same Terminal UI used to display the status of Parallel Agents spec.

2. Requirements

User Initiation

  1. From CLI: kilocode --cloud "Task description"
  2. Assumes current dir is the repo root, on main branch (error if not)
  3. Stamp a local tag we can use later to apply a patch
  4. Creates a zip of the current HEAD: git archive --format=zip HEAD > repo.zip
  5. Uploads zip to cloud backend (e.g., via HTTP POST to kilocode.com/api/upload), gets session ID in response
  6. Displays status within Kilo Code’s CLI

Cloud Execution

Backend

  1. Receives zip and task description
  2. Spins up ephemeral sandbox
  3. Unzips to temp dir, runs agent: kilocode "Task description"
  4. Status updates are available to the end-user’s CLI
  5. If succeeds: Generates patch git diff > changes.patch, or zip the modified dir.
  6. Stores encrypted result (patch/zip) keyed by session ID
  7. Handle failures: Store error message/log

Result Retrieval

  1. Kilo Code CLI polls cloud-agent status updates and displays in CLI
  2. When done, if cloud succeeded, downloads patch
  3. Applies locally: Creates new branch git checkout -b kilo-task-<id>, applies patch git apply changes.patch, commits git commit -am "<AI-generated message>".

Non-functional

  1. Security
  2. Ephemeral sandboxes without network access
  3. Delete data after download/expiry
  4. Use HTTPS for transfers
  5. Basic anti-abuse limits
  6. Agent Interaction: Autonomous run; fail on input needs, suggest local retry

Open Questions

  1. How can we exclude secrets while still getting `.gitignore`d dependencies such as `node_modules`?

3. Non-goals

  1. GitHub integration (PRs, tokens) – deferred
  2. Support for non-main branches or dirty repos
  3. Multi-repo or persistent cloud storage
  4. Support for custom runtime environments

4. Prior Art

  1. Google's Jules: Remote execution inspiration, but simpler here without auth
  2. Roomote: https://www.youtube.com/shorts/Mh3D_8837Bo – For remote envs; consider hiring contributor
  3. Roo Cloud: Leverage existing extension functionality (minute 52: https://www.linkedin.com/events/7378875994083897344/)
  4. Sandboxes: Vercel https://vercel.com/docs/vercel-sandbox or Cloudflare https://sandbox.cloudflare.com/
  5. Similar: Replit-like snapshots, but minimal transfer focus