Head to head · Multi-agent orchestration · October 2026 research run
Friday vs Unstoppable
Friday scores 65.3 (B) on agent readiness against Unstoppable's 38.4 (E), and leads in 6 of 7 scored categories. 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
- Schema & documentation, 82 against 30
- Agent ergonomics, 78 against 5
- Security & auth, 61 against 41
- Payments & pricing, 60 against 45
- Maintenance & community, 70 against 58
Also in its favour
- 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 A developer who runs Claude Code, Codex and Cursor on existing plans and wants parallel worktrees, pipelines and phone check-ins in one app.
Also in its favour
- Free to start without a card
Watch for
No API, MCP server, SDK or documented CLI for an outside agent. A Linux command-line tool is offered for download with no documentation, and MCP tools for cloud tasks appear only in changelog lines
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.
Agent ergonomics Friday +73
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.
Unstoppable 5
These lines measure an interface an agent calls, and Unstoppable has none, so context cost, output controls and retries score nothing. For the person, a usage limit shows choices to wait for the reset or continue on credits (2 of 20). Guest use with no account, a first-run page that imports Claude and Codex projects, and few required settings. No SDK (3 of 15). Total 5.
Schema & documentation Friday +52
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.
Unstoppable 30
Graded on the interface an outside agent can use, which is none. No API, OpenAPI file, MCP server or documented command (0). unstoppable.ai/llms.txt lists the product, help and policy pages in Markdown (10). Twenty-two dated help articles explain for a person what each part does and when to use it, such as Code and Work modes and approval modes (5 of 20). No typed inputs an agent could call (0). Step-by-step examples for people and named error states such as usage limit reached and update failed, with no error responses for an agent (3 of 15). Numbered versions and a public dated changelog, which lists only four releases from 20 to 23 October 2026 (12 of 15). Total 30.
Security & auth Friday +20
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.
Unstoppable 41
Harness reading of the framework checklist, as for the other harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Activity sharing is Off for every activity type by default and secrets are removed before upload. The repository's HOSTED-SERVICES.md now lists every telemetry flow with a switch in Settings, Privacy, Usage data, and the privacy policy names those switches, but all of them start on, PostHog session replays are recorded by default, LaunchDarkly gets the account and connected-provider emails by default and can only be switched to an anonymous context, and updates download automatically by default (15 of 30, unchanged, judgement call). Ask and Accept edits modes with allow and deny rules by command, file write, MCP tool and network host, deny winning, and safety rules that block force-pushes and destructive deletes. Every kind of chat starts in Full access, which skips prompts and safety rules, and local agents have no documented sandbox. Cloud worktrees get their own sandbox (8 of 20, per the 27 October check). The in-app browser stops agents acting on private sign-in pages. No other guidance on untrusted content from web pages, MCP servers or connected tools (3 of 15). Cost and usage panels, a team feed with tool-use metadata, approval rules with their origin, and an Audit Trail experiment in Labs (8 of 15, per the 27 October check). A SECURITY.md in the client repository sends reports to GitHub's private vulnerability reporting and states that fixes go into the latest release, with no acknowledgement time (7, was 2). No security.txt on unstoppable.ai per the 27 October check, the parent's expired, and no SOC 2 or ISO 27001 found. Total 41.
Payments & pricing Friday +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.
Unstoppable 45
No x402, MPP or L402 (0). The app is published as free, but AI credit prices appear only after sign-in, and no pricing page exists (unstoppable.ai/pricing redirects to the home page). Plan prices of $19, $29 and $49 appear only in an 11 August 2026 blog post (10). Guest use with no account, and 10 free AI credits a day with no card (20). A person has to download and install the app, so no autonomous onboarding (0). Total 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Maintenance & community Friday +12
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.
Unstoppable 58
Read for a closed product with a public source export. Desktop 1.19.0, tagged source-desktop/v1.19.0 on 5 November 2026 and offered on the download page (30). Desktop 1.12.0 to 1.15.0 from 20 to 23 October, source tags for 1.17.0 (3 November) and 1.19.0 (5 November), and iOS updates since 11 August 2026 (20). A public changelog, a support email, in-app feedback, a Discord server and, since 29 October, GitHub issues, none of which we could read for replies (6 of 15, held). No SDK and no MCP registry entry (0). The source carries a pnpm lock file and no CI beyond closing pull requests (2 of 10). Total 58.
Score by category
| Category | Weight | Friday | Unstoppable | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 45 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 30 | Friday +52 |
| Agent ergonomics | 13% | 78 | 5 | Friday +73 |
| Security & auth | 14% | 61 | 41 | Friday +20 |
| Payments & pricing | 10% | 60 | 45 | Friday +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 58 | Friday +12 |
| Transparency & trust | 7% | 68 | 67 | Friday +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 65.3/100 | E 38.4/100 |
Facts side by side
| Fact | Friday | Unstoppable |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Friday Work | Unstoppable Domains, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | |
| Auth | None | None |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | MIT for the desktop and mobile client source (github.com/unstoppableweb/unstoppable-code, from 29 October 2026). Hosted services stay closed under Unstoppable Domains, Inc.'s Terms of Service |
| Tools exposed | 8 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.tryfridaywork/friday-work | not listed |
| Last release | 2026-11-17 | 2026-11-05 |
| Terms last updated | 2026-11-01 | 2026-10-06 |
| Privacy policy last updated | 2026-11-01 | 2026-10-08 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| 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 |
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.
Unstoppable
Unstoppable runs several coding agents side by side in separate worktrees on the owner's Claude, ChatGPT or Cursor plans, and its desktop and mobile clients are MIT source with a documented telemetry list. It has no API, MCP server or documented command an outside agent can call, and every chat starts in Full access.
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
Unstoppable
- Don't plan to drive Unstoppable from another agent. It has no documented API, MCP server or CLI. Call Claude Code, Codex or Cursor directly and let the person use Unstoppable around them
- Inside Unstoppable, check the approval mode before acting. New chats start in Full access unless the person set Ask or Accept edits in Settings, Approvals
- When a Claude or Codex usage limit is reached, ask the person before choosing Use credits now or Always use credits, since both spend their AI credits
- Keep each task in its own worktree and let the person review the diff and press Create PR, rather than pushing to a shared branch
- If the person cares what leaves the machine, point them to Settings, Privacy, Usage data, where each telemetry flow starts on
Questions
Which is better for AI agents, Friday or Unstoppable?
Friday scores 65.3 (B) on agent readiness against Unstoppable's 38.4 (E), and leads in 6 of 7 scored categories.
Are Friday and Unstoppable open source?
Yes. Friday is open source (MIT). Unstoppable is open source (MIT for the desktop and mobile client source (github.com/unstoppableweb/unstoppable-code, from 29 October 2026). Hosted services stay closed under Unstoppable Domains, Inc.'s Terms of Service).
Other comparisons with Friday or Unstoppable
- Agent Zero vs Friday
- Agent Zero vs Unstoppable
- Aider vs Friday
- Aider vs Unstoppable
- Amp vs Friday
- Amp vs Unstoppable
- Antigravity CLI vs Friday
- Antigravity CLI vs Unstoppable
- Auggie CLI vs Friday
- Auggie CLI vs Unstoppable
- AXLR vs Friday
- AXLR vs Unstoppable
- boxes.dev vs Friday
- boxes.dev vs Unstoppable
- Claude Code vs Friday
- Claude Code vs Unstoppable
- Click vs Friday
- Click vs Unstoppable
- Cline vs Friday
- Cline vs Unstoppable
- Conductor vs Friday
- Conductor vs Unstoppable
- Crush vs Friday
- Crush vs Unstoppable
- Cursor CLI vs Friday
- Cursor CLI vs Unstoppable
- DeepSeek Harness (dsh) vs Friday
- DeepSeek Harness (dsh) vs Unstoppable
- dsh-superagent (DeepSeek) vs Friday
- dsh-superagent (DeepSeek) vs Unstoppable
- Devin vs Friday
- Devin vs Unstoppable
- Droid CLI vs Friday
- Droid CLI vs Unstoppable
- Pi vs Friday
- Pi vs Unstoppable
- Emdash vs Friday
- Emdash vs Unstoppable
- Friday vs Harness²
- Friday vs mini-swe-agent
- Friday vs OpenAI Agents API
- Friday vs OpenAI Codex
- Gemini CLI vs Unstoppable
- GitHub Copilot CLI vs Unstoppable
- goose vs Unstoppable
- Harness² vs Unstoppable
- HarnessRouter vs Unstoppable
- Jules vs Unstoppable
- Junie CLI vs Unstoppable
- Kilo Code CLI vs Unstoppable
- Kimi Code CLI vs Unstoppable
- Kiro CLI vs Unstoppable
- Letta vs Unstoppable
- mini-swe-agent vs Unstoppable
- MiniMax Code vs Unstoppable
- Mistral Vibe CLI vs Unstoppable
- Muse Code vs Unstoppable
- OpenAI Agents API vs Unstoppable
- OpenAI Codex vs Unstoppable
- OpenCode vs Unstoppable
- OpenHands vs Unstoppable
- Orca vs Unstoppable
- Paseo vs Unstoppable
- Prime Agent vs Unstoppable
- Qoder CLI vs Unstoppable
- Qwen Code vs Unstoppable
- Mirror CLI vs Unstoppable
- Rovo Dev CLI vs Unstoppable
- Sculptor vs Unstoppable
- T3 Code vs Unstoppable
- Traycer vs Unstoppable
- Agent Relay vs Friday
- Agent Relay vs Unstoppable
- Clawboo vs Friday
- Clawboo vs Unstoppable
- CLI Manager vs Friday
- CLI Manager vs Unstoppable
- 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 Mirror CLI
- Friday vs Rovo Dev CLI
- Friday vs Sculptor
- Friday vs T3 Code
- Friday vs Traycer
- Friday vs Verdent
- Friday vs Vibe-Trading
- Friday vs Warp (Warp Agent CLI and the Oz Agent API)
- Harness vs Unstoppable
- herdr vs Unstoppable
- OpenMausBot vs Unstoppable
- Paperclip vs Unstoppable
- Parallax vs Unstoppable
- Unstoppable vs Verdent
- Unstoppable vs Vibe-Trading
- Unstoppable vs Warp (Warp Agent CLI and the Oz Agent API)
Machine-readable
- This page as Markdown
/compare/friday-work-vs-unstoppable.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/friday-work.json·/api/v1/tools/unstoppable.json - From a terminal
anchor compare friday-work unstoppable(the CLI) - Over MCP
compare_tools {"a": "friday-work", "b": "unstoppable"}at/mcp, no key