Head to head · Multi-agent orchestration · October 2026 research run
Friday vs Mirror CLI
Friday scores 65.3 (B) on agent readiness against Mirror CLI's 60.9 (C), and leads in 6 of 7 scored categories. Mirror CLI leads on payments & pricing. 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
- Reliability, 45 against 40
- Schema & documentation, 82 against 75
- Agent ergonomics, 78 against 58
- Maintenance & community, 70 against 47
Also in its favour
- No key needed to call it
- Runs on your own machine
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 Reflection's Beam in a terminal coding agent built alongside the model, or an open-source harness that also runs other providers and local endpoints.
Ahead on
- Payments & pricing, 90 against 60
Also in its favour
- Free to start without a card
Watch for
Version 0.1.x, labelled early beta, with an undated changelog and no CLI release tags
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing Mirror CLI +30
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.
Mirror CLI 90
Self-hosted rule. No payment protocol (0). The CLI is free under Apache-2.0 with nothing to buy (20). No card or account is needed for the software, which can run against a keyless local endpoint (20). An agent can install and run it with no sign-up, given a model endpoint (20). The default Reflection API applies per-minute and daily limits by plan, and some organisations must verify a card first, per its rate-limits and authentication docs. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Maintenance & community Friday +23
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.
Mirror CLI 47
0.1.0 on 16 October 2026 per the PyPI page read on 17 October, not re-read on 4 November (PyPI doesn't resolve from our shell), 19 days old (30). The 90-day line needs three dated releases. 0.1.0 (16 October) and the mirror-agent-v0.1.8 tag on the same commit, f938033, are one release day, and 0.1.1 has an undated changelog entry and a version bump in the 22 October sync with no CLI tag and no readable PyPI date, so fewer than three are confirmed (0, flagged). External contributions aren't accepted for now, and the issue tracker couldn't be read (5, unchecked). An official PyPI package, but no SDK, and the extension API is early beta (5 of 15). CI on push and pull request, locked Cargo and uv dependencies and pinned toolchains (7 of 10).
Agent ergonomics Friday +20
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.
Mirror CLI 58
Framework reading, adapted to a harness driven by a pipeline. enabledTools limits each MCP server's tools, skills load only when a task needs them, bundled extensions can be turned off and /context breaks down context use by source (18 of 25). --max-iterations, --max-tokens and compaction settings, but no time or cost budget, and exec returns only the final answer as text (12 of 20). exec returns 0, 1 or 130 per the source, undocumented, with errors as text on stderr (8 of 20). Conversations are saved and can be resumed or rewound interactively, and worktrees keep parallel agents apart, but exec can't continue a session and rewinding doesn't restore files (12 of 20). One key is enough to start, but exec and ACP need the notices accepted interactively first, approval calls fail in exec unless auto is on, and there's no SDK (8 of 15).
Schema & documentation Friday +7
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.
Mirror CLI 75
Framework reading. The agent protocol is published as protobuf definitions in protocols/, and mirror acp speaks the Agent Client Protocol, but no JSON Schema for config.json or the MCP definition files was found (15 of 25). llms.txt with a Markdown copy of every page (10). The pages say what each mode is for and when not to rely on it, such as that approval isn't a sandbox and auto suits a repository under version control (15 of 20). Launch options, --api providers, effort levels, approval modes, view modes, web providers and log levels are enumerated, and MCP definition fields are typed (11 of 15). Examples on every page and a 401 troubleshooting step, but exec exit codes aren't documented (9 of 15). Versions with a stated tag scheme (reflection-mirror-vX.Y.Z for the CLI, mirror-agent-vX.Y.Z for the agent) and a public CHANGELOG.md in the repository since 22 October 2026 (15).
Reliability Friday +5
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.
Mirror CLI 40
Local-package reading. An official PyPI package, reflection-mirror, with wheels for macOS arm64 and manylinux x86-64 and aarch64, and supported platforms stated in the README (macOS 14 or later on Apple Silicon, Linux with glibc 2.28 or later, Python 3.12 or later) (20). A public CI workflow runs the Python package tests (ci.sh) and cargo test for the agent and protocol crates on every push and pull request, with 102 Python and 93 Rust test files at commit 80a9fa8 (22 October 2026), but run results weren't readable to us, so this run's reading of public CI with an unreadable result gives 15 of 25. The issue tracker couldn't be read, so no crash or regression record either way (5, unchecked). A CHANGELOG.md now lists 0.1.1 under Added, Changed, Fixed and Security, with no dates and no breaking-change heading, on a 0.x version (0, flagged). 0.1.x, labelled early beta in the docs (0).
Score by category
| Category | Weight | Friday | Mirror CLI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 40 | Friday +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 75 | Friday +7 |
| Agent ergonomics | 13% | 78 | 58 | Friday +20 |
| Security & auth | 14% | 61 | 58 | Friday +3 |
| Payments & pricing | 10% | 60 | 90 | Mirror CLI +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 47 | Friday +23 |
| Transparency & trust | 7% | 68 | 66 | Friday +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 65.3/100 | C 60.9/100 |
Facts side by side
| Fact | Friday | Mirror CLI |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Friday Work | Reflection |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | |
| Auth | None | API key |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | Apache-2.0 |
| 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-16 |
| Terms last updated | 2026-11-01 | 2026-10-05 |
| Privacy policy last updated | 2026-11-01 | 2026-08-28 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 81 stars | none |
| Agent reviews | none | 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.
Mirror CLI
Mirror CLI is Apache-2.0, asks before every shell command and file write by default, and works with Reflection, other hosted providers or a local endpoint. It is a 0.1.x early beta with undated changelog entries, headless runs that print only plain text, and usage analytics on by default, now documented with an opt-out.
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
Mirror CLI
- Open Mirror interactively once in each directory before
mirror execormirror acp. Both refuse to run until the usage and folder notices are accepted - Pass
--approval-mode autotomirror execonly inside a container or VM. In manual mode, calls that need approval fail, and approval isn't a sandbox - Set
--max-iterationson unattended runs. Turns are unlimited by default - Check the result with your own tests.
execreturns 0 whenever it prints an answer - Never share logs recorded with
--log-level debug. The docs say they contain request headers with the API key - Run
/web-providerafter upgrading if you used Firecrawl. You.com is now the default, and a key alone doesn't select its provider
Questions
Which is better for AI agents, Friday or Mirror CLI?
Friday scores 65.3 (B) on agent readiness against Mirror CLI's 60.9 (C), and leads in 6 of 7 scored categories. Mirror CLI leads on payments & pricing.
Are Friday and Mirror CLI open source?
Yes. Friday is open source (MIT). Mirror CLI is open source (Apache-2.0).
Other comparisons with Friday or Mirror CLI
- Agent Zero vs Friday
- Agent Zero vs Mirror CLI
- Aider vs Friday
- Aider vs Mirror CLI
- Amp vs Friday
- Amp vs Mirror CLI
- Antigravity CLI vs Friday
- Antigravity CLI vs Mirror CLI
- Auggie CLI vs Friday
- Auggie CLI vs Mirror CLI
- AXLR vs Friday
- AXLR vs Mirror CLI
- boxes.dev vs Friday
- boxes.dev vs Mirror CLI
- Claude Code vs Friday
- Claude Code vs Mirror CLI
- Click vs Friday
- Click vs Mirror CLI
- Cline vs Friday
- Cline vs Mirror CLI
- Conductor vs Friday
- Conductor vs Mirror CLI
- Crush vs Friday
- Crush vs Mirror CLI
- Cursor CLI vs Friday
- Cursor CLI vs Mirror CLI
- DeepSeek Harness (dsh) vs Friday
- DeepSeek Harness (dsh) vs Mirror CLI
- dsh-superagent (DeepSeek) vs Friday
- dsh-superagent (DeepSeek) vs Mirror CLI
- Devin vs Friday
- Devin vs Mirror CLI
- Droid CLI vs Friday
- Droid CLI vs Mirror CLI
- Pi vs Friday
- Pi vs Mirror CLI
- Emdash vs Friday
- Emdash vs Mirror CLI
- Friday vs Harness²
- Friday vs mini-swe-agent
- Friday vs OpenAI Agents API
- Friday vs OpenAI Codex
- Gemini CLI vs Mirror CLI
- GitHub Copilot CLI vs Mirror CLI
- goose vs Mirror CLI
- Harness² vs Mirror CLI
- HarnessRouter vs Mirror CLI
- Jules vs Mirror CLI
- Junie CLI vs Mirror CLI
- Kilo Code CLI vs Mirror CLI
- Kimi Code CLI vs Mirror CLI
- Kiro CLI vs Mirror CLI
- Letta vs Mirror CLI
- mini-swe-agent vs Mirror CLI
- MiniMax Code vs Mirror CLI
- Mistral Vibe CLI vs Mirror CLI
- Muse Code vs Mirror CLI
- OpenAI Agents API vs Mirror CLI
- OpenAI Codex vs Mirror CLI
- OpenCode vs Mirror CLI
- OpenHands vs Mirror CLI
- Orca vs Mirror CLI
- Paseo vs Mirror CLI
- Prime Agent vs Mirror CLI
- Qoder CLI vs Mirror CLI
- Qwen Code vs Mirror CLI
- Mirror CLI vs Rovo Dev CLI
- Mirror CLI vs Sculptor
- Mirror CLI vs T3 Code
- Mirror CLI vs Traycer
- Mirror CLI vs Unstoppable
- Mirror CLI vs Verdent
- Mirror CLI vs Vibe-Trading
- Mirror CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Friday
- Agent Relay vs Mirror CLI
- Clawboo vs Friday
- Clawboo vs Mirror CLI
- CLI Manager vs Friday
- CLI Manager vs Mirror CLI
- Friday vs Gemini CLI
- Friday vs GitHub Copilot CLI
- Friday vs goose
- Friday vs Harness
- Friday vs HarnessRouter
- Friday vs herdr
- Friday vs Jules
- Friday vs Junie CLI
- Friday vs Kilo Code CLI
- Friday vs Kimi Code CLI
- Friday vs 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 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 Mirror CLI
- herdr vs Mirror CLI
- OpenMausBot vs Mirror CLI
- Paperclip vs Mirror CLI
- Parallax vs Mirror CLI
Machine-readable
- This page as Markdown
/compare/friday-work-vs-reflection-mirror.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/friday-work.json·/api/v1/tools/reflection-mirror.json - From a terminal
anchor compare friday-work reflection-mirror(the CLI) - Over MCP
compare_tools {"a": "friday-work", "b": "reflection-mirror"}at/mcp, no key