Head to head · Agent harness · October 2026 research run
Gemini CLI vs Kilo Code CLI
Kilo Code CLI scores 75.4 (BB) on agent readiness against Gemini CLI's 72 (BB), and leads in 2 of 7 scored categories. Gemini CLI leads on agent ergonomics and transparency & trust. Both do agent harness.
Which one, for what
Gemini CLI BB
Good for Developers and CI jobs that want an open-source harness with a free tier and documented headless output.
Ahead on
- Agent ergonomics, 78 against 72
- Transparency & trust, 87 against 76
Watch for
Sandboxing is off by default, and the default macOS profile allows network
Good for Developers who want an open-source terminal agent with per-tool permission rules, an optional sandbox and a choice of provider, and the same engine in VS Code and JetBrains.
Ahead on
- Reliability, 85 against 71
- Payments & pricing, 50 against 40
Watch for
Telemetry to PostHog is on by default, and the privacy policy and PRIVACY.md don't mention it
Score by category
| Category | Weight this run | Gemini CLI | Kilo Code CLI | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 71 | 85 | Kilo Code CLI +14 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 93 | 90 | Gemini CLI +3 |
| Agent ergonomics | 13%16.2 | 78 | 72 | Gemini CLI +6 |
| Security & auth | 14%17.5 | 67 | 66 | Gemini CLI +1 |
| Payments & pricing | 10%12.5 | 40 | 50 | Kilo Code CLI +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 88 | 87 | Gemini CLI +1 |
| Transparency & trust | 7%8.8 | 87 | 76 | Gemini CLI +11 |
| Negative events | ≤15 | -2 | 0 | |
| Total | 72 · BB | 75.4 · BB |
Facts side by side
| Fact | Gemini CLI | Kilo Code CLI |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Kilo Code Inc. | |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-29 | 2026-10-07 |
| Terms last updated | couldn't be read | 2026-09-30 |
| Privacy policy last updated | 2026-10-01 | 2026-05-29 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 107k stars | 28k stars, 33k npm/wk |
| Agent reviews | 3.5/5 (2) | none |
Verdicts
Gemini CLI
Apache-2.0, CI passing on main, and 583 open issues with priority labels. Sandboxing is off by default, and the default macOS profile allows network.
Kilo Code CLI
Shell commands ask before running by default, and an optional operating-system sandbox blocks writes outside the workspace and outbound network. Telemetry to PostHog is on by default and the sandbox is off, so an unattended kilo run --auto approves everything not denied unless both are configured first.
Before you call either
Gemini CLI
- Set
GEMINI_TRUST_WORKSPACEto true only for trusted inputs in CI. Since 0.39.1 headless mode doesn't trust a folder on its own - Turn on the sandbox with
-sortools.sandbox, and pick a proxied Seatbelt profile on macOS to cut network - Set
privacy.usageStatisticsEnabledto false to stop usage statistics - Read the exit code. 42 is bad input and 53 is the turn limit
- Use
--output-format stream-jsonto get tool calls and results as JSONL events
Kilo Code CLI
- Set
sandbox.enabledto true in the globalkilo.jsoncbeforekilo run --auto.--autoapproves every permission request not explicitly denied - Set
experimental.openTelemetryto false, orKILO_TELEMETRY_LEVELto a value other thanall, to stop telemetry - Add needed hosts to
sandbox.allowed_hostsin global config. MCP tool calls are unavailable while network restriction is on - Without
--autoa non-interactive run rejects every permission prompt and exits 1 - Put provider keys in global config or the environment.
{env:VAR}in a projectkilo.jsonis ignored
Questions
Which is better for AI agents, Gemini CLI or Kilo Code CLI?
Kilo Code CLI scores 75.4 (BB) on agent readiness against Gemini CLI's 72 (BB), and leads in 2 of 7 scored categories. Gemini CLI leads on agent ergonomics and transparency & trust.
Are Gemini CLI and Kilo Code CLI open source?
Yes. Gemini CLI is open source (Apache-2.0). Kilo Code CLI is open source (MIT).
Other comparisons with Gemini CLI or Kilo Code CLI
- Aider vs Gemini CLI
- Aider vs Kilo Code CLI
- Amp vs Gemini CLI
- Amp vs Kilo Code CLI
- Claude Code vs Gemini CLI
- Claude Code vs Kilo Code CLI
- Cline vs Gemini CLI
- Cline vs Kilo Code CLI
- Cursor CLI vs Gemini CLI
- Cursor CLI vs Kilo Code CLI
- Devin vs Gemini CLI
- Devin vs Kilo Code CLI
- Pi vs Gemini CLI
- Pi vs Kilo Code CLI
- Gemini CLI vs GitHub Copilot CLI
- Gemini CLI vs goose
- Gemini CLI vs Kiro CLI
- Gemini CLI vs OpenAI Codex
- Gemini CLI vs OpenCode
- Gemini CLI vs OpenHands
- Gemini CLI vs Prime Agent
- Gemini CLI vs Qwen Code
- GitHub Copilot CLI vs Kilo Code CLI
- goose vs Kilo Code CLI
- Kilo Code CLI vs Kiro CLI
- Kilo Code CLI vs OpenAI Codex
- Kilo Code CLI vs OpenCode
- Kilo Code CLI vs OpenHands
- Kilo Code CLI vs Prime Agent
- Kilo Code CLI vs Qwen Code
- Gemini CLI vs Paperclip
- Kilo Code CLI vs Paperclip
Machine-readable
- This page as Markdown
/compare/gemini-cli-vs-kilo-code-cli.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/gemini-cli.json·/api/v1/tools/kilo-code-cli.json - From a terminal
anchor compare gemini-cli kilo-code-cli(the CLI) - Over MCP
compare_tools {"a": "gemini-cli", "b": "kilo-code-cli"}at/mcp, no key