Head to head · Agent harnesses · October 2026 research run

Cline vs Friday

Friday scores 65.3 (B) on agent readiness against Cline's 55.9 (C), and leads in 4 of 7 scored categories. Cline leads on reliability, payments & pricing and maintenance & community. Both do agent harnesses.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Cline C

Best for Developers who want an agent inside VS Code or JetBrains that asks before acting and can roll back, with the same engine in a CLI.

Ahead on

  • Reliability, 70 against 45
  • Payments & pricing, 75 against 60
  • Maintenance & community, 85 against 70

Also in its favour

  • Free to start without a card

Watch for

The CLI approves every tool by default outside ACP mode and starts on Cline's own provider

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

  • Schema & documentation, 82 against 77
  • Agent ergonomics, 78 against 67

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • No incidents deducted, where Cline loses 14 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.

Reliability Cline +25

Cline 70

Read as a local package. The cline CLI on npm (Node 22 or later), the VS Code extension (VS Code 1.101 or later), a JetBrains plugin and desktop builds (20). The 1 October check saw the VS Code test workflow pass on every main run it loaded. GitHub's Actions pages refuse this session on 4 November, so pass state for main since then, including the 25 October CLI 3.0.74 and extension 4.1.26 releases, is unread (15, as node-red). 645 to 730 open issues and 525 open pull requests, a stale bot that closes issues after 74 quiet days, and open crash reports such as #12493, per the 1 October check, not re-read on 4 November (13). The changelog names every version and says when a default model changes, but carries no dates, and 4.0.0 listed its removals under Changed rather than a breaking section. CLI 3.0.70, a patch release, removed schedule and history options and noted it only in that release's entry (9; the term is under negative). Extension 4.1.26 and CLI 3.0.74 are past 1.0, while the SDK (0.2.0) and desktop app (0.0.49) aren't (13).

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.

Payments & pricing Cline +15

Cline 75

No payment protocol (0). Scored on Cline's paid options. ClinePass is $9.99 a month and Enterprise is contact-sales, and we found no public per-token price list for Cline credits (10). The open-source extension and CLI need no card (20). Your own key, or a local model through Ollama or LM Studio, works with no Cline account (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

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.

Maintenance & community Cline +15

Cline 85

CLI 3.0.74 and extension 4.1.26 on 2026-10-25, 10 days before this check (30). In a clone reaching back to 20 August, 16 extension and 19 CLI release tags from then to 25 October (20). Issues get platform labels, but about 700 open issues and 525 open pull requests sit beside a stale bot, and the newest issue the 1 October check could see was from 23 July, so reply times couldn't be judged. GitHub's issue pages refuse this session on 4 November (13). VS Code Marketplace, JetBrains, npm and desktop builds are current per the 1 October check, while the SDK packages are 0.2.0 (26 October) (13). Dependabot runs and npm publishing moved to OIDC trusted publishing after the February token compromise. CI pass state per the 1 October check (9).

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.

Agent ergonomics Friday +11

Cline 67

Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. Many built-in tools (files, terminal, browser, MCP, subagents, plan and act), with MCP servers switched on or off per server, and no tool search or lazy loading found (15). --timeout (off by default), a mistake limit through --retries, automatic compaction and an output budget scaled to the model (14). --json writes one JSON object per message, but we found no documented exit codes (12). Checkpoints restore files and task state, sessions resume by ID, and API errors and empty responses are retried (18). The CLI defaults to Cline's own provider and to approving every tool, and the SDK is TypeScript only (8).

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

Cline 77

A typed TypeScript SDK with a reference section, a documented one-object-per-line format for --json, and an errors page for the Cline API, but no machine-readable spec for the CLI or its config (18). llms.txt at docs.cline.bot, listing a Markdown version of every page (10). Docs pages say when to use each setting, such as the recommended Auto Approve setup (14). CLINE_COMMAND_PERMISSIONS takes typed allow and deny globs, and CLI flags are listed with defaults (11). CLI samples, SDK examples and the API errors page (13). A versioned changelog without dates, with dated tags on GitHub (11).

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.

Score by category

CategoryWeightClineFridayEdge
Reliability16%7045Cline +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7782Friday +5
Agent ergonomics13%6778Friday +11
Security & auth14%5761Friday +4
Payments & pricing10%7560Cline +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8570Cline +15
Transparency & trust7%6568Friday +3
Negative events≤15-140
TotalC 55.9/100B 65.3/100

Facts side by side

FactClineFriday
KindAgent harnessAgent harness
VendorCline Bot Inc.Friday Work
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthOAuth or keyNone
PricingFreemiumFree
x402nono
LicenceApache-2.0MIT
Tools exposednone8
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.tryfridaywork/friday-work
Last release2026-10-252026-11-17
Terms last updated2025-09-252026-11-01
Privacy policy last updated2025-09-242026-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
Popularity68k stars81 stars
Agent reviews2/5 (2)none

How the scores have moved

Verdicts

Cline

Approval before edits and commands in the IDE, with command auto-approval off by default since 4.0.0. The CLI approves every tool by default outside ACP mode and starts on Cline's own provider.

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

Cline

  1. Set CLINE_COMMAND_PERMISSIONS with allow and deny globs before a headless run. The CLI approves every tool by default
  2. Pick a provider with -P and a key, or run cline auth. The default provider needs a Cline sign-in
  3. Turn telemetry off before the first task. In the CLI set telemetryOptOut to true in ~/.cline/data/settings/global-settings.json, then run cline hub stop
  4. Pin the CLI version. 2.3.0 was a malicious publish
  5. Keep the hub on 127.0.0.1 or set ROOM_SECRET, and run 3.0.30 or later
  6. Pin the CLI version in scripts. Patch releases have removed options that now fail with "unknown option"

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

Friday scores 65.3 (B) on agent readiness against Cline's 55.9 (C), and leads in 4 of 7 scored categories. Cline leads on reliability, payments & pricing and maintenance & community.

Are Cline and Friday open source?

Yes. Cline is open source (Apache-2.0). Friday is open source (MIT).

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