Head to head · Multi-agent orchestration · October 2026 research run
Friday vs T3 Code
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.
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 55
- Agent ergonomics, 78 against 60
- Security & auth, 61 against 35
- Transparency & trust, 68 against 51
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
T3 Code C
Best 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
Watch for
Usage data on by default, with hashed OpenAI and Claude account identifiers, and relay traces to Axiom
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 T3 Code +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.
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 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Schema & documentation Friday +27
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.
T3 Code 55
Harness reading. User docs in the repository (managed policy, handoffs, providers, telemetry), AGENTS.md for contributors, a server other clients connect to (55).
Security & auth Friday +26
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.
T3 Code 35
Harness reading. Product usage events go by default to ingest.t3.codes and PostHog, with hashed identifiers for your T3 Connect, OpenAI and Claude accounts, and relay traces to Axiom, which can include machine names and error text. Off with T3CODE_TELEMETRY_ENABLED=false or a managed policy. Disclosed in docs/user/telemetry.md, not the README (10 of 30). Permission modes and managed policies (12 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 10 + 12 + 5 + 5 + 3 = 35.
Agent ergonomics Friday +18
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.
T3 Code 60
Harness reading. Remote control from phone or browser, portable handoffs between providers and managed policies for teams (60).
Transparency & trust Friday +17
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.
T3 Code 51
MIT (30). docs/user/telemetry.md lists what is sent and what isn't, but includes hashed third-party account identifiers and the README doesn't mention it (15 of 30). No deprecation policy (5). Disclosed with an opt-out, on by default (12 of 20). 30 + 15 + 5 + 12 = 62.
Maintenance & community T3 Code +5
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.
T3 Code 75
Commits and nightly tags on 6 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current official apps and install script (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.
Score by category
| Category | Weight | Friday | T3 Code | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 43 | Friday +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 55 | Friday +27 |
| Agent ergonomics | 13% | 78 | 60 | Friday +18 |
| Security & auth | 14% | 61 | 35 | Friday +26 |
| Payments & pricing | 10% | 60 | 90 | T3 Code +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 75 | T3 Code +5 |
| Transparency & trust | 7% | 68 | 51 | Friday +17 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 65.3/100 | C 55.7/100 |
Facts side by side
| Fact | Friday | T3 Code |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Friday Work | T3 Tools Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | |
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | MIT |
| Tools exposed | 8 | none |
| Read-only variant documented | no | no |
| 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 |
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.
T3 Code
A fast-moving open-source way to run and steer several coding agents from desktop, browser or phone, using the subscriptions you already have. It's pre-1.0, and it sends usage data by default, including hashed identifiers for your OpenAI and Claude accounts, with the opt-out documented outside the README.
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
T3 Code
- Set T3CODE_TELEMETRY_ENABLED=false before starting the server if you don't want usage events sent
- Install and log in to at least one provider CLI first, such as codex login or claude auth login
- Use a managed policy to fix settings across a team
Questions
Which is better for AI agents, Friday or T3 Code?
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.
Are Friday and T3 Code open source?
Yes. Friday is open source (MIT). T3 Code is open source (MIT).
Other comparisons with Friday or T3 Code
- Agent Zero vs Friday
- Agent Zero vs T3 Code
- Aider vs Friday
- Aider vs T3 Code
- Amp vs Friday
- Amp vs T3 Code
- Antigravity CLI vs Friday
- Antigravity CLI vs T3 Code
- Auggie CLI vs Friday
- Auggie CLI vs T3 Code
- AXLR vs Friday
- AXLR vs T3 Code
- boxes.dev vs Friday
- boxes.dev vs T3 Code
- Claude Code vs Friday
- Claude Code vs T3 Code
- Click vs Friday
- Click vs T3 Code
- Cline vs Friday
- Cline vs T3 Code
- Conductor vs Friday
- Conductor vs T3 Code
- Crush vs Friday
- Crush vs T3 Code
- Cursor CLI vs Friday
- Cursor CLI vs T3 Code
- DeepSeek Harness (dsh) vs Friday
- DeepSeek Harness (dsh) vs T3 Code
- dsh-superagent (DeepSeek) vs Friday
- dsh-superagent (DeepSeek) vs T3 Code
- Devin vs Friday
- Devin vs T3 Code
- Droid CLI vs Friday
- Droid CLI vs T3 Code
- Pi vs Friday
- Pi vs T3 Code
- Emdash vs Friday
- Emdash vs T3 Code
- Friday vs Harness²
- Friday vs mini-swe-agent
- Friday vs OpenAI Agents API
- Friday vs OpenAI Codex
- Gemini CLI vs T3 Code
- GitHub Copilot CLI vs T3 Code
- goose vs T3 Code
- Harness² vs T3 Code
- HarnessRouter vs T3 Code
- Jules vs T3 Code
- Junie CLI vs T3 Code
- Kilo Code CLI vs T3 Code
- Kimi Code CLI vs T3 Code
- Kiro CLI vs T3 Code
- Letta vs T3 Code
- mini-swe-agent vs T3 Code
- MiniMax Code vs T3 Code
- Mistral Vibe CLI vs T3 Code
- Muse Code vs T3 Code
- OpenAI Agents API vs T3 Code
- OpenAI Codex vs T3 Code
- OpenCode vs T3 Code
- OpenHands vs T3 Code
- Orca vs T3 Code
- Paseo vs T3 Code
- Prime Agent vs T3 Code
- Qoder CLI vs T3 Code
- Qwen Code vs T3 Code
- Mirror CLI vs T3 Code
- Rovo Dev CLI vs T3 Code
- Sculptor vs T3 Code
- T3 Code vs Traycer
- T3 Code vs Unstoppable
- T3 Code vs Verdent
- T3 Code vs Vibe-Trading
- T3 Code vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Friday
- Agent Relay vs T3 Code
- Clawboo vs Friday
- Clawboo vs T3 Code
- CLI Manager vs Friday
- CLI Manager vs T3 Code
- 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 Traycer
- Friday vs Unstoppable
- Friday vs Verdent
- Friday vs Vibe-Trading
- Friday vs Warp (Warp Agent CLI and the Oz Agent API)
- Harness vs T3 Code
- herdr vs T3 Code
- OpenMausBot vs T3 Code
- Paperclip vs T3 Code
- Parallax vs T3 Code
Machine-readable
- This page as Markdown
/compare/friday-work-vs-t3-code.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/friday-work.json·/api/v1/tools/t3-code.json - From a terminal
anchor compare friday-work t3-code(the CLI) - Over MCP
compare_tools {"a": "friday-work", "b": "t3-code"}at/mcp, no key