Kilo Code
TL;DR
Kilo Code is an MIT-licensed coding agent for VS Code, JetBrains and a CLI that is a fork of OpenCode. Its Agent Manager runs parallel sessions in git worktrees, and agents can delegate to task subagents. The pricing page says Kilo was acquired by Anaconda. It suits developers who want one agent across editors with model choice.
Key facts
| Type | Harness |
|---|---|
| Languages / SDKs | TypeScript |
| License | MIT |
| Pricing model | Open core |
| Orchestration pattern | Supervisor |
| GitHub stars | 27,453 (as of 2026-09-30) |
| GitHub forks | 3,218 |
| Last push | 2026-09-30 |
| Latest release | jetbrains/v7.1.8 |
| Repository | Kilo-Org/kilocode |
| Website | kilo.ai |
| Documentation | kilo.ai |
| Last verified | 2026-09-30 |
Key features
- Agent Manager, a VS Code panel for parallel sessions in isolated git worktrees or the shared workspace, each with its own transcript, prompt queue and terminal. (source)
- Multi-version mode runs up to four parallel implementations of one prompt in separate worktrees, optionally with a different model for each. (source)
- The
agent_managertool lets an agent start up to 20 worktree sessions from chat, list them, prompt them, stop them and answer their questions. (source) tasksubagents let Code, Plan and Debug agents delegate subtasks in the same directory, in the foreground or in the background; Kilo Swarm adds a shared message board for a session and its descendants. (source)- A diff and review panel shows changes against the parent branch, sends review comments back to the agent, and shows pull request status badges. (source)
- MCP servers are configured for the extension and CLI, with curated ones installable from the Kilo Marketplace. (source)
- Permission rules (allow, ask, deny) apply per tool, command pattern and subagent in agent files and config. (source)
- The
kiloCLI runs interactively or withkilo run --autofor CI, andkilo acpstarts an Agent Client Protocol server. (source)
Architecture and orchestration pattern
Pattern: Supervisor
Kilo Code is a coding agent with three surfaces: a VS Code extension (with an embedded runtime), a JetBrains plugin and the kilo CLI, which the README says is a fork of OpenCode. Agents are named modes: Code, Plan, Ask and Debug, plus custom agents. Models come from the user's own keys, local models, or the Kilo Gateway, which the README says charges provider rates with no markup.
The docs describe three multi-agent mechanisms. task subagents are non-interactive children of one session that share its directory. Agent Manager sessions are independent top-level sessions that can each own a git worktree and are supervised from a panel, and an agent can start or prompt them with the agent_manager tool. Kilo Swarm is a message board (board_post, board_read) for a session and its task descendants; the docs say it does not start, stop or assign agents. The older orchestrator agent is deprecated.
Agent Manager state (worktrees, sections, tabs, cached PR data) is stored in .kilo/agent-manager.json, and managed worktrees live under .kilo/worktrees/. There is also a hosted Cloud Agent that runs Kilo in a remote environment against GitHub, GitLab or Bitbucket repositories.
Human in the loop
A Permission Dock shows tool approval prompts with approve once, approve always, or deny, and Agent Manager sessions accept follow-up messages, cancel (cooperative stop) and stop (force). Permission rules can set each tool, command pattern or subagent to allow, ask or deny. Reviewers can comment on diff lines and send the comments to the agent. Approving an agent_manager request is scoped to the requested capability, and prompting an existing session needs its own approval. kilo run --auto approves permission prompts unless a rule denies them and the README says to use it only in trusted environments.
Protocols
| Protocol | Support | Note |
|---|---|---|
| MCP | Yes evidence | Kilo is an MCP client: the docs describe configuring MCP servers for the extension and CLI, with allow, ask or deny rules for MCP tools. An MCP server exposing Kilo itself is not described. |
| A2A | Unknown | Searched the README and the complete docs bundle (kilo.ai/docs/llms.txt) for 'a2a' and 'agent2agent'; nothing found. kilo acp starts an Agent Client Protocol server, which is a different protocol. |
| AG-UI | Unknown | Searched the README and the docs bundle for 'ag-ui'; nothing found, and Kilo is not named in the AG-UI README. |
Best for
- Running several agent sessions in parallel in isolated git worktrees from inside VS Code, with a diff panel and PR status. (shortlist)
- Trying up to four model variants of the same prompt and keeping the best worktree. (shortlist)
- Using one coding agent across VS Code, JetBrains and the terminal with a choice of hosted, bring-your-own-key or local models. (shortlist)
- Running unattended fixes in CI with
kilo run --autoin a trusted environment. (shortlist)
Not for
- Users who want Agent Manager in JetBrains or the CLI: the docs say the
agent_managertool is available by default only in the VS Code extension. - Anyone who needs subagents to be isolated from each other: a
tasksubagent does not create a worktree. - Teams looking for a launcher for other vendors' agents (Claude Code, Codex): Kilo runs its own agent and only imports their session history.
Quickstart
npm install -g @kilocode/clinpm install -g @kilocode/cli # also: curl -fsSL https://kilo.ai/cli/install | bash, brew install Kilo-Org/tap/kilo
cd my-project
kilo # start Kilo in the project directory
# Unattended run for CI; auto-approves permission prompts unless a rule denies them
kilo run --auto "run tests and fix any failures"
# VS Code: install the Kilo Code extension, then open the Agent Manager
# Cmd+Shift+M (macOS) / Ctrl+Shift+M (Windows, Linux)
# In chat, ask for parallel work; the agent uses the agent_manager tool:
# "Start two worktree sessions: one to add pagination, one to fix the flaky test."
Common pitfalls
- Agent Manager is a VS Code extension feature; it needs a git repository, and new worktrees must be created from the main repository, not from an existing worktree checkout.
kilo run --autoapproves permission prompts unless a rule denies them; the README says to use it only in trusted environments.- The CLI is a fork of OpenCode; Kilo no longer falls back to configuration stored in
.opencodedirectories, so move it into~/.config/kilo/or./.kilo/. - The orchestrator agent is deprecated; use Code, Plan or Debug, which delegate with
taskdirectly. tasksubagents share the parent's directory, so avoid duplicate edits in the same files; use worktree sessions when isolation is needed.- The README says VS Code users create an account for the Kilo Gateway models; bring-your-own-key and local models are alternatives.
Pros
- Worktree-isolated parallel sessions with a review panel, and up to four model variants of one prompt. (source)
- Clear separation of orchestration layers: task subagents inside a session, independent Agent Manager sessions, and a message board. (source)
- MIT licensed, available in VS Code, JetBrains and the CLI. (source)
- Fine-grained allow, ask and deny permission rules, including for MCP tools and subagents. (source)
- Models are not tied to one vendor: bring your own keys, run local models, or use the Kilo Gateway; the pricing page lists Free, Teams and Enterprise platform plans. (source)
Cons
- The pricing page carries a banner saying Kilo has been acquired by Anaconda; the effect on the open-source project is not described there. (source)
- Orchestrator mode is deprecated and scheduled for removal, so older workflows built on it need migration. (source)
- Agent Manager and its
agent_managertool are available by default only in the VS Code extension. (source) - Kilo Swarm only exchanges notes; it does not start, stop or assign agents, and separate Agent Manager sessions do not share a board. (source)
kilo run --autoauto-approves permission prompts, which is unsafe outside trusted environments. (source)
Alternatives
FAQ
Does Kilo Code support MCP?
Yes, as a client. The docs cover configuring MCP servers for the extension and CLI, permission rules for MCP tools, and a marketplace of curated servers. They do not describe Kilo as an MCP server.
Is Kilo Code free?
The extensions and CLI are MIT licensed and the pricing page lists a Free plan. Paid options include Teams and Enterprise plans, usage-based cloud compute, and model usage through the Kilo Gateway, Kilo Pass or your own keys.
How does Kilo run agents in parallel?
Agent Manager runs independent sessions in git worktrees, with multi-version mode for up to four variants. Inside one session, task subagents delegate subtasks in the same directory.
How is it related to OpenCode?
The README says the Kilo CLI is a fork of OpenCode. Kilo runs its own agent; it does not launch OpenCode, Claude Code or Codex, though its CLI can import Claude Code and Codex session history.
Who owns Kilo Code?
The kilo.ai pricing page carries a banner saying Kilo has been acquired by Anaconda and links to an announcement. The repository license is still MIT.