# Clawboo vs Friday (slim)

> Friday and Clawboo score within a point of each other for multi-agent orchestration, 65.3 and 65.1 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/clawboo-vs-friday-work.md (~6,050 tokens) · this version ~830 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-friday-work.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-friday-work
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Clawboo: B 65.1, rank #549 of 1557 · https://www.anchorterminal.com/tools/clawboo.min.md
- Friday: B 65.3, rank #544 of 1557 · https://www.anchorterminal.com/tools/friday-work.min.md
- Clawboo, good 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 Free to start without a card.
- Friday, good 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 Runs on your own machine; No incidents deducted, where Clawboo loses 4 points for them.

| Category | Clawboo | Friday |
| --- | --- | --- |
| Reliability (16%) | 52 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 82 |
| Agent ergonomics (13%) | 75 | 78 |
| Security & auth (14%) | 70 | 61 |
| Payments & pricing (10%) | 90 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 51 | 70 |
| Transparency & trust (7%) | 58 | 68 |

| Fact (where they differ) | Clawboo | Friday |
| --- | --- | --- |
| Vendor | Sanreds | Friday Work |
| Transports |  | stdio |
| Tools exposed | none | 8 |
| 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 |

Why the edge:
- Payments & pricing, Clawboo +30: Clawboo 90 (No payment protocol (0).); Friday 60 (Scored on the hosted option, as for Orca.)
- Maintenance & community, Friday +19: Clawboo 51 (0.5.0 was published to npm on 21 October 2026 (30).); Friday 70 (v0.3.3 on 17 November 2026, one day before the check (30).)
- Transparency & trust, Friday +10: Clawboo 58 (MIT, Copyright 2026 Sanreds, with a third-party notices file (30).); Friday 68 (MIT (30).)
- Security & auth, Clawboo +9: Clawboo 70 (Harness reading of the framework checklist, as for the other harnesses.); Friday 61 (Harness reading, as for herdr.)
- Reliability, Clawboo +7: Clawboo 52 (Read as local software.); Friday 45 (Read as local software, as for herdr and Orca.)
