# Kiro CLI vs Paseo (slim)

> Paseo scores 62.1 (B) to Kiro CLI's 59.8 (C) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/kiro-cli-vs-paseo.md (~5,450 tokens) · this version ~1,980 tokens · JSON https://www.anchorterminal.com/compare/kiro-cli-vs-paseo.json · canonical https://www.anchorterminal.com/compare/kiro-cli-vs-paseo
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Paseo scores 62.1 (B) on agent readiness against Kiro CLI's 59.8 (C), and leads in 3 of 7 scored categories. Kiro CLI leads on reliability, schema & documentation and security & auth. Both do agent harnesses.

- Kiro CLI: C 59.8, rank #675 of 1486 · https://www.anchorterminal.com/tools/kiro-cli.min.md
- Paseo: B 62.1, rank #575 of 1486 · https://www.anchorterminal.com/tools/paseo.min.md
- Kiro CLI, 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; Schema & documentation, 79 against 65; Security & auth, 69 against 58. Also Free to start without a card.
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Payments & pricing, 60 against 40. Also No key needed to call it; Open source; No incidents deducted, where Kiro CLI loses 5 points for them.

| Category | Kiro CLI | Paseo |
| --- | --- | --- |
| Reliability (16%) | 57 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 79 | 65 |
| Agent ergonomics (13%) | 67 | 70 |
| Security & auth (14%) | 69 | 58 |
| Payments & pricing (10%) | 40 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 73 | 75 |
| Transparency & trust (7%) | 71 | 68 |

| Fact (where they differ) | Kiro CLI | Paseo |
| --- | --- | --- |
| Vendor | Amazon Web Services | Mohamed Boudra |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| Licence | Proprietary. 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 | Apache-2.0 |
| llms.txt | yes | no |
| Last release | 2026-11-03 | 2026-11-07 |
| Terms last updated | 2026-08-14 | no document linked |
| Privacy policy last updated | 2026-05-18 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 4.4k stars | none |
| Agent reviews | 2.8/5 (4) | none |

Why the edge:
- Payments & pricing, Paseo +20: Kiro CLI 40 (Harness reading of the published rubric, scored on the Kiro subscription the CLI needs. No payment protocol (0). Plan prices, the $0.04 credit price and per-model credit multipliers are public without a login (20). Kiro Free has 50 credits a month, and the pricing page asks for a card only on upgrade (20). A person signs in through a browser or device flow, and the API key for headless runs is created by hand at app.kiro.dev on a paid plan (0).); Paseo 60 (Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.)
- Schema & documentation, Kiro CLI +14: Kiro CLI 79 (Framework reading. A command reference, a settings reference, an exit-code page and a documented rule format for permissions, plus the Agent Client Protocol methods the CLI implements. No published schema for the stream-json events was found (14). kiro.dev/llms.txt indexes every docs page and each has a Markdown twin, though robots.txt disallows both for crawlers (10). The permissions page states the defaults, what each preset allows and when to pick it, and that headless runs treat ask as deny (16). Rules are validated, an unknown preset rejects the session request, and a malformed managed policy fails closed (12). CI examples, exit codes 0, 1, 3 and 4 and hook exit codes are documented, but code 1 covers every other failure (12). Versioned releases with a dated changelog and a 2.x reference kept beside V3 (15).); Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).)
- Security & auth, Kiro CLI +11: Kiro CLI 69 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Telemetry and content collection are on by default for Free and individual accounts, each with a documented opt-out, and enterprise users are opted out. API keys are long-lived and revocable with no scopes, and administrators must switch key generation on (14). Deny over ask over allow across six scopes, hard-coded denies on Kiro's own settings paths, workspace trust and a managed policy that fails closed. V3 is the default since 3.0.0 (3 November 2026), interactive V3 sessions ask before loading a folder's hooks, agents and MCP servers since 2.33.0, and `/sandbox` puts agent shell commands and local stdio MCP servers in an operating-system sandbox. The sandbox is off unless chosen and doesn't cover the agent, built-in file tools or remote MCP servers, and AWS says managed policies are client-enforced and can be circumvented (17). An untrusted workspace doesn't load its agents, steering, MCP configuration or skills, compound shell commands are split before matching, and the MCP page warns that servers run outside any sandbox (11). Enterprise prompt logging to the customer's S3 bucket covers the CLI, with daily activity reports and OpenTelemetry export, and individuals have local logs only (11). AWS vulnerability reporting through a HackerOne disclosure programme with no paid bounty, CVEs published in security bulletins with credit to reporters, ISO/IEC 27001:2022 scope and HIPAA eligibility. The aws.amazon.com security.txt is valid (Expires 2027-10-16) and kiro.dev/.well-known/security.txt answers 404, so 2 are held back for that and 2 for no bounty (16). 14+17+11+11+16 = 69.); Paseo 58 (Harness reading. The README says no telemetry, tracking or forced log-ins (30 of 30). Worktree per agent, on your own machine (10 of 20). No prompt-injection guidance (5). No audit log (5). SECURITY.md (8). 30 + 10 + 5 + 5 + 8 = 58.)
- Reliability, Kiro CLI +7: Kiro CLI 57 (Local-package reading, the same as the other closed-source harnesses. An install script that verifies SHA-256 checksums, a .deb, an AppImage and a PowerShell script, with macOS, Windows 11 and Linux (glibc 2.34 or newer, or musl) stated, per the 8 October check (20). No public CI or test suite, since the source isn't published and the GitHub repository is an issue tracker whose newest commit is 27 August (0). Per the 8 October check, not re-read on 3 November, 1,401 open issues in the shared Kiro tracker, 428 labelled cli, with 96 cli issues opened and 69 closed in the 30 days to 8 October, area labels, a triage label and stale-issue automation (12). A dated changelog for every release, and 3.0.0 lists its breaking changes under their own heading with a migration route, though 2.24.0 stopped loading project `.env` files in a minor version (10). 3.0.0 on 3 November 2026 makes V3 the default engine (15). 20+0+12+10+15 = 57.); Paseo 50 (Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.)