# Friday vs T3 Code (slim)

> Friday scores 65.3 (B) to T3 Code's 55.7 (C) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/friday-work-vs-t3-code.md (~5,800 tokens) · this version ~880 tokens · JSON https://www.anchorterminal.com/compare/friday-work-vs-t3-code.json · canonical https://www.anchorterminal.com/compare/friday-work-vs-t3-code
- 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 scores 65.3 (B) on agent readiness against T3 Code's 55.7 (C), and leads in 5 of 7 scored categories. T3 Code leads on payments & pricing and maintenance & community. Both do multi-agent orchestration.

- Friday: B 65.3, rank #544 of 1557 · https://www.anchorterminal.com/tools/friday-work.min.md
- T3 Code: C 55.7, rank #974 of 1557 · https://www.anchorterminal.com/tools/t3-code.min.md
- 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 Schema & documentation, 82 against 55; Agent ergonomics, 78 against 60; Security & auth, 61 against 35; Transparency & trust, 68 against 51. Also Runs on your own machine.
- T3 Code, good for Developers who want one app, including on their phone, to drive several coding agents they already pay for. Ahead on Payments & pricing, 90 against 60; Maintenance & community, 75 against 70.

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

| Fact (where they differ) | Friday | T3 Code |
| --- | --- | --- |
| Vendor | Friday Work | T3 Tools Inc. |
| Transports | stdio |  |
| Tools exposed | 8 | none |
| llms.txt | yes | no |
| MCP registry | `com.tryfridaywork/friday-work` | not listed |
| Last release | 2026-11-17 | 2026-11-06 |
| Terms last updated | 2026-11-01 | no document linked |
| Privacy policy last updated | 2026-11-01 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 81 stars | none |

Why the edge:
- Payments & pricing, T3 Code +30: Friday 60 (Scored on the hosted option, as for Orca.); T3 Code 90 (Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60. Re-scored on…)
- Schema & documentation, Friday +27: Friday 82 (Read on the outside-agent MCP server.); T3 Code 55 (Harness reading.)
- Security & auth, Friday +26: Friday 61 (Harness reading, as for herdr.); T3 Code 35 (Harness reading.)
- Agent ergonomics, Friday +18: Friday 78 (Eight compact tools (25).); T3 Code 60 (Harness reading.)
- Transparency & trust, Friday +17: Friday 68 (MIT (30).); T3 Code 51 (MIT (30).)
- Maintenance & community, T3 Code +5: Friday 70 (v0.3.3 on 17 November 2026, one day before the check (30).); T3 Code 75 (Commits and nightly tags on 6 November 2026 (30).)
