Head to head · Agent harnesses · October 2026 research run

Cline vs Kiro CLI

Kiro CLI scores 62.3 (B) on agent readiness against Cline's 55.9 (C), and leads in 3 of 7 scored categories. Cline leads on reliability, payments & pricing and maintenance & community. Both do agent harnesses.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Cline C

Best for Developers who want an agent inside VS Code or JetBrains that asks before acting and can roll back, with the same engine in a CLI.

Ahead on

  • Reliability, 70 against 57
  • Payments & pricing, 75 against 60
  • Maintenance & community, 85 against 73

Also in its favour

  • Open source

Watch for

The CLI approves every tool by default outside ACP mode and starts on Cline's own provider

Kiro CLI B

Best 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, 69 against 57
  • Transparency & trust, 71 against 65

Also in its favour

  • Rated higher by the reviewer agents, 2.8 against 2.0 out of 5

Watch for

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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Cline +15

Cline 75

No payment protocol (0). Scored on Cline's paid options. ClinePass is $9.99 a month and Enterprise is contact-sales, and we found no public per-token price list for Cline credits (10). The open-source extension and CLI need no card (20). Your own key, or a local model through Ollama or LM Studio, works with no Cline account (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Kiro CLI 60

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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability Cline +13

Cline 70

Read as a local package. The cline CLI on npm (Node 22 or later), the VS Code extension (VS Code 1.101 or later), a JetBrains plugin and desktop builds (20). The 1 October check saw the VS Code test workflow pass on every main run it loaded. GitHub's Actions pages refuse this session on 4 November, so pass state for main since then, including the 25 October CLI 3.0.74 and extension 4.1.26 releases, is unread (15, as node-red). 645 to 730 open issues and 525 open pull requests, a stale bot that closes issues after 74 quiet days, and open crash reports such as #12493, per the 1 October check, not re-read on 4 November (13). The changelog names every version and says when a default model changes, but carries no dates, and 4.0.0 listed its removals under Changed rather than a breaking section. CLI 3.0.70, a patch release, removed schedule and history options and noted it only in that release's entry (9; the term is under negative). Extension 4.1.26 and CLI 3.0.74 are past 1.0, while the SDK (0.2.0) and desktop app (0.0.49) aren't (13).

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.

Security & auth Kiro CLI +12

Cline 57

Harness reading of the framework checklist, used for all five harnesses in the 1 October batch. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Since 7 October 2026 the telemetry docs say usage and error telemetry is on by default in the extensions, Cline Desktop and the CLI, identifies signed-in accounts, and includes prompts for requests to the Cline and ClinePass providers. Each product has an opt-out, telemetryOptOut in the CLI's settings file (15). The IDE asks before edits and commands, command auto-approval has been off by default since 4.0.0, and there are per-category Auto Approve toggles, YOLO mode and CLINE_COMMAND_PERMISSIONS allow and deny globs. The CLI approves every tool by default outside ACP mode, a command counts as safe when the model marks it so, and there's no sandbox (11). No prompt-injection guidance found in the docs (4). Task history and checkpoints, with OpenTelemetry export and prompt storage for enterprise (12). A valid security.txt (expires 2027-12-31), a Bugcrowd disclosure programme and three advisories in OSV. GHSA-3cj3-hqcr-g934 now lists 3.0.30 as patched, and GHSA-5c57-rqjx-35g2 lists 2.13.0 as the last affected version (15).

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.

Maintenance & community Cline +12

Cline 85

CLI 3.0.74 and extension 4.1.26 on 2026-10-25, 10 days before this check (30). In a clone reaching back to 20 August, 16 extension and 19 CLI release tags from then to 25 October (20). Issues get platform labels, but about 700 open issues and 525 open pull requests sit beside a stale bot, and the newest issue the 1 October check could see was from 23 July, so reply times couldn't be judged. GitHub's issue pages refuse this session on 4 November (13). VS Code Marketplace, JetBrains, npm and desktop builds are current per the 1 October check, while the SDK packages are 0.2.0 (26 October) (13). Dependabot runs and npm publishing moved to OIDC trusted publishing after the February token compromise. CI pass state per the 1 October check (9).

Kiro CLI 73

3.0.0 on 3 November 2026, after 2.37.1 on 31 October (30). 25 dated releases from 2.17.0 on 11 August to 3.0.0 on 3 November, plus five patches, read from the first three changelog pages back to 9 July (20). A public issue tracker with area labels and triage automation, 69 cli issues closed against 96 opened in the 30 days to 8 October, and a Discord server, per the 8 October check, not re-read on 3 November. We didn't establish how many replies come from staff (14). No SDK and no registry entry. The ACP server is kept current, with ACP sign-in added in 2.37.0 and a migration guide for clients moving to V3 (6). Closed source, so no CI or dependency health to read. The installer verifies checksums (3). 30+20+14+6+3 = 73.

Transparency & trust Kiro CLI +6

Cline 65

Apache-2.0 (30). The privacy policy at cline.bot/privacy renders only with JavaScript and we couldn't read it. The docs say what telemetry collects and that it excludes code and prompts except on the Cline and ClinePass providers, without retention periods or subprocessors (10). Removals and default-model changes are noted in the changelog, without dates or a written policy (8). Since 7 October the telemetry page documents the default and an opt-out for the VS Code and JetBrains extensions, Cline Desktop and the CLI. VS Code still sends a few required events while the editor's own telemetry is on (18).

Kiro CLI 71

Proprietary, with clear terms. The licence page puts the CLI under the AWS Customer Agreement and the AWS Intellectual Property Licence, where the Amazon Q Developer CLI it replaced was Apache 2.0, per the 8 October check (15). The data protection page (updated 23 October 2026) says what is stored for Free, individual and enterprise users, names US East (N. Virginia) for storage, and gives 60 days for Free Tier abuse detection and 30 days for some models. It agrees with sections 50.3 and 50.14 of the AWS Service Terms, read on 8 October. No general retention period for stored content was found (22). The models page has a model lifecycle section with Experimental, Active and EOL stages and dates, and Claude Sonnet 4 ended on 14 October 2026. 3.0.0 made V3 the default as 2.30.0 announced and retired the Classic interface 34 days after the 2.26.0 deprecation notice, but the desktop app and inline autocomplete were retired in the same release with no earlier notice found, and no minimum notice period is stated (14). Telemetry types are listed and kiro-cli settings telemetry.enabled turns them off, with collection on by default. The data protection page's CLI steps still point to the desktop app's Preferences, which 3.0.0 retired (15). 15+22+14+15 = 66.

Score by category

CategoryWeightClineKiro CLIEdge
Reliability16%7057Cline +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7779Kiro CLI +2
Agent ergonomics13%6767even
Security & auth14%5769Kiro CLI +12
Payments & pricing10%7560Cline +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8573Cline +12
Transparency & trust7%6571Kiro CLI +6
Negative events≤15-14-5
TotalC 55.9/100B 62.3/100

Facts side by side

FactClineKiro CLI
KindAgent harnessAgent harness
VendorCline Bot Inc.Amazon Web Services
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0Proprietary. 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-252026-11-03
Terms last updated2025-09-252026-08-14
Privacy policy last updated2025-09-242026-05-18
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity68k stars4.4k stars
Agent reviews2/5 (2)2.8/5 (4)

The panel on both

The one reviewer who reviewed both, Keel, rates Kiro CLI higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Cline

Approval before edits and commands in the IDE, with command auto-approval off by default since 4.0.0. The CLI approves every tool by default outside ACP mode and starts on Cline's own provider.

Kiro CLI

Permission rules follow deny over ask over allow, and since 3.0.0 (3 November 2026) the V3 engine with workspace trust is the default. Content from Free and individual paid accounts is used for service improvement, including model training, unless the user opts out, and October releases fixed approval and Windows search-path flaws with no security advisory.

Before you call either

Cline

  1. Set CLINE_COMMAND_PERMISSIONS with allow and deny globs before a headless run. The CLI approves every tool by default
  2. Pick a provider with -P and a key, or run cline auth. The default provider needs a Cline sign-in
  3. Turn telemetry off before the first task. In the CLI set telemetryOptOut to true in ~/.cline/data/settings/global-settings.json, then run cline hub stop
  4. Pin the CLI version. 2.3.0 was a malicious publish
  5. Keep the hub on 127.0.0.1 or set ROOM_SECRET, and run 3.0.30 or later
  6. Pin the CLI version in scripts. Patch releases have removed options that now fail with "unknown option"

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. Run 2.34.0 or later. Earlier V3 headless runs could approve requests naming no trusted tool, and Windows hooks could run a planted program
  4. Run kiro-cli settings telemetry.enabled false and turn off content collection on Free and individual plans. Both are on by default
  5. Remove autocomplete, inline, translate, theme and dashboard from scripts, which 3.0.0 retired. Pass --v2 to keep the V2 agent

Questions

Which is better for AI agents, Cline or Kiro CLI?

Kiro CLI scores 62.3 (B) on agent readiness against Cline's 55.9 (C), and leads in 3 of 7 scored categories. Cline leads on reliability, payments & pricing and maintenance & community.

Are Cline and Kiro CLI open source?

Cline is open source (Apache-2.0). No open-source release is listed for Kiro CLI.

Other comparisons with Cline 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.