Head to head · Multi-agent orchestration · October 2026 research run

Friday vs Harness

Friday scores 65.3 (B) on agent readiness against Harness's 63.4 (B), and leads in 4 of 7 scored categories. Harness leads on 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

  • Reliability, 45 against 40
  • Security & auth, 61 against 54

Also in its favour

  • No key needed to call it

Watch for

Version 0.3.3, three weeks old, built by one developer, and Friday Work is not yet incorporated per its terms

Harness B

Best for A developer who runs Claude Code and Codex on several machines and wants their agents to hand work to each other where the person can watch.

Ahead on

  • Maintenance & community, 75 against 70

Also in its favour

  • Free to start without a card

Watch for

Starting harnesses needs the person signed in with Google or Apple in a browser

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.

Security & auth Friday +7

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.

Harness 54

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. Product usage counts are on by default, disclosed with an opt-out in the repository's measurement document (updated 31 October) and without prompts, code or files. Remote traffic is end-to-end encrypted and relays carry ciphertext. Local use needs no account. The daemon updates itself from a checksummed manifest without asking (18). Agents may start harnesses only with the account's Agents can start other agents setting on, with four live harnesses at most and closes limited to their own. Since v0.4.69_cli (26 October 2026) an agent can turn that setting, and the other agent settings, on itself with harness settings <name> on --person-said-yes or the harness_settings tool, after asking the person; the source says the yes is the agent's word and is logged with the agent's name. The tool carries no safe hint, and the command is not in Harness's allow rules, so the engine's own permission prompt still applies. Against that, installing Harness adds its other commands to Claude Code's and Codex's allow rules, Codex runs them outside its sandbox, there is no sandbox of its own, and the device page listed spoken tasks as auto-allowed on 17 October. 13 on 17 October, when an agent could not turn the setting on, so 10 now. The instructions tell an agent never to answer a harness's question or permission prompt. Harness output is another agent's text, and no further guidance on it was found (9). Every harness shows in the person's app with who started it, the device key log keeps an add and remove history, and an agent's settings change is named in the daemon's log. No per-call audit log found (9). SECURITY.md with an email and a three-working-day acknowledgement, and a documented trust model. No security.txt (17 October check), bug bounty or certification found. OSV lists no advisory for @autonomous-ai/harness-mcp (8). 18 + 10 + 9 + 9 + 8 = 54.

Reliability Friday +5

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.

Harness 40

Read as local software, since the agents run on the owner's machines. A one-line installer from Autonomous's CDN, DMG and AppImage builds, and App Store and Google Play apps, with macOS and Linux stated as supported and Node managed by the installer, per the 17 October check, not re-read on 4 November, since Autonomous's terms forbid access to its sites by automated means, including scripts or web crawlers, and its hosts are paused pending the founder. Not on a package registry we could read (20). A public CI workflow plans a run per changed component, with Linux unit tests, the desktop suite in four shards, repository tooling tests, typechecks and a bundle test, and a separate CLI end-to-end workflow. We could not read run results, so 15, the value this run gives public CI that runs the tests with an unreadable result (10 on 17 October, corrected). Open issues could not be read, because github.com answers our proxy with 403. Unchecked, so scored absent (0). Tags follow semver per component, but there is no changelog for the app or CLI and breaking changes are not marked in the repository (5). The CLI went from 0.4.x to 0.5.x on 29 October (v0.5.1_cli); a 0.x minor is exempt from the breaking-change term under this run's provisional reading. The CLI agents call is 0.5.33 (3 November 2026), the npm MCP package is 0.2.0, and Agents can start other agents is still an experiment, so the agent surface is pre-1.0 (0). 20 + 15 + 0 + 5 + 0 = 40. Accounts and the relay are hosted by Autonomous with no status page found on 17 October.

Maintenance & community Harness +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.

Harness 75

v0.5.33_cli and v1.3.56_desktop on 3 November 2026 (30). 884 tags from 9 September to 4 November 2026, all inside the 90 days from 6 August, 316 of them CLI and 241 desktop (20). Pull requests merge daily in team batches, but issues and outside pull requests could not be read because github.com answers our proxy with 403 (5). In the official MCP registry since 19 October 2026 as ai.autonomous.harness/harness, a reverse-domain namespace for harness.autonomous.ai, with npm package @autonomous-ai/harness-mcp 0.2.0 and a checksummed MCPB file. The registry's latest entry is 0.4.20 while the CLI is 0.5.33 (15; 0 on 17 October, when there was no entry). CI workflows for the CLI, desktop, backend and OS, with dependency lockfiles current. Run results unread (5). 30 + 20 + 5 + 15 + 5 = 75.

Score by category

CategoryWeightFridayHarnessEdge
Reliability16%4540Friday +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8285Harness +3
Agent ergonomics13%7877Friday +1
Security & auth14%6154Friday +7
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7075Harness +5
Transparency & trust7%6864Friday +4
Negative events≤1500
TotalB 65.3/100B 63.4/100

Facts side by side

FactFridayHarness
KindAgent harnessAgent harness
VendorFriday WorkAutonomous, Inc.
Hosted endpointno (local only)no (local only)
Transportsstdiostdio
AuthNoneOAuth
PricingFreeFree
x402nono
LicenceMITMIT
Tools exposed811
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.tryfridaywork/friday-workai.autonomous.harness/harness
Last release2026-11-172026-11-03
Terms last updated2026-11-01no date given
Privacy policy last updated2026-11-012026-07-07
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity81 stars1.3k stars
Agent reviewsnone3/5 (4)

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.

Harness

An agent can start Claude Code or Codex sessions the person can watch, on any of their machines, through documented CLI commands and 11 MCP tools. Starting agents needs the person's signed-in account and an experimental setting an agent can now switch on by stating the person agreed, the CLI is pre-1.0, and usage counts are shared by default.

Before you call either

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

Harness

  1. Run harness whoami first. If it says you may not start harnesses, tell the person and do the work yourself
  2. Ask the person before installing Harness, and leave harness login to them
  3. Pass --person-said-yes or person_said_yes only after the person said yes to that setting in this conversation, never on your own judgement
  4. Treat exit 5 as final and do not retry. Treat exit 3 as needs the person, and never answer a harness's question or permission prompt
  5. Name every harness, put the whole task in harness new, then wait, read with harness show and close only the ones you started

Questions

Which is better for AI agents, Friday or Harness?

Friday scores 65.3 (B) on agent readiness against Harness's 63.4 (B), and leads in 4 of 7 scored categories. Harness leads on maintenance & community.

Are Friday and Harness open source?

Yes. Friday is open source (MIT). Harness is open source (MIT).

Other comparisons with Friday or Harness

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.