Get an audit

Head to head · Agent harness · October 2026 research run

Pi vs Kiro CLI

Pi scores 68.4 (B) on agent readiness against Kiro CLI's 59.9 (C), and leads in 5 of 7 scored categories. Kiro CLI leads on security & auth. Both do agent harness.

PiEarendil · Agent harness B68.4/100#180 of 722 Kiro CLIAmazon Web Services · Agent harness C59.9/100#419 of 722

Which one, for what

Pi B

Good for Developers and pipelines that want a small, scriptable coding agent they can extend in TypeScript and drive over JSONL or RPC, inside their own container.

Ahead on

  • Reliability, 75 against 57
  • Schema & documentation, 84 against 79
  • Agent ergonomics, 76 against 67
  • Payments & pricing, 60 against 40
  • Maintenance & community, 87 against 73

Also in its favour

  • No key needed to call it
  • Open source

Watch for

No permission system or sandbox. Tool calls run with the user's rights and without an approval prompt

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

  • Security & auth, 66 against 61

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 runPiKiro CLIEdge
Reliability16%207557Pi +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28479Pi +5
Agent ergonomics13%16.27667Pi +9
Security & auth14%17.56166Kiro CLI +5
Payments & pricing10%12.56040Pi +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88773Pi +14
Transparency & trust7%8.86467Kiro CLI +3
Negative events≤15-4-4
Total68.4 · B59.9 · C

Facts side by side

FactPiKiro CLI
KindAgent harnessAgent harness
VendorEarendilAmazon Web Services
Hosted endpointno (local only)no (local only)
Transports
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceMITProprietary. 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.txtnoyes
Last release2026-10-072026-10-05
Terms last updatedno document linked2026-08-14
Privacy policy last updatedno document linked2026-05-18
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waiveryes
Popularity113k stars, 5.2M npm/wk4.4k stars

Verdicts

Pi

Four default tools, a JSONL event stream, an RPC mode and MCP tools kept out of the model's declarations by default keep context small and scripting simple. Pi has no permission system or sandbox and doesn't ask before tool calls, so isolation is the operator's job. Version 1.0.0 is dated 1 October 2026.

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

Pi

  1. Run Pi inside a container or VM for unattended work. It has no sandbox and doesn't ask before running shell commands
  2. Use pi --mode json and wait for agent_settled. A failed response doesn't set a nonzero exit code in JSON mode
  3. Split the JSONL stream on LF only. Node's readline also splits on U+2028 and U+2029, which are valid inside JSON strings
  4. Pass --no-approve or --approve in scripts to make the project trust decision explicit
  5. Set PI_TELEMETRY=0 and PI_SKIP_VERSION_CHECK=1, or PI_OFFLINE=1, to stop the default requests to pi.dev

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, Pi or Kiro CLI?

Pi scores 68.4 (B) on agent readiness against Kiro CLI's 59.9 (C), and leads in 5 of 7 scored categories. Kiro CLI leads on security & auth.

Are Pi and Kiro CLI open source?

Pi is open source (MIT). No open-source release is listed for Kiro CLI.

Other comparisons with Pi or Kiro CLI

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