ToolScore

Kilo Code

Kilo Code (acquired by Anaconda) · ai coding agents · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-10

Open-source VS Code/JetBrains/CLI agent — a merge of Roo Code and Cline, acquired by Anaconda in July 2026.

#9 of 15 in AI Coding Agents

Get Kilo Code
Real price
$0 · OSS
open-source
BYOK (own key)
Yes
Bring your own Anthropic, OpenAI, Google, Azure or Bedrock keys, or run local models with Ollama / LM Studio —
Limits
9.0/10
$0 platform + PAYG at provider rates (Teams $15, Pass from $19)
Verdict
SOLID OSS ALL-ROUNDER
"No rate limiting on paid models — no weekly, daily, or monthly limits" when using your credits; no 5-hour win

ToolScore breakdown — why 74.5/100

Price / Value
8.5
Token & Rate Limits
9.0
Speed / Latency
7.0
Privacy & Retention
6.0
BYOK (Own API Key)
9.5
Output Quality
7.0
Stability
7.0
Ease of Setup
8.0
Billing Transparency
6.5
Support & Community
6.0

10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →

What it does well

  • ▸Full BYOK incl. Ollama/LM Studio on the free plan; PAYG at exact provider rates with no markup
  • ▸No rate limits on paid models — no 5-hour windows, no weekly caps
  • ▸VS Code + JetBrains + CLI + cloud agents ($0.33–1.20/h) + mobile, one-line installs
  • ▸Very active MIT repo: 27.9k stars, 34k commits

Where it costs you

  • ▸Zero-retention only on paid plans; training-on-your-code is not explicitly disclaimed
  • ▸Acquired by Anaconda (July 2026) — pricing/policy direction may shift
  • ▸HN launch skepticism ("fork for VC metrics"); no independent quality edge over Cline demonstrated

Hidden traps — the stuff the pricing page doesn't say

high riskZero-retention is a paid feature

"No data retention for AI prompts and outputs" applies to paid plans only — on the free/BYOK path no ZDR promise covers your prompts.

high riskAnaconda acquisition (2026-07-15)

The Trust Center now redirects to trust.anaconda.com; pricing, license and privacy terms may change under new ownership.

medium risk5% credit fee + $5 cloud minimum

PAYG at "exact provider rates" quietly loses 5% to a processing fee on every credit purchase.

medium riskOpen core, not all open

Cloud agents, the Gateway and Trust Center are hosted/closed parts; HN critics call it a walled garden.

Try Kilo Code

Know the limits before you pay: read the traps above, then decide with eyes open.

Visit official site

Affiliate link where available — never affects the score.

What the advertised price hides
Free & open-source platform (usage billed separately); Teams $15/user/mo; Kilo Pass from $19/mo buys bonus inference credits (with a 5% processing fee and $5 cloud minimum).
Sources & freshness

Data as of 2026-11-10. Prices and limits change monthly — report anything stale. How we verify: methodology.

Closest alternatives

Kilo Code review

In-depth analysis · last updated 2026-11-10

The Cline/Roo merge that grew up

Kilo Code started as a feature-merge of Roo Code and Cline (VS Code extension) and now spans VS Code, JetBrains, a CLI forked from OpenCode, cloud agents and even mobile. 27.9k stars and 34k commits of MIT code.

The pricing posture

The platform is free; inference is PAYG at exact provider rates (500+ models through the Gateway) or full BYOK — including Ollama and LM Studio on the free plan. Paid layers: Teams at $15/user, Kilo Pass from $19/mo for bonus credits. On paid models: "no weekly, daily, or monthly limits" — the cleanest limits story among the subscription-adjacent tools.

What holds it back

Zero-retention is a paid feature; training on your code is never explicitly disclaimed. HN's launch-thread skepticism ("$15 credit bribe", "walled garden") never fully got an independent quality rebuttal — with the same BYOK models as Cline, no demonstrated agent-layer edge. And the July 2026 Anaconda acquisition puts a question mark over future pricing and policy.

Verdict

A solid all-rounder if you want Cline-class capability with cloud and mobile extras — 74.5/100. Read the retention terms before pointing it at client code.

From the insights