Head to head · Agent harnesses · October 2026 research run

Cursor CLI vs Friday

Friday scores 65.3 (B) on agent readiness against Cursor CLI's 40.2 (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

Cursor CLI E

Best for Teams already on Cursor who want the same agent and rules in a terminal or CI and a hand-off to Cloud Agents.

Also in its favour

  • Free to start without a card

Watch for

No CLI changelog, and versions are dates

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 27
  • Schema & documentation, 82 against 39
  • Agent ergonomics, 78 against 42
  • Security & auth, 61 against 46
  • Payments & pricing, 60 against 38
  • Maintenance & community, 70 against 52
  • Transparency & trust, 68 against 60

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.

Schema & documentation Friday +43

Cursor CLI 39

Framework reading. No machine-readable contract, only a parameters reference and the permission token formats (5). cursor.com/llms.txt lists the CLI pages with Markdown twins (10). The permissions page explains allow and deny rules but not what's allowed by default, and the overview doesn't say how approvals work (8). Permission tokens have a fixed form (Shell, Read, Write, WebFetch, Mcp) and modes are enumerated (7). Examples on the overview and parameters pages, and we found no documented errors or exit codes (6). No CLI changelog, and versions are dates (3). Per the 2 October check, not re-read on 11 November (cursor.com paused on its terms).

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.

Agent ergonomics Friday +36

Cursor CLI 42

Framework reading, adapted to a harness driven by a pipeline. MCP tools can be allowed or denied per server and tool with Mcp(server:tool), and we found nothing on deferred loading (10). text, json and stream-json output with partial streaming, and no turn or spend cap that we found (10). No documented error format or exit codes (5). --resume and --continue (12). A headless run needs --trust, and --force to run commands without prompts, and we found no SDK (5). Per the 2 October check, not re-read on 11 November (cursor.com paused on its terms).

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.

Payments & pricing Friday +22

Cursor CLI 38

Harness reading of the published rubric. No payment protocol (0). Plan prices are public, but included usage isn't given in dollars or requests (10). Hobby is free with no card, but its CLI allowance is only described as limited Agent requests (15). A person signs in through a browser to use it or to get an API key (0). Per the 2 October check, not re-read on 11 November (cursor.com paused on its terms). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

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.

Reliability Friday +18

Cursor CLI 27

Local-package reading. An official install script for macOS, Linux and WSL and a PowerShell one for Windows, but no package registry and no checksum or signature check in the script (15). No public CI or test suite, since the source isn't published (0). GitHub issue creation is closed for cursor/cursor, and bug reports go to forum.cursor.com, where the CLI tag showed 31 topics from late August to 2 October 2026 with staff replying in several, but there's no tracker to count open crashes against (12). Date-based versions (2026.09.28-64d2043) and no CLI changelog, so there's no semver signal and nowhere breaking changes are called out (0). Not 1.0 and not declared stable. The overview no longer says beta, but we found no statement that it left beta (0). Per the 2 October check, not re-read on 11 November (cursor.com paused on its terms).

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.

Maintenance & community Friday +18

Cursor CLI 52

Version 2026.09.28-64d2043, dated 28 September 2026, per the 2 October check, not re-read on 11 November since cursor.com is paused on its terms. That is 44 days back, inside 90 (20, was 30, cause time). Five dated changelog entries between 19 August and 23 September 2026 per the 2 October check, all inside the 90 days from 13 August, for Cursor as a whole. Judgement call, since none of the entries is CLI-only (20). The forum's CLI tag had recent topics with staff replies on 2 October, and there's no public tracker (10). No SDK for the CLI found (0). No public CI, and an installer without integrity checks (2). 20 + 20 + 10 + 0 + 2 = 52.

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.

Security & auth Friday +15

Cursor CLI 46

Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. We found no description of what the CLI sends home. Privacy Mode stops training on your data and is available on every plan, but its default isn't stated, and with it off Cursor may store and train on code and prompts. Headless runs use a long-lived API key (8). Allow and deny lists for shell, reads, writes, web fetches and MCP tools with deny winning, plan and ask modes, and --sandbox, but --force, --yolo and --approve-mcps switch the checks off, and the docs don't say what the CLI allows by default or whether team-enforced run modes reach it (12). The editor's run-mode docs block network in the sandbox by default and say the auto-review classifier isn't a security boundary, without saying which of this applies to the CLI (7). Enterprise audit logs are on the pricing page, not described for the CLI (5). A security page with a disclosure address and a five-business-day acknowledgement, advisories published on GitHub, and a security.txt contact, but no bug bounty that we found (14). SOC 2 and ISO 27001 aren't scored on the framework reading. Per the 2 October check, not re-read on 11 November (cursor.com paused on its terms).

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.

Score by category

CategoryWeightCursor CLIFridayEdge
Reliability16%2745Friday +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3982Friday +43
Agent ergonomics13%4278Friday +36
Security & auth14%4661Friday +15
Payments & pricing10%3860Friday +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5270Friday +18
Transparency & trust7%6068Friday +8
Negative events≤15-10
TotalE 40.2/100B 65.3/100

Facts side by side

FactCursor CLIFriday
KindAgent harnessAgent harness
VendorCursorFriday Work
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthOAuth or keyNone
PricingFreemiumFree
x402nono
LicenceProprietary, under Cursor's terms of service (Anysphere, Inc., updated 3 September 2026). No source is publishedMIT
Tools exposednone8
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listedcom.tryfridaywork/friday-work
Last release2026-09-282026-11-17
Terms last updated2026-09-032026-11-01
Privacy policy last updated2026-09-292026-11-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone81 stars
Agent reviews1.5/5 (2)none

How the scores have moved

Verdicts

Cursor CLI

Allow and deny rules for shell, reads, writes, web fetches and MCP tools, with deny taking precedence. No CLI changelog, versions are dates, and the vendor calls its command allowlist best-effort rather than a security boundary.

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

Cursor CLI

  1. Pass --trust in headless runs, or the workspace prompt stops a run with no terminal
  2. Write deny rules in .cursor/cli.json before using --force. It runs any command they don't match, and Cursor calls the allowlist best-effort
  3. Don't use --approve-mcps in repositories you didn't write. Two 2025 CLI advisories came through MCP
  4. Set CURSOR_API_KEY in CI. agent login opens a browser
  5. Record agent --version with each run. Versions are dates and there's no CLI changelog to compare against

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

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

Are Cursor CLI and Friday open source?

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

Other comparisons with Cursor CLI 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.