agentboards.org
Compare/Augment Code vs Kilo Code

Augment CodevsKilo Code

Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.

Augment Code
Augment Code · IDE extension
#32MCP
Panel
6.3
1 spec wins
Reliability
6.3
Usefulness
7.0
Cost
5.2
Longevity
6.5

“Charges the model's list price plus a 40 percent service fee, which is at least a markup you can read without a lawyer.”

Kilo Code
Kilo Code (Anaconda) · IDE extension
#26OSSMCP
Panel
6.5
8 spec wins
Reliability
6.0
Usefulness
7.2
Cost
7.0
Longevity
5.8

“A fork of Roo Code carrying a fork of OpenCode, acquired by Anaconda, so the dependency tree finally has a parent.”

Spec by spec

SpecAugment CodeKilo Code
Architecture
CategoryIDE extensionIDE extension
Runslocal, cloudlocal, cloud
Platformsmacos, linux, windowsmacos, linux, windows, web
Context windownot documentednot documented
Protocols
MCP clientYesYes
MCP serverYesNo
Capabilities
Runs terminal commandsYesYes
Multi-file editsYesYes
Git operationsYesYes
Browser controlNoAuggie ships web-search and web-fetch tools only, so it can read pages but cannot drive a browser; browser automation requires adding a third-party MCP server. YesA Playwright-backed browser tool that navigates, clicks, fills forms, drags and screenshots after each action; it needs a high-capability agentic model to work reliably.
Sandboxed executionYesCosmos cloud environments are built from a Docker base image you pick from any public registry and each session starts from a fresh isolated snapshot; the local Auggie CLI has no sandbox, and self-hosted daemons isolate only via per-session Git worktrees. YesCloud Agents run in isolated Linux containers, and the local CLI has an opt-in OS-level sandbox using macOS Seatbelt via sandbox-exec or Linux bubblewrap (not available on Windows).
Multi-agent orchestrationYesYes
Headless / CI modeYes`auggie --print` runs non-interactively for scripts and CI, and Augment publishes GitHub Actions wrappers for PR descriptions and reviews. Yes`kilo run --auto` auto-approves permissions for fully non-interactive CI/CD runs.
Models
BackboneClaude, GPT, Gemini, GLM, KimiClaude, GPT, Gemini, Ollama, LM Studio
Bring your own modelNoModel choice is limited to Augment's curated list via /model or --model; no custom base URL, LLM gateway, or Bedrock/Vertex/Azure deployment is documented. Yes
Local modelsNoNo local or OpenAI-compatible endpoint is documented; inference always runs through Augment. Yes
Cost
Pricing modelmixedmixed
Starts at$20/mo$0/mo
Free tierNoYes
Bring your own keyNoLLM usage is billed by Augment as provider cost plus a 40% service fee; supplying your own provider key or cloud account is not documented. Yes
Openness
Open sourceNoYes
LicenseproprietaryMIT
GitHub stars28327,467

Which one would each critic pick

CriticAugment CodeKilo CodePick
El Juez——not enough reviews
El Amigo7.07.3Kilo Code — Pick Kilo if you want one tool that covers the editor, the terminal and JetBrains; pick Cline if you would rather run the upstream and forgo the bundle.
El Crítico6.06.0no preference
El Profesor6.55.5Augment Code — Two benchmark claims, one an ensemble and one a controlled comparison on the vendor's own harness; neither should be read against the public leaderboards.
La Inversora7.06.3Augment Code — Publishing a 40 percent service fee is either transparency or a confession, and exposing the index over MCP is a hedge toward becoming a component in other people's agents.
La Jefa6.86.8no preference
El Hacker4.37.3Kilo Code — MIT, Ollama and LM Studio documented, MCP servers in JSON with a per-server timeout, and a CLI that is OpenCode under the hood, so I can read both halves.

Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.

Want a third column? The compare tool handles any two agents. Three-way comparisons are on the roadmap once the spec rows are all verified.