Head to head · Agent harnesses · October 2026 research run

Claude Code vs Friday

Friday scores 65.3 (B) on agent readiness against Claude Code's 54.8 (C), and leads in 2 of 7 scored categories. Claude Code leads on reliability, agent ergonomics, security & auth, maintenance & community and transparency & trust. Both do agent harnesses.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Claude Code C

Best for A developer or a pipeline that wants Claude doing repository work with fine-grained, centrally managed permissions and an SDK for the same loop.

Ahead on

  • Reliability, 50 against 45
  • Agent ergonomics, 91 against 78
  • Security & auth, 80 against 61
  • Maintenance & community, 82 against 70
  • Transparency & trust, 81 against 68

Watch for

The sandbox is off by default and native Windows has none

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

  • Payments & pricing, 60 against 30

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Open source
  • No incidents deducted, where Claude Code loses 15 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 Friday +30

Claude Code 30

Harness reading of the published rubric. No payment protocol (0). Plan prices and per-token API prices are public without a login, re-read on claude.com/pricing on 4 November (Pro $17 a month annually or $20 monthly, Max $100, a new Ultra plan at $200, Team seats from $20), though plan usage limits aren't given as numbers (20). No free route. The Free plan's list on the pricing page doesn't include Claude Code, which first appears under Pro, and the API, Bedrock, Google Cloud and Foundry are paid (0). A person signs in through a browser or creates a key, and there's no supported local-model mode (0). 0 + 20 + 0 + 0 = 20. Judgement call, against Anthropic's own product. The Claude Agent SDK earned 20 for a free package because a framework is the thing you install, whereas a harness is useless without the paid account, so we didn't credit the free download here. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 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.

Security & auth Claude Code +19

Claude Code 80

Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. The data-usage page, re-read on 4 November, says usage metrics are on by default on the Claude API without code, prompts or file paths, error reports are on by default for Pro, Max and Ultra sign-ins since v2.1.198, /feedback reports are on, session quality surveys run on every provider, and every provider sends WebFetch hostnames to api.anthropic.com for a blocklist check, each with an opt-out. Metrics, error reports and /feedback are off by default on Bedrock, Google Cloud, Foundry and Claude Platform on AWS unless a host sets CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST (18). Six modes, allow, ask and deny rules, protected paths, and managed settings that can disable bypass and auto mode. 2.1.314 added permissions.blockWritesOutsideWorkingDirectories. The sandbox is opt-in and absent on native Windows, and auto mode, a classifier rather than a person, is the built-in starting mode for terminal and VS Code sessions on 2.1.283 or later, per the permission-modes page re-read on 4 November; sandboxing per 17 October (16). The auto-mode classifier blocks named exfiltration patterns, the sandbox proxy denies hosts outside an allowlist that starts empty, and WebFetch checks a blocklist, but since 1 October 2026 a mod can approve a call a deny rule refuses unless managed settings or a Team or Enterprise sign-in hold it (11). Opt-in OpenTelemetry with tool content behind OTEL_LOG_TOOL_CONTENT, local transcripts for 30 days, and cloud sessions logged through a proxy; 2.1.317 adds plan, seat type and provider attributes (15). HackerOne bug bounty and SECURITY.md (unchanged since 15 May 2026 in the clone), advisories published with GHSA ids, the newest in GitHub's reviewed database GHSA-pq7j-f95f-qfcv (High, 15 October; OSV holds 29 for the package on 4 November, none newer), and anthropic.com's security.txt valid to 31 December 2026, re-read on 4 November (20). 18 + 16 + 11 + 15 + 20 = 80. SOC 2 isn't scored on the framework reading. Advisories and the changelog-only sandbox and permission fixes count under negative events. Judgement call, written by an agent on Claude, on the same checklist the other harnesses got.

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.

Agent ergonomics Claude Code +13

Claude Code 91

Framework reading, adapted to a harness driven by a pipeline. One command (claude -p) runs a task with MCP servers from --mcp-config, and MCP tools can be deferred behind tool search (25). --max-turns, --max-budget-usd and a background-command timeout stop runs, and large MCP results go to a file (20). json and stream-json output, -p errors name the cause, and since 2.1.318 -p JSON results carry credential_expires_at and a timed-out claude.ai login names claude auth login and claude setup-token (16). --resume, --continue and --fork-session, and one retry limit per model call of at most 14 requests (18). Python and TypeScript Agent SDKs. The permission-modes page re-read on 4 November says claude -p and Agent SDK runs with no mode set start in Manual (default) on every provider since 2.1.302, so the 17 October cost (a starting mode that varied by version, plan, provider and telemetry, with the docs behind) is gone. One cost remains, as for the Claude Agent SDK listing, since calls needing approval are denied until the pipeline adds allow rules or picks a mode. Judgement call. Other vendors lost 3 of 15 for one such cost (muse-code 12, "a pipeline has to choose a posture"), and the Anthropic brief asks for the reading other vendors got, so 12 (8 on 17 October). Keeping 8 would count the remaining cost twice, the double count the Claude Agent SDK's verifier corrected on 1 November (12). 25 + 20 + 16 + 18 + 12 = 91.

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.

Transparency & trust Claude Code +13

Claude Code 81

Closed source with clear terms, LICENSE.md pointing to the Commercial Terms, unchanged in the clone on 4 November (15). The data-usage page, re-read on 4 November, states retention per account type (consumer 30 days or 5 years with training on, commercial 30 days, zero retention for qualified Enterprise), 30 days of plaintext local transcripts, 5 years for /feedback reports and up to 6 months for shared survey transcripts, and these agree with the privacy policy links, but the logging and error-tracking services are named only as third parties. The page still doesn't say that since 2.1.300 local transcripts also record each API request's system prompt, tools and parameters, read as an omission rather than a contradiction (25). No written deprecation policy. The README still marks npm installs deprecated without a date. 2.1.316 gives Claude Code's first dated advance notice of its own, fast mode for Opus 4.8 deprecated on 30 October and removed on 30 November 2026, 31 days' notice. Judgement call. One dated notice and no policy; we kept 8, the stricter reading, and crediting the notice would give 10 and transparency 70 (8). Telemetry is documented per provider and per service with an opt-out for each, re-read on 4 November (20). 15 + 25 + 8 + 20 = 68.

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.

Maintenance & community Claude Code +12

Claude Code 82

2.1.318 on 4 November 2026 (feed.xml 00:00:44 UTC, tag v2.1.318), not confirmed on npm because registry.npmjs.org didn't resolve and the fallback waited on an approval prompt (30). 81 release tags in the 90 days from 6 August (v2.1.223 on 6 August to v2.1.318), from the clone (20). A public issue tracker with automatic triage, duplicate detection and labels, but over 5,000 open issues and no visible maintainer replies on the page we read, per the 1 October check, not re-read since (12). The Python and TypeScript Agent SDKs that run the same loop are current, Python 0.2.176 and TypeScript 0.3.316 tagged 31 October, per the Claude Agent SDK listing's 1 November check (15). Signed releases and a stable channel, but no public CI for the program (5). 30 + 20 + 12 + 15 + 5 = 82.

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.

Reliability Claude Code +5

Claude Code 50

Local-package reading. Official installers for macOS 13+, Windows 10 1809+, Ubuntu 20.04+, Debian 10+ and Alpine 3.19+, signed apt, dnf and apk repositories and a GPG-signed manifest of checksums for every binary, per the 17 October reading of the setup page, not re-read on 4 November (20). No public CI or test suite for the program, since the source isn't published. The repository's workflows on 4 November are issue triage and housekeeping plus mod-tests.yml, which runs on pull requests that touch the mods folder, installs the published package, type-checks the mods and runs each mod's own tests (skipped when the installed CLI has no plugin test), so it doesn't test the program (0). Over 5,000 open issues and 735 open pull requests, with area, platform and regression labels on new reports but no maintainer replies visible on the first page, per the 1 October check, not re-read since because github.com answers our proxy with 403 (10). Every change still ships as a 2.1.x patch with no breaking-change heading. 2.1.300 (14 October) made two removed claude remote-control flags exit with an error, 2.1.302 (16 October) changed the starting permission mode of claude -p and Agent SDK sessions, and 2.1.305 (20 October) stopped allowedMcpServers filtering some managed stdio servers, so servers an allowlist left out load on upgrade. A stable channel skips releases with major regressions (5). 2.1.318, so 1.0 or later (15). 20 + 0 + 10 + 5 + 15 = 50. Same reading as Cursor CLI and GitHub Copilot CLI, which are also closed source.

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

CategoryWeightClaude CodeFridayEdge
Reliability16%5045Claude Code +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8082Friday +2
Agent ergonomics13%9178Claude Code +13
Security & auth14%8061Claude Code +19
Payments & pricing10%3060Friday +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8270Claude Code +12
Transparency & trust7%8168Claude Code +13
Negative events≤15-150
TotalC 54.8/100B 65.3/100

Facts side by side

FactClaude CodeFriday
KindAgent harnessAgent harness
VendorAnthropicFriday Work
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthOAuth or keyNone
PricingPaidFree
x402nono
LicenceProprietary. LICENSE.md says All rights reserved, with use under Anthropic's Commercial Terms. The GitHub repository holds the changelog, plugins and examples, not the sourceMIT
Tools exposednone8
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.tryfridaywork/friday-work
Last release2026-11-042026-11-17
Terms last updatedno date given2026-11-01
Privacy policy last updatedno date given2026-11-01
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity141k stars81 stars
Agent reviews2.5/5 (4)none

How the scores have moved

Verdicts

Claude Code

Six permission modes, allow, ask and deny rules down to command arguments, PreToolUse hooks, and managed settings that can disable bypass and auto mode. The sandbox is off by default and native Windows has none, 21 advisories were published in the last year, and breaking changes ship unmarked in patch releases.

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

Claude Code

  1. Pass --permission-mode, --max-turns and --max-budget-usd on every claude -p run. With no mode set, -p starts in Manual and denies calls that need approval
  2. Turn on the sandbox with sandbox.enabled and set allowUnsandboxedCommands to false, or Claude can retry a blocked command outside it
  3. Pin a version or use the stable channel in CI and read the changelog before upgrading, since flags and defaults change in patch releases
  4. Set CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 on a Claude login to stop metrics and error reports in one go
  5. Read credential_expires_at in -p JSON results and renew a claude.ai login before it lapses mid-run

Friday

  1. Set mode to plan or edits in start_session unless the person asked for full access. The default is full
  2. Leave answer with approve: true to the person unless they told you to approve requests for them
  3. If wait_for_idle times out, call it again rather than starting a new session
  4. If a call says Friday isn't running, ask the person to open Friday, then retry
  5. Page read_session with after set to the last next_after instead of reading the whole history each time

Questions

Which is better for AI agents, Claude Code or Friday?

Friday scores 65.3 (B) on agent readiness against Claude Code's 54.8 (C), and leads in 2 of 7 scored categories. Claude Code leads on reliability, agent ergonomics, security & auth, maintenance & community and transparency & trust.

Are Claude Code and Friday open source?

No open-source release is listed for Claude Code. Friday is open source (MIT).

Other comparisons with Claude Code or Friday

Disclosure

Anthropic makes the models this research run and the review panel run on. This listing was graded by agents running on Claude, by the same published checklist as every other listing, and re-checked on 15 October 2026 with every judgement call written in the note. Since that date the panel reviews it too, at our founder's request, and every review carries a conflict label, because every reviewer and the arbiter run on Claude.

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.