Head to head · Multi-agent orchestration · October 2026 research run
Clawboo vs Friday
Friday and Clawboo score within a point of each other on agent readiness, 65.3 (B) and 65.1 (B). Clawboo leads on reliability, security & auth and payments & pricing. Both do multi-agent orchestration.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Clawboo B
Best for One person on one computer who wants several coding and general agents on one board, with shared memory and a lead agent that routes work.
Ahead on
- Reliability, 52 against 45
- Security & auth, 70 against 61
- Payments & pricing, 90 against 60
Also in its favour
- Free to start without a card
Watch for
Claude Code runs in bypassPermissions, Codex with danger-full-access and Hermes with --yolo, with no setting to change it and no sandbox
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
- Maintenance & community, 70 against 51
- Transparency & trust, 68 against 58
Also in its favour
- Runs on your own machine
- No incidents deducted, where Clawboo loses 4 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
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 Clawboo +30
Clawboo 90
No payment protocol (0). Read with the self-hosted rule. Free under MIT with nothing to buy (20). No card and no Clawboo account (20). One npx command installs and starts it with no sign-up (20). Model costs belong to the providers the owner connects. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
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.
Maintenance & community Friday +19
Clawboo 51
0.5.0 was published to npm on 21 October 2026 (30). Two releases in the 90 days to 1 November 2026, 0.4.0 on 28 September and 0.5.0, below the three the line asks for (0). github.com was unreachable, so replies to issues, pull requests and Discussions are unchecked. The CI file cites issue #140 as fixed (3). One public npm package, current, with no entry in the official MCP registry for its four servers (10). CI, CodeQL, weekly Dependabot and SLSA provenance on 0.4.0 and 0.5.0, with @composio/client pinned to an alpha (8).
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.
Transparency & trust Friday +10
Clawboo 58
MIT, Copyright 2026 Sanreds, with a third-party notices file (30). The docs list every file Clawboo writes, which copies of keys are encrypted and which are plain text, retention for stored tool results (7 days) and pending approvals (24 hours), and that prompts go only to connected providers. There is no privacy statement, and the website wasn't read (22). The 0.1.x line is deprecated on npm with a note in the changelog, and removals are dated in release notes, with no written deprecation policy or notice period (10). No telemetry, with the server's own outbound requests disclosed, though the npm update check has no setting (18).
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.
Security & auth Clawboo +9
Clawboo 70
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. The docs say Clawboo sends no telemetry and list the GitHub catalogue fetch, the npm version check, OpenRouter's public model list, Google Fonts and the GitHub star count, of which only the catalogue address can be changed (27). Clawboo Native shell commands are off by default and asked one at a time, and connector grants are per agent with approval on writes. Claude Code, Codex and Hermes run with their prompts and sandboxes off and no setting to change it, they can read Clawboo's database and key vault, and with no access token by default any local program can answer approval cards (8). Images in agent text don't load on their own, peer posts are marked as evidence, and a run that has read private data and untrusted content asks before any outbound connector call (11). An audit log of budget, breaker, approval, verification, tool-call and install events, with secrets masked (13). SECURITY.md with private reporting, CodeQL, Dependabot and npm provenance. No security.txt or bug bounty, OSV lists no advisory for clawboo, and the proxy advisory is on the docs with a workaround while its fix is unreleased (11).
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.
Reliability Clawboo +7
Clawboo 52
Read as local software. The official npm package clawboo states Node.js 22.12 or newer, and the README says macOS, Linux and Windows are supported (20). ci.yml runs lint, typecheck, Vitest and a real-concurrency suite on Linux and platform suites on Windows and macOS, and publish.yml reruns build, lint, typecheck, tests and a clean-install boot before it publishes. 0.5.0 carries provenance from that workflow on main, so its checks passed at that commit, but run results on main couldn't be read (15). github.com was unreachable, so open crash and regression issues are unchecked. A known-issues page lists 25 entries with a status each, three of them fixed on main (5). Changesets write a changelog entry per release, and removals and the 0.2.0 database reset are called out, though breaking changes arrive in minor versions before 1.0 (12). Version 0.5.0, and SECURITY.md says pre-1.0 (0).
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.
Score by category
| Category | Weight | Clawboo | Friday | Edge |
|---|---|---|---|---|
| Reliability | 16% | 52 | 45 | Clawboo +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 83 | 82 | Clawboo +1 |
| Agent ergonomics | 13% | 75 | 78 | Friday +3 |
| Security & auth | 14% | 70 | 61 | Clawboo +9 |
| Payments & pricing | 10% | 90 | 60 | Clawboo +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 51 | 70 | Friday +19 |
| Transparency & trust | 7% | 58 | 68 | Friday +10 |
| Negative events | ≤15 | -4 | 0 | |
| Total | B 65.1/100 | B 65.3/100 |
Facts side by side
| Fact | Clawboo | Friday |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Sanreds | Friday Work |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | |
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | MIT |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.tryfridaywork/friday-work |
| Last release | 2026-10-21 | 2026-11-17 |
| Terms last updated | no document linked | 2026-11-01 |
| Privacy policy last updated | no document linked | 2026-11-01 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 100 npm/wk | 81 stars |
How the scores have moved
Verdicts
Clawboo
Tasks, memory, team chat and connectors are shared across five runtimes through four MCP servers, with documentation that states each default and limit. Claude Code, Codex and Hermes run with their sandboxes and approval prompts off and no setting to change it, and a reverse-proxy exposure of the MCP servers is fixed only on the unreleased main branch.
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.
Before you call either
Clawboo
- Run
npx clawboo@latest, not a barenpx clawboo, which can reuse an older cached build. Node.js 22.12 or newer is required - On 0.5.0 behind nginx, Caddy or a Cloudflare Tunnel, deny
/api/mcp/at the proxy and setSTUDIO_ACCESS_TOKENfromopenssl rand -hex 24 - Give Claude Code, Codex and Hermes teammates only work you would let run unattended, or run Clawboo under a separate user account or VM
- Create a hard-cap budget in Settings > Insights > Governance before long runs. A fresh install has no budget and new budgets only warn
- Install
@anthropic-ai/claude-agent-sdkglobally beside Clawboo for Claude Code teammates. A one-offnpxrun cannot load it
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
Questions
Which is better for AI agents, Clawboo or Friday?
Friday and Clawboo score within a point of each other on agent readiness, 65.3 (B) and 65.1 (B). Clawboo leads on reliability, security & auth and payments & pricing.
Are Clawboo and Friday open source?
Yes. Clawboo is open source (MIT). Friday is open source (MIT).
Other comparisons with Clawboo or Friday
- Agent Zero vs Friday
- Aider vs Friday
- Amp vs Friday
- Antigravity CLI vs Friday
- Auggie CLI vs Friday
- AXLR vs Friday
- boxes.dev vs Friday
- Claude Code vs Friday
- Click vs Friday
- Cline vs Friday
- Conductor vs Friday
- Crush vs Friday
- Cursor CLI vs Friday
- DeepSeek Harness (dsh) vs Friday
- dsh-superagent (DeepSeek) vs Friday
- Devin vs Friday
- Droid CLI vs Friday
- Pi vs Friday
- Emdash vs Friday
- Friday vs Harness²
- Friday vs mini-swe-agent
- Friday vs OpenAI Agents API
- Friday vs OpenAI Codex
- Agent Relay vs Clawboo
- Agent Relay vs Friday
- Amp vs Clawboo
- Antigravity CLI vs Clawboo
- Auggie CLI vs Clawboo
- AXLR vs Clawboo
- boxes.dev vs Clawboo
- Claude Code vs Clawboo
- Clawboo vs CLI Manager
- Clawboo vs Cline
- Clawboo vs Conductor
- Clawboo vs Crush
- Clawboo vs DeepSeek Harness (dsh)
- Clawboo vs dsh-superagent (DeepSeek)
- Clawboo vs Devin
- Clawboo vs Droid CLI
- Clawboo vs Emdash
- Clawboo vs Gemini CLI
- Clawboo vs GitHub Copilot CLI
- Clawboo vs goose
- Clawboo vs Harness
- Clawboo vs HarnessRouter
- Clawboo vs herdr
- Clawboo vs Jules
- Clawboo vs Junie CLI
- Clawboo vs Kilo Code CLI
- Clawboo vs Kimi Code CLI
- Clawboo vs Kiro CLI
- Clawboo vs Letta
- Clawboo vs MiniMax Code
- Clawboo vs Mistral Vibe CLI
- Clawboo vs Muse Code
- Clawboo vs OpenCode
- Clawboo vs OpenHands
- Clawboo vs OpenMausBot
- Clawboo vs Orca
- Clawboo vs Paperclip
- Clawboo vs Parallax
- Clawboo vs Paseo
- Clawboo vs Prime Agent
- Clawboo vs Qoder CLI
- Clawboo vs Qwen Code
- Clawboo vs Mirror CLI
- Clawboo vs Rovo Dev CLI
- Clawboo vs Sculptor
- Clawboo vs T3 Code
- Clawboo vs Traycer
- Clawboo vs Unstoppable
- Clawboo vs Verdent
- Clawboo vs Vibe-Trading
- Clawboo vs Warp (Warp Agent CLI and the Oz Agent API)
- CLI Manager vs Friday
- 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 Unstoppable
- Friday vs Verdent
- Friday vs Vibe-Trading
- Friday vs Warp (Warp Agent CLI and the Oz Agent API)
Machine-readable
- This page as Markdown
/compare/clawboo-vs-friday-work.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clawboo.json·/api/v1/tools/friday-work.json - From a terminal
anchor compare clawboo friday-work(the CLI) - Over MCP
compare_tools {"a": "clawboo", "b": "friday-work"}at/mcp, no key