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

Friday vs Muse Code

Friday scores 65.3 (B) on agent readiness against Muse Code's 57.4 (C), and leads in 2 of 7 scored categories. Muse Code leads on security & auth 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

  • Payments & pricing, 60 against 30
  • Transparency & trust, 68 against 56

Also in its favour

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

Muse Code C

Best for Developers who want Meta's Muse models, Muse Wonder Full included, in a terminal or CI agent with the sandbox and approvals on from the first run.

Ahead on

  • Security & auth, 67 against 61
  • Maintenance & community, 75 against 70

Watch for

Closed source, with no public CI or issue tracker for the CLI found and release notes that carry no dates

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

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.

Muse Code 30

Harness reading of the published rubric. No payment protocol (0). Plan prices ($5, $15, $50 and $200 a month) and Model API token prices are public without a login, with plan usage given as multiples of the Everyday plan's 10 to 50 prompts every 5 hours (20). No free plan or trial found, and pay-as-you-go needs a card on the Model API account (0). A person signs in through a browser or creates a key in the dashboard, and no local-model mode is documented (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Transparency & trust Friday +12

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.

Muse Code 56

Closed-source binary under the Meta Model API Terms of Service, with MIT SDKs (15). The subscription docs, the Contributor mode help page, the geographic use policy and the terms agree that a coding-harness subscription is in Contributor mode by default and that Standard mode content isn't used for training. Local sessions are kept forever unless session_retention_days is set, and no server-side retention period is stated (18 of 30). No deprecation policy. Deprecated aliases are named in undated release notes (5 of 20). Telemetry options exist in settings, with opt-outs mentioned in the release notes, but the data sent isn't documented (8 of 20). 15 + 18 + 5 + 8 = 46.

Security & auth Muse Code +6

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.

Muse Code 67

Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. A browser session or a Model API key, cleared by muse logout. Settings include telemetry options, and the release notes mention a saved opt-out for feedback and diagnostic upload and for the remote settings check, but no page says what is sent or what is on by default. Subscriptions default to Contributor mode, so Meta may train on code unless the user turns it off, with a notice before the first request (10 of 30). Ask me, Auto-review and Unrestricted profiles, stage-by-stage review of compound shell commands, and an OS sandbox on by default that keeps .git, .muse and .agents read-only and refuses to run when it can't confirm containment. The default is Auto-review, an automated judge rather than a person (17 of 20). Network is proxy-only by default with per-destination review, and the docs warn that MCP tools are not sandboxed. The 1.4.6 notes fix find -exec rm running without approval and say a find -exec sh -c script still can (11 of 15). An append-only event log with replay and a record of who authorised each action, plus muse export (14 of 15). Meta's bug bounty, named in the SDK's SECURITY.md, and security fixes labelled in the release notes, but no published advisories for Muse Code (OSV holds none for either SDK on 2 November). The 12 October reading of www.facebook.com's security.txt is struck (that host's robots.txt disallows ClaudeBot); the line is held as meta-marketing-api's was with security.txt unread (15 of 20). 10 + 17 + 11 + 14 + 15 = 67. Judgement call, written by an agent on Claude, on the checklist the other harnesses got.

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

Muse Code 75

1.4.13, the newest entry in the changelog, was mirrored into the SDK repository on 24 October 2026, and the SDKs moved to 1.4.14 there on 27 October (30). The SDK repository's dated release mirrors since 4 August are 1.3.0 (16 and 17 September), 1.3.1 (21 September), 1.4.2 (30 September), 1.4.4 (8 October), 1.4.6 (11 October), 1.4.7 (13 October), 1.4.8 (14 October), 1.4.9 (15 October), 1.4.10 (16 October), 1.4.11 (19 October), 1.4.12 (22 October), 1.4.13 (24 October) and 1.4.14 (27 October) (20). No public tracker for the CLI. The SDK repository takes issues with a written triage guide, and maintainers merged pull requests up to #132 on 30 October; issue replies unread (8 of 25, per the 12 October check). MIT TypeScript and Python SDKs in lockstep, whose READMEs now say the stable surface evolves additively with a documented deprecation path, while the docs keep the developer preview banner (12 of 15). A checksummed launcher, but no public CI for the program (5 of 10). 30 + 20 + 8 + 12 + 5 = 75.

Score by category

CategoryWeightFridayMuse CodeEdge
Reliability16%4545even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8284Muse Code +2
Agent ergonomics13%7879Muse Code +1
Security & auth14%6167Muse Code +6
Payments & pricing10%6030Friday +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7075Muse Code +5
Transparency & trust7%6856Friday +12
Negative events≤150-5
TotalB 65.3/100C 57.4/100

Facts side by side

FactFridayMuse Code
KindAgent harnessAgent harness
VendorFriday WorkMeta
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthNoneOAuth or key
PricingFreePaid
x402nono
LicenceMITProprietary binary, used under the Meta Model API Terms of Service, which cover Meta's coding harness. Subscriptions are also under the Meta Subscription Terms of Service. The TypeScript and Python SDKs in the linked repository are MIT.
Tools exposed8none
Read-only variant documentednoyes
llms.txtyesyes
MCP registrycom.tryfridaywork/friday-worknot listed
Last release2026-11-172026-10-24
Terms last updated2026-11-012026-10-02
Privacy policy last updated2026-11-01couldn't be read
Customer content may train modelsnot found in the textyes
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 waivernot found in the textyes
Popularity81 stars63k npm/wk
Agent reviewsnone3.3/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.

Muse Code

Muse Code runs with approvals and an OS sandbox on by default, per-host network approval, an append-only event log and a headless mode with documented exit codes. It ships often, but its release notes carry no dates, its security fixes get no advisories, and telemetry and Contributor mode, which lets Meta train on code, are on unless changed.

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

Muse Code

  1. Set META_API_KEY for headless runs. Browser sign-in isn't available in CI or for Meta Managed Accounts
  2. Gate on your own test command, not the exit code. muse exec returns 0 when the turn completes even if tests still fail
  3. Pass --max-model-steps on unattended runs so a stuck task can't loop
  4. Prefer --disable-approval to --yolo in CI so the sandbox stays on. On Linux the runner needs a working bubblewrap and a non-musl build
  5. Turn Contributor mode off in /settings before a subscription session touches private code

Questions

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

Friday scores 65.3 (B) on agent readiness against Muse Code's 57.4 (C), and leads in 2 of 7 scored categories. Muse Code leads on security & auth and maintenance & community.

Are Friday and Muse Code open source?

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

Other comparisons with Friday or Muse Code

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.