Get an audit

Head to head · Agent harness · October 2026 research run

Claude Code vs Kiro CLI

Claude Code scores 61.9 (C) on agent readiness against Kiro CLI's 59.9 (C), and leads in 5 of 7 scored categories. Kiro CLI leads on reliability and payments & pricing. Both do agent harness.

Claude CodeAnthropic · Agent harness C61.9/100#316 of 629 Kiro CLIAmazon Web Services · Agent harness C59.9/100#370 of 629

Which one, for what

Claude Code C

Good for A developer or a pipeline that wants Claude doing repository work with fine-grained, centrally managed permissions and an SDK for the same loop.

Ahead on

  • Agent ergonomics, 87 against 67
  • Security & auth, 80 against 66
  • Maintenance & community, 82 against 73
  • Transparency & trust, 81 against 67

Watch for

The sandbox is off by default and native Windows has none

Kiro CLI C

Good for Teams on AWS that want one agent configuration across terminal, IDE and web, with central permission policy, prompt logging to their own S3 bucket and IAM Identity Centre sign-in.

Ahead on

  • Reliability, 57 against 50
  • Payments & pricing, 40 against 20

Also in its favour

  • Free to start without a card

Watch for

Free and individual paid accounts have content used for service improvement, including model training, unless they opt out

Score by category

CategoryWeight this runClaude CodeKiro CLIEdge
Reliability16%205057Kiro CLI +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28079Claude Code +1
Agent ergonomics13%16.28767Claude Code +20
Security & auth14%17.58066Claude Code +14
Payments & pricing10%12.52040Kiro CLI +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88273Claude Code +9
Transparency & trust7%8.88167Claude Code +14
Negative events≤15-6-4
Total61.9 · C59.9 · C

Facts side by side

FactClaude CodeKiro CLI
KindAgent harnessAgent harness
VendorAnthropicAmazon Web Services
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary. LICENSE.md says All rights reserved, with use under Anthropic's Commercial Terms. The GitHub repository holds the changelog, plugins and examples, not the sourceProprietary. Licensed as AWS Content under the AWS Customer Agreement and the AWS Intellectual Property Licence (https://kiro.dev/license/). The GitHub repository is the public issue tracker and doesn't hold the source
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-012026-10-05
Terms last updatedno date given2026-08-14
Privacy policy last updatedno date given2026-05-18
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesyes
Popularity141k stars4.4k stars

Verdicts

Claude Code

Six permission modes, allow, ask and deny rules down to command arguments, PreToolUse hooks, and managed settings that can disable bypass and auto mode. The sandbox is off by default and native Windows has none.

Kiro CLI

Permission rules follow deny over ask over allow, cloned repositories can't add rules, and a headless session treats every ask as a deny. Content from Free and individual paid accounts is used for service improvement, including model training, unless the user opts out, and API keys for pipelines need a paid plan.

Before you call either

Claude Code

  1. Pass --permission-mode on every claude -p run. An unset mode can start in auto mode, depending on version, plan, provider and telemetry
  2. Turn on the sandbox with sandbox.enabled and set allowUnsandboxedCommands to false, or Claude can retry a blocked command outside it
  3. Set CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 on a Claude login to stop metrics and error reports in one go
  4. Set autoUpdatesChannel to stable or DISABLE_AUTOUPDATER=1 in CI. Native installs update themselves about once a day
  5. Cap pipeline runs with --max-turns and --max-budget-usd

Kiro CLI

  1. Set KIRO_API_KEY and pass --no-interactive with --trust-tools=<list> in pipelines. Keep --trust-all-tools for disposable environments
  2. Pass --require-mcp-startup when a run depends on MCP tools. Without it a failed server is logged and the run continues
  3. Pass --no-interactive whenever input is piped from a source you don't control, and run 2.10.0 or later on Windows
  4. Run kiro-cli settings telemetry.enabled false and turn off content collection on Free and individual plans. Both are on by default
  5. Export variables in the shell before starting. Since 2.24.0 a project .env file is no longer loaded into sessions, MCP servers or tools

Questions

Which is better for AI agents, Claude Code or Kiro CLI?

Claude Code scores 61.9 (C) on agent readiness against Kiro CLI's 59.9 (C), and leads in 5 of 7 scored categories. Kiro CLI leads on reliability and payments & pricing.

Other comparisons with Claude Code or Kiro CLI

Disclosure

Anthropic makes the models this research run and the review panel run on. This listing was graded by agents running on Claude, by the same published checklist as every other listing, and the panel doesn't review it, because every reviewer runs on Claude too.

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report