Head to head · Agent harnesses · October 2026 research run

Conductor vs Friday

Friday scores 65.3 (B) on agent readiness against Conductor's 41.3 (E), and leads in every scored category. Both do agent harnesses.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Conductor E

Best for Existing Conductor users planning their move before Cloud closes on 20 November 2026 and the local app winds down in early 2027.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No new downloads or sign-ups since 4 November 2026

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 25
  • Schema & documentation, 82 against 60
  • Agent ergonomics, 78 against 55
  • Security & auth, 61 against 45
  • Payments & pricing, 60 against 0
  • Maintenance & community, 70 against 58
  • Transparency & trust, 68 against 53

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Open source

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 +60

Conductor 0

No new sign-ups since 4 November, free users can't upgrade, and no price is shown. No protocol, no published price, no open free tier, no onboarding (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

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.

Agent ergonomics Friday +23

Conductor 55

Harness reading. Each task gets a workspace, branch, terminal and diff, with pull requests and merges from the app, and an API for integrations; not re-read in detail (55).

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.

Schema & documentation Friday +22

Conductor 60

Harness reading. Docs for workspaces, review and merge, a Conductor API reference page linked from the docs (not read), and security and permissions pages (60).

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.

Reliability Friday +20

Conductor 25

Read as local software that is winding down. Installed from Conductor's own download, which stopped taking new users on 4 November 2026 (10). Closed source, so no public CI or issue tracker (0, 0). A dated changelog, newest 0.93.0 on 4 November (15). Version 0.93 (0). 10 + 0 + 0 + 15 + 0 = 25.

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.

Security & auth Friday +16

Conductor 45

Closed app. Telemetry and data handling weren't read beyond the transition notice (10 of 30). A security and permissions page (10 of 20). No prompt-injection guidance found (5). No audit log found (5). SOC 2 Type II report at trust.conductor.build (15 of 20). 10 + 10 + 5 + 5 + 15 = 45.

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.

Transparency & trust Friday +15

Conductor 53

Closed service with terms and privacy pages (15). The transition notice says when Cloud data deletion begins (20 November) and that all user data is deleted when the app shuts down in early 2027 (20 of 30). Dated shutdown notice (15 of 20). SOC 2 report on a trust portal, subprocessors not read (10 of 20). 15 + 20 + 15 + 10 = 60.

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.

Score by category

CategoryWeightConductorFridayEdge
Reliability16%2545Friday +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6082Friday +22
Agent ergonomics13%5578Friday +23
Security & auth14%4561Friday +16
Payments & pricing10%060Friday +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5870Friday +12
Transparency & trust7%5368Friday +15
Negative events≤1500
TotalE 41.3/100B 65.3/100

Facts side by side

FactConductorFriday
KindAgent harnessAgent harness
VendorConductor (joining Meta)Friday Work
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthOAuth or keyNone
PricingPaidFree
x402nono
LicenceProprietary. A closed-source Mac app and hosted Conductor Cloud under Conductor's termsMIT
Tools exposednone8
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.tryfridaywork/friday-work
Last release2026-11-042026-11-17
Terms last updatednot read yet2026-11-01
Privacy policy last updatednot read yet2026-11-01
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularitynone81 stars

How the scores have moved

Conductor

No score change since it was listed.

Friday

Verdicts

Conductor

Conductor ran parallel coding agents on the Mac, and Meta is acquiring it. It has taken no new users since 4 November 2026, Cloud turns read-only on 13 November and shuts down on 20 November, and the local app winds down in early 2027, when all user data is deleted.

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

Conductor

  1. Export your data from Settings, Account, Export data before 20 November 2026
  2. Move Cloud workspaces to your Mac with Transfer to local before 13 November
  3. Plan a move off the local app before early 2027; see the agent-harnesses category for alternatives

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, Conductor or Friday?

Friday scores 65.3 (B) on agent readiness against Conductor's 41.3 (E), and leads in every scored category.

Are Conductor and Friday open source?

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

Other comparisons with Conductor or Friday

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.