{
  "data": {
    "a": {
      "slug": "friday-work",
      "name": "Friday",
      "vendor": "Friday Work",
      "vendorUrl": "https://www.tryfridaywork.com",
      "company": "tryfridaywork.com",
      "kind": "harness",
      "category": "agent-harnesses",
      "summary": "Friday is a free, MIT-licensed desktop app that runs Claude Code, Codex, Cursor and other coding agents as one team on a person's own computer. Outside agents drive it through a local stdio MCP server.",
      "url": "https://www.anchorterminal.com/tools/friday-work",
      "markdownUrl": "https://www.anchorterminal.com/tools/friday-work.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/friday-work.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/friday-work.json",
      "dns": "friday-work.grade.anchorterminal.com",
      "repo": "https://github.com/splashxmoon/friday",
      "license": "MIT",
      "transports": [
        "stdio"
      ],
      "packages": [],
      "auth": "none",
      "authNotes": "No account for the open-source app. Its server listens on 127.0.0.1 only and refuses requests from other web pages. The outside MCP server reads a random token from `~/.friday/outside-token`, created owner-only (0600), on each call, so an agent's MCP config holds only a path. The coding tools Friday runs keep their own sign-ins. The hosted Friday Team uses accounts and scoped OAuth, by arrangement only.",
      "pricing": "free",
      "pricingNotes": "The app is free and MIT licensed, with no account and no card. It runs the coding tools a person already pays for. Friday Team, the hosted multi-person version, is sold to companies on request, with the price agreed in writing, and new self-service sign-ups are closed per the terms of 1 November 2026.",
      "priceSummary": "Free · OSS",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "Local software with nothing to buy. No x402, MPP or L402 in the repository or on tryfridaywork.com, read on 2026-11-18.",
        "endpoints": []
      },
      "toolCount": 8,
      "popularity": {
        "githubStars": 81,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://www.tryfridaywork.com/docs",
      "llmsTxt": "https://www.tryfridaywork.com/llms.txt",
      "registryName": "com.tryfridaywork/friday-work",
      "capabilities": [
        "agent.multi-agent",
        "agent.harness"
      ],
      "tags": [
        "open-source",
        "mit",
        "local",
        "free",
        "desktop-app",
        "mcp",
        "stdio",
        "typescript",
        "pre-1.0",
        "macos",
        "windows",
        "linux",
        "llms-txt",
        "mcp-registry"
      ],
      "lastRelease": "2026-11-17",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 65.3,
        "grade": "B",
        "agentReady": false,
        "rank": 544,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 17,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 78,
          "maintenance": 70,
          "payments": 60,
          "reliability": 45,
          "schema": 82,
          "security": 61,
          "transparency": 68
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "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.",
        "bestFor": "A person who already runs several coding CLIs and wants an outside agent to hand work to them and wait on the result.",
        "strengths": [
          "Eight compact outside-agent MCP tools with typed JSON Schema inputs, `readOnlyHint` on the four read tools and paging on `read_session`",
          "MIT licensed, with no account, a server on 127.0.0.1 only and an owner-only token file for outside agents",
          "Usage counts go to PostHog only after the person answers a notice, never include code or prompts, and turn off with `FRIDAY_NO_TELEMETRY=1`",
          "Text from GitHub issues, pull requests and CI logs is fenced as untrusted before an agent reads it",
          "36 releases between 26 October and 17 November 2026, with a dated changelog and CI on Linux, macOS and Windows"
        ],
        "weaknesses": [
          "Version 0.3.3, three weeks old, built by one developer, and Friday Work is not yet incorporated per its terms",
          "`start_session` defaults to `full` mode, so the coding agent edits files and runs commands without asking unless the caller sets a mode",
          "The `answer` tool lets an outside agent approve another agent's permission requests, and it isn't marked destructive",
          "No sandbox, no independent security audit, and the Windows installer isn't signed",
          "The outside MCP server is documented only in one README line, not on the docs site"
        ],
        "agentNotes": [
          "Set `mode` to `plan` or `edits` in `start_session` unless the person asked for full access. The default is `full`",
          "Leave `answer` with `approve: true` to the person unless they told you to approve requests for them",
          "If `wait_for_idle` times 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_session` with `after` set to the last `next_after` instead of reading the whole history each time"
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 65.3
          }
        ],
        "editorialScores": {
          "ergonomics": 78,
          "maintenance": 70,
          "payments": 60,
          "reliability": 45,
          "schema": 82,
          "security": 61,
          "transparency": 77
        },
        "provenanceScore": 58,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "lastMoved": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npx github:splashxmoon/friday   # needs Node.js 22 and Git, or use the desktop app from github.com/splashxmoon/friday/releases",
        "claudeCode": "claude mcp add friday --scope user -- node ~/.friday/outside-mcp.mjs",
        "config": {
          "mcpServers": {
            "friday": {
              "args": [
                "~/.friday/outside-mcp.mjs"
              ],
              "command": "node"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/agent.multi-agent",
        "tool": "https://letme.dev/friday-work"
      },
      "area": "frameworks",
      "provenance": {
        "legalEntity": "Friday Work (not yet incorporated, per its terms of 1 November 2026)",
        "domain": "tryfridaywork.com",
        "domainRegistered": "",
        "endpointOnVendorDomain": null,
        "terms": "https://www.tryfridaywork.com/terms",
        "privacy": "https://www.tryfridaywork.com/privacy",
        "statusPage": "",
        "changelog": "https://www.tryfridaywork.com/changelog",
        "securityTxt": "unknown",
        "checked": "2026-11-18",
        "notes": [
          "The terms say Friday Work is not yet incorporated and that the company name, address and governing law will be added once it is. The about page names Arun Dass as founder, working alone, and the LICENSE carries his name.",
          "www.tryfridaywork.com/robots.txt allows all agents, with `Content-Signal: search=yes, ai-input=yes, ai-train=yes`.",
          "Local software, so there is no vendor endpoint or status page for the app. The hosted Friday Team server at www.app.tryfridaywork.com/mcp wasn't contacted, since its docs aren't public.",
          "security.txt wasn't requested. SECURITY.md and the security page give security@tryfridaywork.com with a three-working-day answer."
        ],
        "score": 58
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/friday-work.json",
      "live": {
        "slug": "friday-work",
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "com.tryfridaywork/friday-work",
            "version": "0.1.73",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          }
        ],
        "updatedAt": "2026-11-18T22:45:57.054523297Z"
      }
    },
    "answer": "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 \u0026 auth.",
    "b": {
      "slug": "kiro-cli",
      "name": "Kiro CLI",
      "vendor": "Amazon Web Services",
      "vendorUrl": "https://kiro.dev/cli/",
      "company": "amazon.com",
      "kind": "harness",
      "category": "agent-harnesses",
      "summary": "AWS's coding agent for the terminal and the successor to the Amazon Q Developer CLI. It runs interactive chat, non-interactive runs for pipelines with an API key, MCP servers and an Agent Client Protocol server for editors.",
      "url": "https://www.anchorterminal.com/tools/kiro-cli",
      "markdownUrl": "https://www.anchorterminal.com/tools/kiro-cli.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kiro-cli.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kiro-cli.json",
      "dns": "kiro-cli.grade.anchorterminal.com",
      "repo": "https://github.com/kirodotdev/Kiro",
      "license": "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",
      "transports": [],
      "packages": [],
      "auth": "mixed",
      "authNotes": "`kiro-cli login` with GitHub, Google, AWS Builder ID, AWS IAM Identity Centre or an external identity provider, in a browser or by device flow on a remote machine. Pipelines use an API key in `KIRO_API_KEY`, created at app.kiro.dev by Pro, Pro+, Pro Max and Power subscribers. Keys are long-lived, named and revocable, with no scopes, and API key generation is off by default for subscriptions an administrator manages. An active browser session takes precedence over the key.",
      "pricing": "freemium",
      "pricingNotes": "Kiro Free is $0 with 50 credits a month and a reduced model list. Pro is $20 a user a month with 1,000 credits, Pro+ $40 with 2,000, Pro Max $100 with 5,000 and Power $200 with 10,000, and extra credits cost $0.04 each. Models use credits at different rates (Auto is the 1.0x baseline). API keys for headless runs need a paid plan, and a paid plan needs a card. GovCloud prices are about 20 per cent higher with no free tier (checked 2026-10-08).",
      "priceSummary": "$20 / mo",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs, the pricing page or the CLI changelog (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 4356,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://kiro.dev/docs/cli/",
      "llmsTxt": "https://kiro.dev/llms.txt",
      "capabilities": [
        "agent.harness",
        "agent.mcp-client",
        "agent.multi-agent"
      ],
      "tags": [
        "official",
        "harness",
        "coding-agent",
        "cli",
        "closed-source",
        "mcp",
        "acp",
        "llms-txt",
        "free-tier",
        "no-card",
        "telemetry-default-on"
      ],
      "lastRelease": "2026-11-03",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.3,
        "grade": "B",
        "agentReady": false,
        "rank": 686,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 22,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 67,
          "maintenance": 73,
          "payments": 60,
          "reliability": 57,
          "schema": 79,
          "security": 69,
          "transparency": 71
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-03"
        },
        "negative": -5,
        "negativeNotes": [
          "2026-10-23. Released fixes with no advisory, one term. 2.33.0 (20 October 2026) says V3 hook commands on Windows no longer run a same-named program from the working directory and the semantic-search model download no longer extracts a file outside its model directory. 2.34.0 (23 October) says V3 headless mode no longer approves requests that name no trusted tool and remote HTTP MCP servers follow only same-origin redirects. No AWS bulletin or CVE covers them on 3 November (https://kiro.dev/changelog/cli/2-34/). -3",
          "2026-08-04. CVE-2026-18657 (bulletin 2026-074-AWS, High, CVSS 3.1 7.8), an uncontrolled search path on Windows let a planted executable in a crafted project directory run when a user started Kiro CLI there. Kiro CLI for Windows before 2.10.0. CVE-2026-18656 in the same bulletin is the Kiro IDE record. Fixed and published with credit to the reporter, over two months ago (https://aws.amazon.com/security/security-bulletins/2026-074-aws/). -1",
          "2026-05-22. CVE-2026-9255 (bulletin 2026-035-AWS, High, CVSS 3.1 7.8), content piped to kiro-cli on stdin could answer the tool approval prompt, so a local actor could run tools and shell commands without the user's approval. kiro-cli before 1.28.0. Fixed and published, over two months ago (https://aws.amazon.com/security/security-bulletins/2026-035-aws/). -1"
        ],
        "verdict": "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.",
        "bestFor": "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.",
        "strengths": [
          "Capability permissions with deny over ask over allow, stored outside the repository so a clone can't add rules",
          "An untrusted workspace doesn't load its own agents, steering files, MCP configuration or skills, and asks before every shell command",
          "Headless runs with `--no-interactive`, JSON Lines output, and exit codes 3 and 4 for MCP startup and missing-agent failures",
          "25 dated releases between 11 August and 3 November 2026, with 3.0.0's breaking changes listed in the release",
          "Plan prices, the $0.04 credit price and per-model credit multipliers are public, with a free tier of 50 credits a month"
        ],
        "weaknesses": [
          "Free and individual paid accounts have content used for service improvement, including model training, unless they opt out",
          "Closed source since it replaced the Apache 2.0 Amazon Q Developer CLI, with no public CI or test suite",
          "API keys for headless runs need a paid plan, are long-lived and carry no scopes",
          "The local command sandbox is off unless chosen even with V3 the default, and AWS says managed permission policies are client-enforced",
          "Two CLI CVEs in 2026, both fixed, and fixes for a Windows search-path flaw and a headless approval flaw in October with no advisory"
        ],
        "agentNotes": [
          "Set `KIRO_API_KEY` and pass `--no-interactive` with `--trust-tools=\u003clist\u003e` in pipelines. Keep `--trust-all-tools` for disposable environments",
          "Pass `--require-mcp-startup` when 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 false` and turn off content collection on Free and individual plans. Both are on by default",
          "Remove `autocomplete`, `inline`, `translate`, `theme` and `dashboard` from scripts, which 3.0.0 retired. Pass `--v2` to keep the V2 agent"
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 2.8,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.3
          }
        ],
        "editorialScores": {
          "ergonomics": 67,
          "maintenance": 73,
          "payments": 60,
          "reliability": 57,
          "schema": 79,
          "security": 69,
          "transparency": 66
        },
        "provenanceScore": 76,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-03",
            "maintenance": "2026-11-03",
            "payments": "2026-11-03",
            "reliability": "2026-11-03",
            "schema": "2026-11-03",
            "security": "2026-11-03",
            "transparency": "2026-11-03"
          },
          "last": "2026-11-03",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-03",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "curl -fsSL https://cli.kiro.dev/install | bash",
        "headless": {
          "run": "KIRO_API_KEY=ksk_... kiro-cli chat --no-interactive --trust-tools=read,grep \"Find all TODO comments in src/\""
        }
      },
      "letme": {
        "capability": "https://letme.dev/agent.harness",
        "tool": "https://letme.dev/kiro-cli"
      },
      "sameCompany": [
        "amazon-bedrock",
        "amazon-nova-embeddings",
        "amazon-bedrock-customization",
        "amazon-bedrock-guardrails",
        "amazon-transcribe",
        "amazon-polly",
        "amazon-nova-sonic",
        "strands-agents",
        "agentcore-code-interpreter",
        "agentcore-memory",
        "agentcore-identity",
        "aws-secrets-manager",
        "agentcore-web-search",
        "amazon-textract",
        "aws-mcp-servers",
        "amazon-ses",
        "aws-end-user-messaging",
        "amazon-location",
        "amazon-translate",
        "amazon-sns",
        "amazon-s3",
        "strands-decider",
        "amazon-ads-api",
        "amazon-eventbridge",
        "amazon-creators-api"
      ],
      "area": "frameworks",
      "unitPrices": [
        {
          "item": "Kiro Pro",
          "unit": "month",
          "usd": 20,
          "note": "per user, with 1,000 credits"
        },
        {
          "item": "Add-on credit",
          "unit": "credit",
          "usd": 0.04,
          "note": "paid plans, beyond the plan's credits"
        }
      ],
      "provenance": {
        "legalEntity": "Amazon Web Services, Inc.",
        "domain": "kiro.dev",
        "domainRegistered": "2019-03-01",
        "endpointOnVendorDomain": null,
        "terms": "https://aws.amazon.com/agreement/",
        "privacy": "https://aws.amazon.com/privacy/",
        "statusPage": "",
        "changelog": "https://kiro.dev/changelog/cli/",
        "securityTxt": "none",
        "checked": "2026-11-03",
        "notes": [
          "Kiro's licence page says the Kiro IDE and CLI are licensed as AWS Content under the AWS Customer Agreement and the AWS Intellectual Property Licence. Section 50.14 of the AWS Service Terms names Amazon Web Services, Inc. as the contracting party for subscriptions bought through the Stripe portal.",
          "The AWS Customer Agreement (last updated 14 August 2026) governs use, with the AWS Service Terms sections 50.3 and 50.14 for Kiro. The AWS Privacy Notice (last updated 18 May 2026) is the privacy link in Kiro's footer.",
          "kiro.dev/.well-known/security.txt answered 404 on 3 November. aws.amazon.com publishes a valid security.txt, with Expires 2027-10-16 and a Policy of https://vdp.aws.security/.",
          "No status page for Kiro was found on kiro.dev or in its docs.",
          "RDAP (Google Registry) gives kiro.dev a registration date of 1 March 2019, before the product."
        ],
        "score": 76
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/kiro-cli.json",
      "live": {
        "slug": "kiro-cli",
        "githubStars": 4483,
        "securityTxt": {
          "url": "https://kiro.dev/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:29:42.826164565Z"
        },
        "llmsTxt": {
          "url": "https://kiro.dev/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:14:47.048338053Z"
        },
        "domain": {
          "domain": "kiro.dev",
          "registered": "2019-03-01",
          "source": "https://pubapi.registry.google/rdap/domain/kiro.dev",
          "checkedAt": "2026-11-15T15:33:50.904193374Z"
        },
        "pages": [
          {
            "url": "https://kiro.dev/changelog/cli/",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-11-18T21:45:54.594956202Z",
            "changedAt": "2026-11-18T21:45:54.594956202Z",
            "fingerprint": "4c8825d46976"
          },
          {
            "url": "https://kiro.dev/changelog/cli/3-0/",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-11-18T21:45:56.851915259Z",
            "changedAt": "2026-11-13T18:22:14.649257258Z",
            "fingerprint": "041bbd4c87fa"
          },
          {
            "url": "https://kiro.dev/changelog/models/",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-11-18T21:45:58.798115459Z",
            "changedAt": "2026-11-16T20:25:15.43817777Z",
            "fingerprint": "aae81cd6bfc7"
          }
        ],
        "github": {
          "repo": "kirodotdev/kiro",
          "checkedAt": "2026-11-16T12:12:42.813903344Z",
          "stars": 4473,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-05T17:16:02Z",
          "openIssues": 1640,
          "openPRs": 4,
          "issuesOpened90d": 1568,
          "issuesClosed90d": 1549,
          "prsMerged90d": 4,
          "ci": {
            "branch": "main",
            "runs": 1,
            "success": 0,
            "failure": 1,
            "other": 0,
            "latest": "failure",
            "latestAt": "2026-03-23T17:52:28Z"
          },
          "replies": {
            "sampled": 4,
            "unanswered": 4
          }
        },
        "updatedAt": "2026-11-18T21:45:58.798115459Z"
      }
    },
    "edges": [
      {
        "by": 12,
        "category": "reliability",
        "leads": "kiro-cli",
        "name": "Reliability",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 45,
          "b": 57
        }
      },
      {
        "by": 11,
        "category": "ergonomics",
        "leads": "friday-work",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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.",
          "b": "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)."
        },
        "scores": {
          "a": 78,
          "b": 67
        }
      },
      {
        "by": 8,
        "category": "security",
        "leads": "kiro-cli",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 61,
          "b": 69
        }
      }
    ],
    "facts": [
      {
        "a": "Agent harness",
        "b": "Agent harness",
        "name": "Kind"
      },
      {
        "a": "Friday Work",
        "b": "Amazon Web Services",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "stdio",
        "b": "",
        "name": "Transports"
      },
      {
        "a": "None",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Free",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "MIT",
        "b": "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",
        "name": "Licence"
      },
      {
        "a": "8",
        "b": "none",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "com.tryfridaywork/friday-work",
        "b": "not listed",
        "name": "MCP registry"
      },
      {
        "a": "2026-11-17",
        "b": "2026-11-03",
        "name": "Last release"
      },
      {
        "a": "2026-11-01",
        "b": "2026-08-14",
        "name": "Terms last updated"
      },
      {
        "a": "2026-11-01",
        "b": "2026-05-18",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "81 stars",
        "b": "4.4k stars",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "2.8/5 (4)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "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 \u0026 auth.",
        "question": "Which is better for AI agents, Friday or Kiro CLI?"
      },
      {
        "answer": "Friday is open source (MIT). No open-source release is listed for Kiro CLI.",
        "question": "Are Friday and Kiro CLI open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Agent ergonomics, 78 against 67"
        ],
        "also": [
          "No key needed to call it",
          "Runs on your own machine",
          "Open source",
          "No incidents deducted, where Kiro CLI loses 5 points for them"
        ],
        "goodFor": "A person who already runs several coding CLIs and wants an outside agent to hand work to them and wait on the result.",
        "slug": "friday-work",
        "watchFor": "Version 0.3.3, three weeks old, built by one developer, and Friday Work is not yet incorporated per its terms"
      },
      {
        "aheadOn": [
          "Reliability, 57 against 45",
          "Security \u0026 auth, 69 against 61"
        ],
        "also": [
          "Free to start without a card"
        ],
        "goodFor": "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.",
        "slug": "kiro-cli",
        "watchFor": "Free and individual paid accounts have content used for service improvement, including model training, unless they opt out"
      }
    ],
    "history": {
      "friday-work": [
        {
          "causes": [
            "terms"
          ],
          "date": "2026-11-18",
          "delta": 0,
          "from": 65.3,
          "fromGrade": "B",
          "to": 65.3,
          "toGrade": "B"
        }
      ],
      "kiro-cli": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 59.8,
          "fromGrade": "C",
          "to": 62.3,
          "toGrade": "B"
        },
        {
          "causes": [
            "security"
          ],
          "date": "2026-11-03",
          "delta": -1,
          "from": 60.8,
          "fromGrade": "C",
          "to": 59.8,
          "toGrade": "C"
        },
        {
          "causes": [
            "evidence"
          ],
          "date": "2026-10-28",
          "delta": 0.1,
          "from": 60.7,
          "fromGrade": "C",
          "to": 60.8,
          "toGrade": "C"
        }
      ]
    },
    "job": {
      "capability": "agent.multi-agent",
      "name": "Multi-agent orchestration"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/agent-zero-vs-friday-work.json",
        "title": "Agent Zero vs Friday",
        "url": "https://www.anchorterminal.com/compare/agent-zero-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.json",
        "title": "Agent Zero vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aider-vs-friday-work.json",
        "title": "Aider vs Friday",
        "url": "https://www.anchorterminal.com/compare/aider-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aider-vs-kiro-cli.json",
        "title": "Aider vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/aider-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amp-vs-friday-work.json",
        "title": "Amp vs Friday",
        "url": "https://www.anchorterminal.com/compare/amp-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amp-vs-kiro-cli.json",
        "title": "Amp vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/amp-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-friday-work.json",
        "title": "Antigravity CLI vs Friday",
        "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-cli.json",
        "title": "Antigravity CLI vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auggie-vs-friday-work.json",
        "title": "Auggie CLI vs Friday",
        "url": "https://www.anchorterminal.com/compare/auggie-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/auggie-vs-kiro-cli.json",
        "title": "Auggie CLI vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/auggie-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/axlr-vs-friday-work.json",
        "title": "AXLR vs Friday",
        "url": "https://www.anchorterminal.com/compare/axlr-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/axlr-vs-kiro-cli.json",
        "title": "AXLR vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/axlr-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/boxes-dev-vs-friday-work.json",
        "title": "boxes.dev vs Friday",
        "url": "https://www.anchorterminal.com/compare/boxes-dev-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/boxes-dev-vs-kiro-cli.json",
        "title": "boxes.dev vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/boxes-dev-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/claude-code-vs-friday-work.json",
        "title": "Claude Code vs Friday",
        "url": "https://www.anchorterminal.com/compare/claude-code-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/claude-code-vs-kiro-cli.json",
        "title": "Claude Code vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/claude-code-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/click-agents-vs-friday-work.json",
        "title": "Click vs Friday",
        "url": "https://www.anchorterminal.com/compare/click-agents-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/click-agents-vs-kiro-cli.json",
        "title": "Click vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/click-agents-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cline-vs-friday-work.json",
        "title": "Cline vs Friday",
        "url": "https://www.anchorterminal.com/compare/cline-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cline-vs-kiro-cli.json",
        "title": "Cline vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/cline-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/conductor-vs-friday-work.json",
        "title": "Conductor vs Friday",
        "url": "https://www.anchorterminal.com/compare/conductor-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/conductor-vs-kiro-cli.json",
        "title": "Conductor vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/conductor-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crush-vs-friday-work.json",
        "title": "Crush vs Friday",
        "url": "https://www.anchorterminal.com/compare/crush-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crush-vs-kiro-cli.json",
        "title": "Crush vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/crush-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cursor-cli-vs-friday-work.json",
        "title": "Cursor CLI vs Friday",
        "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cursor-cli-vs-kiro-cli.json",
        "title": "Cursor CLI vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepseek-harness-vs-friday-work.json",
        "title": "DeepSeek Harness (dsh) vs Friday",
        "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepseek-harness-vs-kiro-cli.json",
        "title": "DeepSeek Harness (dsh) vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-friday-work.json",
        "title": "dsh-superagent (DeepSeek) vs Friday",
        "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.json",
        "title": "dsh-superagent (DeepSeek) vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/devin-vs-friday-work.json",
        "title": "Devin vs Friday",
        "url": "https://www.anchorterminal.com/compare/devin-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/devin-vs-kiro-cli.json",
        "title": "Devin vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/devin-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/droid-cli-vs-friday-work.json",
        "title": "Droid CLI vs Friday",
        "url": "https://www.anchorterminal.com/compare/droid-cli-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli.json",
        "title": "Droid CLI vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/earendil-pi-vs-friday-work.json",
        "title": "Pi vs Friday",
        "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli.json",
        "title": "Pi vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/emdash-vs-friday-work.json",
        "title": "Emdash vs Friday",
        "url": "https://www.anchorterminal.com/compare/emdash-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/emdash-vs-kiro-cli.json",
        "title": "Emdash vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/emdash-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-harness2.json",
        "title": "Friday vs Harness²",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-harness2"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-mini-swe-agent.json",
        "title": "Friday vs mini-swe-agent",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-mini-swe-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-openai-agents-api.json",
        "title": "Friday vs OpenAI Agents API",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-openai-agents-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-openai-codex.json",
        "title": "Friday vs OpenAI Codex",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-openai-codex"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gemini-cli-vs-kiro-cli.json",
        "title": "Gemini CLI vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/gemini-cli-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-kiro-cli.json",
        "title": "GitHub Copilot CLI vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/goose-vs-kiro-cli.json",
        "title": "goose vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/goose-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/harness2-vs-kiro-cli.json",
        "title": "Harness² vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/harness2-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli.json",
        "title": "HarnessRouter vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/jules-vs-kiro-cli.json",
        "title": "Jules vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/jules-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/junie-vs-kiro-cli.json",
        "title": "Junie CLI vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/junie-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-cli.json",
        "title": "Kilo Code CLI vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli.json",
        "title": "Kimi Code CLI vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-letta.json",
        "title": "Kiro CLI vs Letta",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-letta"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-mini-swe-agent.json",
        "title": "Kiro CLI vs mini-swe-agent",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-mini-swe-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-minimax-code.json",
        "title": "Kiro CLI vs MiniMax Code",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-minimax-code"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli.json",
        "title": "Kiro CLI vs Mistral Vibe CLI",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code.json",
        "title": "Kiro CLI vs Muse Code",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api.json",
        "title": "Kiro CLI vs OpenAI Agents API",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex.json",
        "title": "Kiro CLI vs OpenAI Codex",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-opencode.json",
        "title": "Kiro CLI vs OpenCode",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-opencode"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openhands.json",
        "title": "Kiro CLI vs OpenHands",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openhands"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openmausbot.json",
        "title": "Kiro CLI vs OpenMausBot",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openmausbot"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-orca.json",
        "title": "Kiro CLI vs Orca",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-orca"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-paseo.json",
        "title": "Kiro CLI vs Paseo",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-paseo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent.json",
        "title": "Kiro CLI vs Prime Agent",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli.json",
        "title": "Kiro CLI vs Qoder CLI",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code.json",
        "title": "Kiro CLI vs Qwen Code",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror.json",
        "title": "Kiro CLI vs Mirror CLI",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli.json",
        "title": "Kiro CLI vs Rovo Dev CLI",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-sculptor.json",
        "title": "Kiro CLI vs Sculptor",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-sculptor"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code.json",
        "title": "Kiro CLI vs T3 Code",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-traycer.json",
        "title": "Kiro CLI vs Traycer",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-traycer"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable.json",
        "title": "Kiro CLI vs Unstoppable",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-verdent.json",
        "title": "Kiro CLI vs Verdent",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-verdent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading.json",
        "title": "Kiro CLI vs Vibe-Trading",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-warp.json",
        "title": "Kiro CLI vs Warp (Warp Agent CLI and the Oz Agent API)",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-warp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agent-relay-vs-friday-work.json",
        "title": "Agent Relay vs Friday",
        "url": "https://www.anchorterminal.com/compare/agent-relay-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agent-relay-vs-kiro-cli.json",
        "title": "Agent Relay vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/agent-relay-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clawboo-vs-friday-work.json",
        "title": "Clawboo vs Friday",
        "url": "https://www.anchorterminal.com/compare/clawboo-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.json",
        "title": "Clawboo vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cli-manager-vs-friday-work.json",
        "title": "CLI Manager vs Friday",
        "url": "https://www.anchorterminal.com/compare/cli-manager-vs-friday-work"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cli-manager-vs-kiro-cli.json",
        "title": "CLI Manager vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/cli-manager-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-gemini-cli.json",
        "title": "Friday vs Gemini CLI",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-gemini-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-github-copilot-cli.json",
        "title": "Friday vs GitHub Copilot CLI",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-github-copilot-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-goose.json",
        "title": "Friday vs goose",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-goose"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-harness-autonomous.json",
        "title": "Friday vs Harness",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-harness-autonomous"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-harnessrouter.json",
        "title": "Friday vs HarnessRouter",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-harnessrouter"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-herdr.json",
        "title": "Friday vs herdr",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-herdr"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-jules.json",
        "title": "Friday vs Jules",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-jules"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-junie.json",
        "title": "Friday vs Junie CLI",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-junie"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-kilo-code-cli.json",
        "title": "Friday vs Kilo Code CLI",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-kilo-code-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-kimi-code-cli.json",
        "title": "Friday vs Kimi Code CLI",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-kimi-code-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-letta.json",
        "title": "Friday vs Letta",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-letta"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-minimax-code.json",
        "title": "Friday vs MiniMax Code",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-minimax-code"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-mistral-vibe-cli.json",
        "title": "Friday vs Mistral Vibe CLI",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-mistral-vibe-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-muse-code.json",
        "title": "Friday vs Muse Code",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-muse-code"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-opencode.json",
        "title": "Friday vs OpenCode",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-opencode"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-openhands.json",
        "title": "Friday vs OpenHands",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-openhands"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-openmausbot.json",
        "title": "Friday vs OpenMausBot",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-openmausbot"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-orca.json",
        "title": "Friday vs Orca",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-orca"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-paperclip.json",
        "title": "Friday vs Paperclip",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-paperclip"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-parallax-agents.json",
        "title": "Friday vs Parallax",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-parallax-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-paseo.json",
        "title": "Friday vs Paseo",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-paseo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-prime-agent.json",
        "title": "Friday vs Prime Agent",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-prime-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-qoder-cli.json",
        "title": "Friday vs Qoder CLI",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-qoder-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-qwen-code.json",
        "title": "Friday vs Qwen Code",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-qwen-code"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-reflection-mirror.json",
        "title": "Friday vs Mirror CLI",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-reflection-mirror"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-rovo-dev-cli.json",
        "title": "Friday vs Rovo Dev CLI",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-rovo-dev-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-sculptor.json",
        "title": "Friday vs Sculptor",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-sculptor"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-t3-code.json",
        "title": "Friday vs T3 Code",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-t3-code"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-traycer.json",
        "title": "Friday vs Traycer",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-traycer"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-unstoppable.json",
        "title": "Friday vs Unstoppable",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-unstoppable"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-verdent.json",
        "title": "Friday vs Verdent",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-verdent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-vibe-trading.json",
        "title": "Friday vs Vibe-Trading",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-vibe-trading"
      },
      {
        "json": "https://www.anchorterminal.com/compare/friday-work-vs-warp.json",
        "title": "Friday vs Warp (Warp Agent CLI and the Oz Agent API)",
        "url": "https://www.anchorterminal.com/compare/friday-work-vs-warp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/harness-autonomous-vs-kiro-cli.json",
        "title": "Harness vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/harness-autonomous-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/herdr-vs-kiro-cli.json",
        "title": "herdr vs Kiro CLI",
        "url": "https://www.anchorterminal.com/compare/herdr-vs-kiro-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-paperclip.json",
        "title": "Kiro CLI vs Paperclip",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-paperclip"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-parallax-agents.json",
        "title": "Kiro CLI vs Parallax",
        "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-parallax-agents"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 12,
        "edge": "kiro-cli",
        "friday-work": 45,
        "key": "reliability",
        "kiro-cli": 57,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 3,
        "edge": "friday-work",
        "friday-work": 82,
        "key": "schema",
        "kiro-cli": 79,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 11,
        "edge": "friday-work",
        "friday-work": 78,
        "key": "ergonomics",
        "kiro-cli": 67,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 8,
        "edge": "kiro-cli",
        "friday-work": 61,
        "key": "security",
        "kiro-cli": 69,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 0,
        "edge": "",
        "friday-work": 60,
        "key": "payments",
        "kiro-cli": 60,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 3,
        "edge": "kiro-cli",
        "friday-work": 70,
        "key": "maintenance",
        "kiro-cli": 73,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 3,
        "edge": "kiro-cli",
        "friday-work": 68,
        "key": "transparency",
        "kiro-cli": 71,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "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 \u0026 auth. Both do multi-agent orchestration.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "friday-work": "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/friday-work-vs-kiro-cli",
    "json": "https://www.anchorterminal.com/compare/friday-work-vs-kiro-cli.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/friday-work-vs-kiro-cli.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/friday-work-vs-kiro-cli.min.md"
  },
  "markdown": "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 \u0026 auth. Both do multi-agent orchestration.\n\n- Friday: grade B, 65.3/100, rank #544 of 1557. Markdown https://www.anchorterminal.com/tools/friday-work.md · JSON https://www.anchorterminal.com/api/v1/tools/friday-work.json\n- Kiro CLI: grade B, 62.3/100, rank #686 of 1557. Markdown https://www.anchorterminal.com/tools/kiro-cli.md · JSON https://www.anchorterminal.com/api/v1/tools/kiro-cli.json\n- Best agent harnesses and coding agents: https://www.anchorterminal.com/best/agent-harnesses/index.md\n- All 1767 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md\n\n## Which one, for what\n\n### Friday (B)\n\nGood for: A person who already runs several coding CLIs and wants an outside agent to hand work to them and wait on the result.\n\nAhead on:\n- Agent ergonomics, 78 against 67\n\nAlso in its favour:\n- No key needed to call it\n- Runs on your own machine\n- Open source\n- No incidents deducted, where Kiro CLI loses 5 points for them\n\nWatch for: Version 0.3.3, three weeks old, built by one developer, and Friday Work is not yet incorporated per its terms\n\n### Kiro CLI (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 57 against 45\n- Security \u0026 auth, 69 against 61\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Free and individual paid accounts have content used for service improvement, including model training, unless they opt out\n\n\n## Why the edge\n\n### Reliability: Kiro CLI +12\n\n- 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.\n- 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.\n\n### Agent ergonomics: Friday +11\n\n- 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.\n- 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).\n\n### Security \u0026 auth: Kiro CLI +8\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | Friday | Kiro CLI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 45 | 57 | Kiro CLI +12 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 82 | 79 | Friday +3 |\n| Agent ergonomics | 13% | 78 | 67 | Friday +11 |\n| Security \u0026 auth | 14% | 61 | 69 | Kiro CLI +8 |\n| Payments \u0026 pricing | 10% | 60 | 60 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 70 | 73 | Kiro CLI +3 |\n| Transparency \u0026 trust | 7% | 68 | 71 | Kiro CLI +3 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **65.3 · B** | **62.3 · B** | |\n\n## Facts side by side\n\n| Fact | Friday | Kiro CLI |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | Friday Work | Amazon Web Services |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio |  |\n| Auth | None | OAuth or key |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| 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 |\n| Tools exposed | 8 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `com.tryfridaywork/friday-work` | not listed |\n| Last release | 2026-11-17 | 2026-11-03 |\n| Terms last updated | 2026-11-01 | 2026-08-14 |\n| Privacy policy last updated | 2026-11-01 | 2026-05-18 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 81 stars | 4.4k stars |\n| Agent reviews | none | 2.8/5 (4) |\n\n## How the scores have moved\n\n### Friday\n\n- no change on 18 November 2026: terms\n\n### Kiro CLI\n\n- +2.5 on 13 November 2026 (C to B): checklist\n- -1.0 on 3 November 2026: security\n- +0.1 on 28 October 2026: new evidence\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Friday\n\n1. Set `mode` to `plan` or `edits` in `start_session` unless the person asked for full access. The default is `full`\n2. Leave `answer` with `approve: true` to the person unless they told you to approve requests for them\n3. If `wait_for_idle` times out, call it again rather than starting a new session\n4. If a call says Friday isn't running, ask the person to open Friday, then retry\n5. Page `read_session` with `after` set to the last `next_after` instead of reading the whole history each time\n\n### Kiro CLI\n\n1. Set `KIRO_API_KEY` and pass `--no-interactive` with `--trust-tools=\u003clist\u003e` in pipelines. Keep `--trust-all-tools` for disposable environments\n2. Pass `--require-mcp-startup` when a run depends on MCP tools. Without it a failed server is logged and the run continues\n3. 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\n4. Run `kiro-cli settings telemetry.enabled false` and turn off content collection on Free and individual plans. Both are on by default\n5. Remove `autocomplete`, `inline`, `translate`, `theme` and `dashboard` from scripts, which 3.0.0 retired. Pass `--v2` to keep the V2 agent\n\n## Questions\n\n### Which is better for AI agents, Friday or Kiro CLI?\n\nFriday 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 \u0026 auth.\n\n### Are Friday and Kiro CLI open source?\n\nFriday is open source (MIT). No open-source release is listed for Kiro CLI.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/friday-work-vs-kiro-cli.json, and with the fewest tokens: https://www.anchorterminal.com/compare/friday-work-vs-kiro-cli.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"friday-work\", \"b\": \"kiro-cli\"}`. From a terminal: `anchor compare friday-work kiro-cli`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/friday-work.json and https://www.anchorterminal.com/api/v1/tools/kiro-cli.json\n\n## Other comparisons with Friday or Kiro CLI\n\n- [Agent Zero vs Friday](https://www.anchorterminal.com/compare/agent-zero-vs-friday-work.md)\n- [Agent Zero vs Kiro CLI](https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.md)\n- [Aider vs Friday](https://www.anchorterminal.com/compare/aider-vs-friday-work.md)\n- [Aider vs Kiro CLI](https://www.anchorterminal.com/compare/aider-vs-kiro-cli.md)\n- [Amp vs Friday](https://www.anchorterminal.com/compare/amp-vs-friday-work.md)\n- [Amp vs Kiro CLI](https://www.anchorterminal.com/compare/amp-vs-kiro-cli.md)\n- [Antigravity CLI vs Friday](https://www.anchorterminal.com/compare/antigravity-cli-vs-friday-work.md)\n- [Antigravity CLI vs Kiro CLI](https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-cli.md)\n- [Auggie CLI vs Friday](https://www.anchorterminal.com/compare/auggie-vs-friday-work.md)\n- [Auggie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/auggie-vs-kiro-cli.md)\n- [AXLR vs Friday](https://www.anchorterminal.com/compare/axlr-vs-friday-work.md)\n- [AXLR vs Kiro CLI](https://www.anchorterminal.com/compare/axlr-vs-kiro-cli.md)\n- [boxes.dev vs Friday](https://www.anchorterminal.com/compare/boxes-dev-vs-friday-work.md)\n- [boxes.dev vs Kiro CLI](https://www.anchorterminal.com/compare/boxes-dev-vs-kiro-cli.md)\n- [Claude Code vs Friday](https://www.anchorterminal.com/compare/claude-code-vs-friday-work.md)\n- [Claude Code vs Kiro CLI](https://www.anchorterminal.com/compare/claude-code-vs-kiro-cli.md)\n- [Click vs Friday](https://www.anchorterminal.com/compare/click-agents-vs-friday-work.md)\n- [Click vs Kiro CLI](https://www.anchorterminal.com/compare/click-agents-vs-kiro-cli.md)\n- [Cline vs Friday](https://www.anchorterminal.com/compare/cline-vs-friday-work.md)\n- [Cline vs Kiro CLI](https://www.anchorterminal.com/compare/cline-vs-kiro-cli.md)\n- [Conductor vs Friday](https://www.anchorterminal.com/compare/conductor-vs-friday-work.md)\n- [Conductor vs Kiro CLI](https://www.anchorterminal.com/compare/conductor-vs-kiro-cli.md)\n- [Crush vs Friday](https://www.anchorterminal.com/compare/crush-vs-friday-work.md)\n- [Crush vs Kiro CLI](https://www.anchorterminal.com/compare/crush-vs-kiro-cli.md)\n- [Cursor CLI vs Friday](https://www.anchorterminal.com/compare/cursor-cli-vs-friday-work.md)\n- [Cursor CLI vs Kiro CLI](https://www.anchorterminal.com/compare/cursor-cli-vs-kiro-cli.md)\n- [DeepSeek Harness (dsh) vs Friday](https://www.anchorterminal.com/compare/deepseek-harness-vs-friday-work.md)\n- [DeepSeek Harness (dsh) vs Kiro CLI](https://www.anchorterminal.com/compare/deepseek-harness-vs-kiro-cli.md)\n- [dsh-superagent (DeepSeek) vs Friday](https://www.anchorterminal.com/compare/deepseek-superagent-vs-friday-work.md)\n- [dsh-superagent (DeepSeek) vs Kiro CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.md)\n- [Devin vs Friday](https://www.anchorterminal.com/compare/devin-vs-friday-work.md)\n- [Devin vs Kiro CLI](https://www.anchorterminal.com/compare/devin-vs-kiro-cli.md)\n- [Droid CLI vs Friday](https://www.anchorterminal.com/compare/droid-cli-vs-friday-work.md)\n- [Droid CLI vs Kiro CLI](https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli.md)\n- [Pi vs Friday](https://www.anchorterminal.com/compare/earendil-pi-vs-friday-work.md)\n- [Pi vs Kiro CLI](https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli.md)\n- [Emdash vs Friday](https://www.anchorterminal.com/compare/emdash-vs-friday-work.md)\n- [Emdash vs Kiro CLI](https://www.anchorterminal.com/compare/emdash-vs-kiro-cli.md)\n- [Friday vs Harness²](https://www.anchorterminal.com/compare/friday-work-vs-harness2.md)\n- [Friday vs mini-swe-agent](https://www.anchorterminal.com/compare/friday-work-vs-mini-swe-agent.md)\n- [Friday vs OpenAI Agents API](https://www.anchorterminal.com/compare/friday-work-vs-openai-agents-api.md)\n- [Friday vs OpenAI Codex](https://www.anchorterminal.com/compare/friday-work-vs-openai-codex.md)\n- [Gemini CLI vs Kiro CLI](https://www.anchorterminal.com/compare/gemini-cli-vs-kiro-cli.md)\n- [GitHub Copilot CLI vs Kiro CLI](https://www.anchorterminal.com/compare/github-copilot-cli-vs-kiro-cli.md)\n- [goose vs Kiro CLI](https://www.anchorterminal.com/compare/goose-vs-kiro-cli.md)\n- [Harness² vs Kiro CLI](https://www.anchorterminal.com/compare/harness2-vs-kiro-cli.md)\n- [HarnessRouter vs Kiro CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli.md)\n- [Jules vs Kiro CLI](https://www.anchorterminal.com/compare/jules-vs-kiro-cli.md)\n- [Junie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/junie-vs-kiro-cli.md)\n- [Kilo Code CLI vs Kiro CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-cli.md)\n- [Kimi Code CLI vs Kiro CLI](https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli.md)\n- [Kiro CLI vs Letta](https://www.anchorterminal.com/compare/kiro-cli-vs-letta.md)\n- [Kiro CLI vs mini-swe-agent](https://www.anchorterminal.com/compare/kiro-cli-vs-mini-swe-agent.md)\n- [Kiro CLI vs MiniMax Code](https://www.anchorterminal.com/compare/kiro-cli-vs-minimax-code.md)\n- [Kiro CLI vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli.md)\n- [Kiro CLI vs Muse Code](https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code.md)\n- [Kiro CLI vs OpenAI Agents API](https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api.md)\n- [Kiro CLI vs OpenAI Codex](https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex.md)\n- [Kiro CLI vs OpenCode](https://www.anchorterminal.com/compare/kiro-cli-vs-opencode.md)\n- [Kiro CLI vs OpenHands](https://www.anchorterminal.com/compare/kiro-cli-vs-openhands.md)\n- [Kiro CLI vs OpenMausBot](https://www.anchorterminal.com/compare/kiro-cli-vs-openmausbot.md)\n- [Kiro CLI vs Orca](https://www.anchorterminal.com/compare/kiro-cli-vs-orca.md)\n- [Kiro CLI vs Paseo](https://www.anchorterminal.com/compare/kiro-cli-vs-paseo.md)\n- [Kiro CLI vs Prime Agent](https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent.md)\n- [Kiro CLI vs Qoder CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli.md)\n- [Kiro CLI vs Qwen Code](https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code.md)\n- [Kiro CLI vs Mirror CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror.md)\n- [Kiro CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli.md)\n- [Kiro CLI vs Sculptor](https://www.anchorterminal.com/compare/kiro-cli-vs-sculptor.md)\n- [Kiro CLI vs T3 Code](https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code.md)\n- [Kiro CLI vs Traycer](https://www.anchorterminal.com/compare/kiro-cli-vs-traycer.md)\n- [Kiro CLI vs Unstoppable](https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable.md)\n- [Kiro CLI vs Verdent](https://www.anchorterminal.com/compare/kiro-cli-vs-verdent.md)\n- [Kiro CLI vs Vibe-Trading](https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading.md)\n- [Kiro CLI vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/kiro-cli-vs-warp.md)\n- [Agent Relay vs Friday](https://www.anchorterminal.com/compare/agent-relay-vs-friday-work.md)\n- [Agent Relay vs Kiro CLI](https://www.anchorterminal.com/compare/agent-relay-vs-kiro-cli.md)\n- [Clawboo vs Friday](https://www.anchorterminal.com/compare/clawboo-vs-friday-work.md)\n- [Clawboo vs Kiro CLI](https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.md)\n- [CLI Manager vs Friday](https://www.anchorterminal.com/compare/cli-manager-vs-friday-work.md)\n- [CLI Manager vs Kiro CLI](https://www.anchorterminal.com/compare/cli-manager-vs-kiro-cli.md)\n- [Friday vs Gemini CLI](https://www.anchorterminal.com/compare/friday-work-vs-gemini-cli.md)\n- [Friday vs GitHub Copilot CLI](https://www.anchorterminal.com/compare/friday-work-vs-github-copilot-cli.md)\n- [Friday vs goose](https://www.anchorterminal.com/compare/friday-work-vs-goose.md)\n- [Friday vs Harness](https://www.anchorterminal.com/compare/friday-work-vs-harness-autonomous.md)\n- [Friday vs HarnessRouter](https://www.anchorterminal.com/compare/friday-work-vs-harnessrouter.md)\n- [Friday vs herdr](https://www.anchorterminal.com/compare/friday-work-vs-herdr.md)\n- [Friday vs Jules](https://www.anchorterminal.com/compare/friday-work-vs-jules.md)\n- [Friday vs Junie CLI](https://www.anchorterminal.com/compare/friday-work-vs-junie.md)\n- [Friday vs Kilo Code CLI](https://www.anchorterminal.com/compare/friday-work-vs-kilo-code-cli.md)\n- [Friday vs Kimi Code CLI](https://www.anchorterminal.com/compare/friday-work-vs-kimi-code-cli.md)\n- [Friday vs Letta](https://www.anchorterminal.com/compare/friday-work-vs-letta.md)\n- [Friday vs MiniMax Code](https://www.anchorterminal.com/compare/friday-work-vs-minimax-code.md)\n- [Friday vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/friday-work-vs-mistral-vibe-cli.md)\n- [Friday vs Muse Code](https://www.anchorterminal.com/compare/friday-work-vs-muse-code.md)\n- [Friday vs OpenCode](https://www.anchorterminal.com/compare/friday-work-vs-opencode.md)\n- [Friday vs OpenHands](https://www.anchorterminal.com/compare/friday-work-vs-openhands.md)\n- [Friday vs OpenMausBot](https://www.anchorterminal.com/compare/friday-work-vs-openmausbot.md)\n- [Friday vs Orca](https://www.anchorterminal.com/compare/friday-work-vs-orca.md)\n- [Friday vs Paperclip](https://www.anchorterminal.com/compare/friday-work-vs-paperclip.md)\n- [Friday vs Parallax](https://www.anchorterminal.com/compare/friday-work-vs-parallax-agents.md)\n- [Friday vs Paseo](https://www.anchorterminal.com/compare/friday-work-vs-paseo.md)\n- [Friday vs Prime Agent](https://www.anchorterminal.com/compare/friday-work-vs-prime-agent.md)\n- [Friday vs Qoder CLI](https://www.anchorterminal.com/compare/friday-work-vs-qoder-cli.md)\n- [Friday vs Qwen Code](https://www.anchorterminal.com/compare/friday-work-vs-qwen-code.md)\n- [Friday vs Mirror CLI](https://www.anchorterminal.com/compare/friday-work-vs-reflection-mirror.md)\n- [Friday vs Rovo Dev CLI](https://www.anchorterminal.com/compare/friday-work-vs-rovo-dev-cli.md)\n- [Friday vs Sculptor](https://www.anchorterminal.com/compare/friday-work-vs-sculptor.md)\n- [Friday vs T3 Code](https://www.anchorterminal.com/compare/friday-work-vs-t3-code.md)\n- [Friday vs Traycer](https://www.anchorterminal.com/compare/friday-work-vs-traycer.md)\n- [Friday vs Unstoppable](https://www.anchorterminal.com/compare/friday-work-vs-unstoppable.md)\n- [Friday vs Verdent](https://www.anchorterminal.com/compare/friday-work-vs-verdent.md)\n- [Friday vs Vibe-Trading](https://www.anchorterminal.com/compare/friday-work-vs-vibe-trading.md)\n- [Friday vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/friday-work-vs-warp.md)\n- [Harness vs Kiro CLI](https://www.anchorterminal.com/compare/harness-autonomous-vs-kiro-cli.md)\n- [herdr vs Kiro CLI](https://www.anchorterminal.com/compare/herdr-vs-kiro-cli.md)\n- [Kiro CLI vs Paperclip](https://www.anchorterminal.com/compare/kiro-cli-vs-paperclip.md)\n- [Kiro CLI vs Parallax](https://www.anchorterminal.com/compare/kiro-cli-vs-parallax-agents.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Friday vs Kiro CLI",
        "url": ""
      }
    ],
    "description": "Friday scores 65.3 (B) to Kiro CLI's 62.3 (B) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Friday B 65.3",
      "Kiro CLI B 62.3",
      "scores"
    ],
    "h1": "Friday vs Kiro CLI",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/friday-work-vs-kiro-cli",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Friday vs Kiro CLI for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/friday-work-vs-kiro-cli"
  },
  "tokens": {
    "markdown": 6100,
    "slim": 830
  },
  "version": 1
}
