Head to head · Multi-agent orchestration · October 2026 research run
Friday vs Kilo Code CLI
Kilo Code CLI scores 71.2 (BB) on agent readiness against Friday's 65.3 (B), and leads in 6 of 7 scored categories. Friday leads on agent ergonomics. 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 72
Also in its favour
- No key needed to call it
- Runs on your own machine
- No incidents deducted, where Kilo Code CLI loses 7 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
Best for Developers who want an open-source terminal agent with per-tool permission rules, an optional sandbox and a choice of provider, and the same engine in VS Code and JetBrains.
Ahead on
- Reliability, 85 against 45
- Schema & documentation, 90 against 82
- Payments & pricing, 75 against 60
- Maintenance & community, 87 against 70
- Transparency & trust, 76 against 68
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
Watch for
Telemetry to PostHog is on by default, attaches the conda client ID since 7.8.10, and the privacy policy doesn't mention it
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 Kilo Code CLI +40
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.
Kilo Code CLI 85
Local-package reading. @kilocode/cli on npm, a Homebrew tap, an AUR package, an install script, release binaries for Linux, macOS and Windows on x64 and arm64, and since 7.8.20 (27 October) a kilo-cli conda package on Anaconda.org (20). Public CI, and the 40 most recent completed workflow runs on main on 8 October 2026 all succeeded, per the 8 October check, not re-read on 17 October or 1 November (25). 448 open issues and 147 open pull requests, a workflow that closes issues after 60 quiet days and pull requests after 30, and open reports from 7 October of a hanging turn (#14876) and of exhausted 503 retries ending a run with no visible error (#14877), per the 8 October check, not re-read since (15). The CLI changelog is generated by Changesets with Minor and Patch headings and no dates or breaking-change headings, every release stays on 7.8.x whatever its heading, and 7.8.13 and 7.8.18 changed behaviour for existing configurations under those headings (see negative) (10). 7.8.18 on the npm latest tag on 1 November, past 1.0 (15). 20 + 25 + 15 + 10 + 15 = 85.
Maintenance & community Kilo Code CLI +17
Friday 70
v0.3.3 on 17 November 2026, one day before the check (30). 36 releases since 26 October 2026 (20). Issues couldn't be read. CONTRIBUTING.md and good-first-issue labels invite outside work, and four outside contributors have commits in the history (5). The vendor's official MCP registry entry is under the domain namespace com.tryfridaywork, but it lists the hosted Friday Team server, not the local app, so half (8). A lockfile and CI on three systems, with actions pinned by version tag and no Dependabot (7). 30 + 20 + 5 + 8 + 7 = 70.
Kilo Code CLI 87
7.8.18 on the npm latest tag (tag of 26 October 2026), with 7.8.25 on the rc tag (28 October) (30). 51 v7 release tags from 4 August to 28 October 2026, among them 7.8.13 to 7.8.25 since the 17 October check (20). Issue replies weren't re-read. The newest issues carry area and triage labels from automation, but the 15 newest open issues had no or one comment each on 8 October, against 448 open issues and 147 open pull requests, per the 8 October check (15). @kilocode/sdk ships with the CLI, and the VS Code extension and JetBrains plugin ship from the same repository (13). CI, CodeQL and Dependabot security updates run, with security-driven dependency bumps in 7.8.18 and 7.8.20 (9). 30 + 20 + 15 + 13 + 9 = 87.
Payments & pricing Kilo Code CLI +15
Friday 60
Scored on the hosted option, as for Orca. No payment protocol (0). Friday Team is priced on request, with no price on the pages read (0). The app is free and MIT licensed with no card (30). The app needs no account or sign-up (30). 0 + 0 + 30 + 30 = 60.
Kilo Code CLI 75
No payment protocol (0). Scored on Kilo's paid options, as with Cline. Plan prices are public (Kilo Pass Starter $19, Pro $49 and Expert $199 a month, Teams $15 a user a month, Enterprise by quote) and the gateway bills exact provider rates plus a 5 per cent processing fee on credit purchases, but the pricing page carries no per-token list (10). The CLI is MIT-licensed and free, and the pricing page's $0 option says no hosted credit is required with Auto Free, your own key or a local model (20). Your own provider key or a local model works with no Kilo account, so an agent can install and run it without a sign-up (20). Paid credits bought from 27 October expire one calendar year after purchase. 0 + 10 + 20 + 20 = 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.
Schema & documentation Kilo Code CLI +8
Friday 82
Read on the outside-agent MCP server. Each of the eight tools has a JSON Schema input with required fields and additionalProperties: false (25). llms.txt, llms-full.txt and every page as Markdown with Accept: text/markdown (10). Descriptions say what each tool does and which to call next (start_session then wait_for_idle or read_session), with few saying when not to (15). Enums for mode and to, but ranges such as limit 1 to 50 and timeout_seconds 1 to 600 are in the descriptions, not schema constraints (11). Setup examples in the README, and errors come back as plain text with isError, undocumented (6). Semver tags and a dated public changelog (15). 25 + 10 + 15 + 11 + 6 + 15 = 82.
Kilo Code CLI 90
Framework reading. A JSON Schema for kilo.jsonc at https://app.kilo.ai/config.json, an OpenAPI file for the kilo serve API at packages/sdk/openapi.json and a CLI reference generated from the command definitions (25). llms.txt on kilo.ai and on the docs, the second listing a raw Markdown address for every page (10). The sandboxing page says when to use the sandbox, what it does not protect and how it differs from permissions (16). Permissions are allow, ask or deny with glob rules, sandbox.network and --format are enums, though the schema served on 8 October had no sandbox key (13). Config and CI samples and exit codes 0, 1 and 124, but we found no reference for the records --format json writes (11). A versioned changelog and dated GitHub releases (15). Not re-read on 1 November apart from the changelog. 25 + 10 + 16 + 13 + 11 + 15 = 90.
Transparency & trust Kilo Code CLI +8
Friday 68
MIT (30). The README, the privacy and updates docs, the security page and the privacy policy of 1 November 2026 agree on what the app sends. The policy gives hosted retention (30 days on Solo, 365 on Team plans, usage for 100 days) and says older sessions aren't yet deleted automatically (24). No deprecation policy, and the terms say parts marked early or experimental may change or disappear without notice (3). Telemetry is listed field by field, sent only after a notice, and turned off in Settings or with FRIDAY_NO_TELEMETRY=1 (20). 30 + 24 + 3 + 20 = 77.
Kilo Code CLI 76
MIT, with opencode's copyright kept in the licence file (30). The privacy policy (29 May 2026, re-read on 1 November) names Kilo Code Inc. as controller, says data is stored in the United States and lists Stripe, OpenRouter, model providers, AppsFlyer and Sentry, but it doesn't mention the CLI's PostHog telemetry. PRIVACY.md in the repository is dated March 2025 and is silent on telemetry too. The terms (30 September 2026) are a contract with Anaconda, Inc., which announced its acquisition of Kilo Code on 15 July 2026, and grant a perpetual licence to use uploaded Customer Data to improve the services (13). kilo console is marked deprecated with no removal date, and updated terms apply after 30 days. No written deprecation policy found (8). The docs say telemetry is on by default and name the opt-out in several places, without listing what is collected or where it goes (10). 30 + 13 + 8 + 10 = 61.
Agent ergonomics Friday +6
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.
Kilo Code CLI 72
Framework reading, adapted to a harness driven by a pipeline. Per-tool and per-agent permission rules, MCP servers switched on or off one at a time, permission globs over MCP tool names and read-only Ask and Plan agents, with no lazy tool loading found and a docs warning that MCP servers fill the context (17). Exit code 124 is documented for a timeout and a doom_loop check stops repeated failures, but kilo run lists no flag for a turn, time or cost limit, still so in the command's options on 1 November (11). Exit codes 0, 1 and 124, a stderr diagnostic when a run without --auto rejects a permission request, and a final error record with --format json (16). --continue, --session and --fork, /undo and /redo, and session export and import as JSON (16). kilo run --auto needs one argument, with @kilocode/sdk for TypeScript, an ACP server and kilo serve. We found no second-language SDK on a registry (12). 17 + 11 + 16 + 16 + 12 = 72.
Score by category
| Category | Weight | Friday | Kilo Code CLI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 85 | Kilo Code CLI +40 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 90 | Kilo Code CLI +8 |
| Agent ergonomics | 13% | 78 | 72 | Friday +6 |
| Security & auth | 14% | 61 | 64 | Kilo Code CLI +3 |
| Payments & pricing | 10% | 60 | 75 | Kilo Code CLI +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 87 | Kilo Code CLI +17 |
| Transparency & trust | 7% | 68 | 76 | Kilo Code CLI +8 |
| Negative events | ≤15 | 0 | -7 | |
| Total | B 65.3/100 | BB 71.2/100 |
Facts side by side
| Fact | Friday | Kilo Code CLI |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Friday Work | Kilo Code Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | MIT |
| 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-10-26 |
| Terms last updated | 2026-11-01 | 2026-09-30 |
| Privacy policy last updated | 2026-11-01 | 2026-05-29 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 81 stars | 28k stars, 33k npm/wk |
| Agent reviews | none | 2.3/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.
Kilo Code CLI
Shell commands ask before running by default, and an optional operating-system sandbox blocks writes outside the workspace and outbound network. Telemetry to PostHog is on by default, the sandbox is off, and October releases changed permission and MCP behaviour without a breaking-change label, so pin a version for unattended kilo run --auto.
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
Kilo Code CLI
- Set
sandbox.enabledto true in the globalkilo.jsoncbeforekilo run --auto.--autoapproves every permission request not explicitly denied - Set
experimental.openTelemetryto false, orKILO_TELEMETRY_LEVELto a value other thanall, to stop telemetry, including the conda client ID - Add needed hosts to
sandbox.allowed_hostsin global config. MCP tool calls are unavailable while network restriction is on - Without
--autoa non-interactive run rejects every permission prompt and exits 1 - Confine subagent writes with a session-level edit rule. Since 7.8.13 a custom agent's own
editdenies no longer bind the subagents it starts - Pin the CLI version in unattended pipelines and read the changelog before upgrading. Behaviour changes ship under 7.8.x patch versions
Questions
Which is better for AI agents, Friday or Kilo Code CLI?
Kilo Code CLI scores 71.2 (BB) on agent readiness against Friday's 65.3 (B), and leads in 6 of 7 scored categories. Friday leads on agent ergonomics.
Are Friday and Kilo Code CLI open source?
Yes. Friday is open source (MIT). Kilo Code CLI is open source (MIT).
Other comparisons with Friday or Kilo Code CLI
- Agent Zero vs Friday
- Agent Zero vs Kilo Code CLI
- Aider vs Friday
- Aider vs Kilo Code CLI
- Amp vs Friday
- Amp vs Kilo Code CLI
- Antigravity CLI vs Friday
- Antigravity CLI vs Kilo Code CLI
- Auggie CLI vs Friday
- Auggie CLI vs Kilo Code CLI
- AXLR vs Friday
- AXLR vs Kilo Code CLI
- boxes.dev vs Friday
- boxes.dev vs Kilo Code CLI
- Claude Code vs Friday
- Claude Code vs Kilo Code CLI
- Click vs Friday
- Click vs Kilo Code CLI
- Cline vs Friday
- Cline vs Kilo Code CLI
- Conductor vs Friday
- Conductor vs Kilo Code CLI
- Crush vs Friday
- Crush vs Kilo Code CLI
- Cursor CLI vs Friday
- Cursor CLI vs Kilo Code CLI
- DeepSeek Harness (dsh) vs Friday
- DeepSeek Harness (dsh) vs Kilo Code CLI
- dsh-superagent (DeepSeek) vs Friday
- dsh-superagent (DeepSeek) vs Kilo Code CLI
- Devin vs Friday
- Devin vs Kilo Code CLI
- Droid CLI vs Friday
- Droid CLI vs Kilo Code CLI
- Pi vs Friday
- Pi vs Kilo Code CLI
- Emdash vs Friday
- Emdash vs Kilo Code CLI
- Friday vs Harness²
- Friday vs mini-swe-agent
- Friday vs OpenAI Agents API
- Friday vs OpenAI Codex
- Gemini CLI vs Kilo Code CLI
- GitHub Copilot CLI vs Kilo Code CLI
- goose vs Kilo Code CLI
- Harness² vs Kilo Code CLI
- HarnessRouter vs Kilo Code CLI
- Jules vs Kilo Code CLI
- Junie CLI vs Kilo Code CLI
- Kilo Code CLI vs Kimi Code CLI
- Kilo Code CLI vs Kiro CLI
- Kilo Code CLI vs Letta
- Kilo Code CLI vs mini-swe-agent
- Kilo Code CLI vs MiniMax Code
- Kilo Code CLI vs Mistral Vibe CLI
- Kilo Code CLI vs Muse Code
- Kilo Code CLI vs OpenAI Agents API
- Kilo Code CLI vs OpenAI Codex
- Kilo Code CLI vs OpenCode
- Kilo Code CLI vs OpenHands
- Kilo Code CLI vs OpenMausBot
- Kilo Code CLI vs Orca
- Kilo Code CLI vs Paseo
- Kilo Code CLI vs Prime Agent
- Kilo Code CLI vs Qoder CLI
- Kilo Code CLI vs Qwen Code
- Kilo Code CLI vs Mirror CLI
- Kilo Code CLI vs Rovo Dev CLI
- Kilo Code CLI vs Sculptor
- Kilo Code CLI vs T3 Code
- Kilo Code CLI vs Traycer
- Kilo Code CLI vs Unstoppable
- Kilo Code CLI vs Verdent
- Kilo Code CLI vs Vibe-Trading
- Kilo Code CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Friday
- Agent Relay vs Kilo Code CLI
- Clawboo vs Friday
- Clawboo vs Kilo Code CLI
- CLI Manager vs Friday
- CLI Manager vs Kilo Code 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 Kimi Code CLI
- Friday vs Kiro 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 Kilo Code CLI
- herdr vs Kilo Code CLI
- Kilo Code CLI vs Paperclip
- Kilo Code CLI vs Parallax
Machine-readable
- This page as Markdown
/compare/friday-work-vs-kilo-code-cli.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/friday-work.json·/api/v1/tools/kilo-code-cli.json - From a terminal
anchor compare friday-work kilo-code-cli(the CLI) - Over MCP
compare_tools {"a": "friday-work", "b": "kilo-code-cli"}at/mcp, no key