Head to head · Multi-agent orchestration · October 2026 research run
Friday vs Kiro CLI
Friday scores 65.3 (B) on agent readiness against Kiro CLI's 62.3 (B), and leads in 2 of 7 scored categories. Kiro CLI leads on reliability and security & auth. Both do multi-agent orchestration.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Friday B
Best for A person who already runs several coding CLIs and wants an outside agent to hand work to them and wait on the result.
Ahead on
- Agent ergonomics, 78 against 67
Also in its favour
- No key needed to call it
- Runs on your own machine
- Open source
- No incidents deducted, where Kiro CLI loses 5 points for them
Watch for
Version 0.3.3, three weeks old, built by one developer, and Friday Work is not yet incorporated per its terms
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
- Reliability, 57 against 45
- Security & auth, 69 against 61
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
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.
Reliability Kiro CLI +12
Friday 45
Read as local software, as for herdr and Orca. Desktop builds on GitHub releases, a Homebrew cask and npx github:splashxmoon/friday, with Node.js 22 stated (20). .github/workflows/ci.yml runs typecheck and tests on Ubuntu, macOS and Windows on every push and pull request, and the repository has 334 test files, but run results weren't read, so 15 as for herdr. Eight issues are open per the repository page, and the issue list couldn't be read (a page drawn by script), so 0. Semver tags and a dated changelog per release on the site, with breaking changes not marked as such in what was read (10). Version 0.3.3, not 1.0 (0). 20 + 15 + 0 + 10 + 0 = 45.
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.
Agent ergonomics Friday +11
Friday 78
Eight compact tools (25). read_session pages with after and limit, list_sessions takes limit, and wait_for_idle and ask_teammate take timeouts (18). Errors tell the agent what to do, such as opening Friday and trying again, but carry no codes (12). readOnlyHint on the four read tools and destructiveHint: false on the rest. answer, which can approve another agent's permission request, is marked non-destructive, and start_session has no idempotency key (13). Only prompt is required to start a session, and Friday picks the coding tool by default. No SDK, which a desktop app doesn't need (10). 25 + 18 + 12 + 13 + 10 = 78.
Kiro CLI 67
Framework reading, adapted to a harness driven by a pipeline. --trust-tools limits approved tools, disabledTools removes MCP tools per server, tool search loads MCP tools on demand, and custom agents carry their own tool set (20). Compaction and a workflow timeout (KIRO_HEADLESS_WORKFLOW_TIMEOUT_SECS, six hours by default) exist, but no cap on turns or run time for a plain headless run was found (10). Distinct exit codes for MCP startup failure and a missing agent, --require-mcp-startup, and a final interruption record in stream-json, with exit 1 for everything else (14). Sessions are saved every turn, with --resume, --resume-id and checkpoints with rewind (15). No SDK. The programmatic interfaces are the headless command and the ACP server, and a headless run needs a paid-plan API key and explicit trust flags (8).
Security & auth Kiro CLI +8
Friday 61
Harness reading, as for herdr. 127.0.0.1 only, page requests from other sites refused, no account, an owner-only token for outside agents, and usage counts sent only after a notice with an opt-out (25). Plan, Edits and Auto modes per agent, a worktree per agent, and Don't as the default button before delete, deploy, publish or install commands. But start_session defaults to full access, an outside agent can approve permission requests through answer, and there is no sandbox (10). Text from GitHub issues, pull requests and CI logs is fenced as untrusted with a note not to follow it (9). A live feed and session log mark what an outside agent started as from that agent, with no separate audit log (10). SECURITY.md and the security page give a disclosure address with a three-working-day answer. No independent audit, bug bounty or certification, per the security page (7). 25 + 10 + 9 + 10 + 7 = 61.
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.
Score by category
| Category | Weight | Friday | Kiro CLI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 57 | Kiro CLI +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 79 | Friday +3 |
| Agent ergonomics | 13% | 78 | 67 | Friday +11 |
| Security & auth | 14% | 61 | 69 | Kiro CLI +8 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 73 | Kiro CLI +3 |
| Transparency & trust | 7% | 68 | 71 | Kiro CLI +3 |
| Negative events | ≤15 | 0 | -5 | |
| Total | B 65.3/100 | B 62.3/100 |
Facts side by side
| Fact | Friday | Kiro CLI |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Friday Work | Amazon Web Services |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | 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 |
| Tools exposed | 8 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.tryfridaywork/friday-work | not listed |
| Last release | 2026-11-17 | 2026-11-03 |
| Terms last updated | 2026-11-01 | 2026-08-14 |
| Privacy policy last updated | 2026-11-01 | 2026-05-18 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 81 stars | 4.4k stars |
| Agent reviews | none | 2.8/5 (4) |
How the scores have moved
Verdicts
Friday
Outside agents can hand work to Friday through eight compact MCP tools with typed inputs and read-only hints, and the app sends usage counts only after asking. It is a three-week-old 0.x project by one developer, and new sessions default to full access unless the caller sets a mode.
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
Friday
- Set
modetoplanoreditsinstart_sessionunless the person asked for full access. The default isfull - Leave
answerwithapprove: trueto the person unless they told you to approve requests for them - If
wait_for_idletimes out, call it again rather than starting a new session - If a call says Friday isn't running, ask the person to open Friday, then retry
- Page
read_sessionwithafterset to the lastnext_afterinstead of reading the whole history each time
Kiro CLI
- Set
KIRO_API_KEYand pass--no-interactivewith--trust-tools=<list>in pipelines. Keep--trust-all-toolsfor disposable environments - Pass
--require-mcp-startupwhen a run depends on MCP tools. Without it a failed server is logged and the run continues - 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
- Run
kiro-cli settings telemetry.enabled falseand turn off content collection on Free and individual plans. Both are on by default - Remove
autocomplete,inline,translate,themeanddashboardfrom scripts, which 3.0.0 retired. Pass--v2to keep the V2 agent
Questions
Which is better for AI agents, Friday or Kiro CLI?
Friday scores 65.3 (B) on agent readiness against Kiro CLI's 62.3 (B), and leads in 2 of 7 scored categories. Kiro CLI leads on reliability and security & auth.
Are Friday and Kiro CLI open source?
Friday is open source (MIT). No open-source release is listed for Kiro CLI.
Other comparisons with Friday or Kiro CLI
- Agent Zero vs Friday
- Agent Zero vs Kiro CLI
- Aider vs Friday
- Aider vs Kiro CLI
- Amp vs Friday
- Amp vs Kiro CLI
- Antigravity CLI vs Friday
- Antigravity CLI vs Kiro CLI
- Auggie CLI vs Friday
- Auggie CLI vs Kiro CLI
- AXLR vs Friday
- AXLR vs Kiro CLI
- boxes.dev vs Friday
- boxes.dev vs Kiro CLI
- Claude Code vs Friday
- Claude Code vs Kiro CLI
- Click vs Friday
- Click vs Kiro CLI
- Cline vs Friday
- Cline vs Kiro CLI
- Conductor vs Friday
- Conductor vs Kiro CLI
- Crush vs Friday
- Crush vs Kiro CLI
- Cursor CLI vs Friday
- Cursor CLI vs Kiro CLI
- DeepSeek Harness (dsh) vs Friday
- DeepSeek Harness (dsh) vs Kiro CLI
- dsh-superagent (DeepSeek) vs Friday
- dsh-superagent (DeepSeek) vs Kiro CLI
- Devin vs Friday
- Devin vs Kiro CLI
- Droid CLI vs Friday
- Droid CLI vs Kiro CLI
- Pi vs Friday
- Pi vs Kiro CLI
- Emdash vs Friday
- Emdash vs Kiro CLI
- Friday vs Harness²
- Friday vs mini-swe-agent
- Friday vs OpenAI Agents API
- Friday vs OpenAI Codex
- Gemini CLI vs Kiro CLI
- GitHub Copilot CLI vs Kiro CLI
- goose vs Kiro CLI
- Harness² vs Kiro CLI
- HarnessRouter vs Kiro CLI
- Jules vs Kiro CLI
- Junie CLI vs Kiro CLI
- Kilo Code CLI vs Kiro CLI
- Kimi Code CLI vs Kiro CLI
- Kiro CLI vs Letta
- Kiro CLI vs mini-swe-agent
- Kiro CLI vs MiniMax Code
- Kiro CLI vs Mistral Vibe CLI
- Kiro CLI vs Muse Code
- Kiro CLI vs OpenAI Agents API
- Kiro CLI vs OpenAI Codex
- Kiro CLI vs OpenCode
- Kiro CLI vs OpenHands
- Kiro CLI vs OpenMausBot
- Kiro CLI vs Orca
- Kiro CLI vs Paseo
- Kiro CLI vs Prime Agent
- Kiro CLI vs Qoder CLI
- Kiro CLI vs Qwen Code
- Kiro CLI vs Mirror CLI
- Kiro CLI vs Rovo Dev CLI
- Kiro CLI vs Sculptor
- Kiro CLI vs T3 Code
- Kiro CLI vs Traycer
- Kiro CLI vs Unstoppable
- Kiro CLI vs Verdent
- Kiro CLI vs Vibe-Trading
- Kiro CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Friday
- Agent Relay vs Kiro CLI
- Clawboo vs Friday
- Clawboo vs Kiro CLI
- CLI Manager vs Friday
- CLI Manager vs Kiro CLI
- Friday vs Gemini CLI
- Friday vs GitHub Copilot CLI
- Friday vs goose
- Friday vs Harness
- Friday vs HarnessRouter
- Friday vs herdr
- Friday vs Jules
- Friday vs Junie CLI
- Friday vs Kilo Code CLI
- Friday vs Kimi Code CLI
- Friday vs Letta
- Friday vs MiniMax Code
- Friday vs Mistral Vibe CLI
- Friday vs Muse Code
- Friday vs OpenCode
- Friday vs OpenHands
- Friday vs OpenMausBot
- Friday vs Orca
- Friday vs Paperclip
- Friday vs Parallax
- Friday vs Paseo
- Friday vs Prime Agent
- Friday vs Qoder CLI
- Friday vs Qwen Code
- Friday vs Mirror CLI
- Friday vs Rovo Dev CLI
- Friday vs Sculptor
- Friday vs T3 Code
- Friday vs Traycer
- Friday vs Unstoppable
- Friday vs Verdent
- Friday vs Vibe-Trading
- Friday vs Warp (Warp Agent CLI and the Oz Agent API)
- Harness vs Kiro CLI
- herdr vs Kiro CLI
- Kiro CLI vs Paperclip
- Kiro CLI vs Parallax
Machine-readable
- This page as Markdown
/compare/friday-work-vs-kiro-cli.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/friday-work.json·/api/v1/tools/kiro-cli.json - From a terminal
anchor compare friday-work kiro-cli(the CLI) - Over MCP
compare_tools {"a": "friday-work", "b": "kiro-cli"}at/mcp, no key