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

Friday vs Paseo

Paseo and Friday score within a point of each other on agent readiness, 65.9 (B) and 65.3 (B). Friday leads on schema & documentation and agent ergonomics. 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

  • Schema & documentation, 82 against 65
  • Agent ergonomics, 78 against 70

Also in its favour

  • Runs on your own machine

Watch for

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

Paseo B

Best for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere.

Ahead on

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

Watch for

Pre-1.0, at 0.15.3

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 Paseo +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.

Paseo 90

Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Schema & documentation Friday +17

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.

Paseo 65

Harness reading. Public docs, a CLI and plugin examples in the repository (65).

Agent ergonomics Friday +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.

Paseo 70

Harness reading. A self-hosted daemon that agents can use to create worktrees, launch other agents and talk to them, scriptable from the CLI (70).

Reliability Paseo +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.

Paseo 50

Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.

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

Paseo 75

v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.

Score by category

CategoryWeightFridayPaseoEdge
Reliability16%4550Paseo +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8265Friday +17
Agent ergonomics13%7870Friday +8
Security & auth14%6158Friday +3
Payments & pricing10%6090Paseo +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7075Paseo +5
Transparency & trust7%6868even
Negative events≤1500
TotalB 65.3/100B 65.9/100

Facts side by side

FactFridayPaseo
KindAgent harnessAgent harness
VendorFriday WorkMohamed Boudra
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Tools exposed8none
Read-only variant documentednono
llms.txtyesno
MCP registrycom.tryfridaywork/friday-worknot listed
Last release2026-11-172026-11-07
Terms last updated2026-11-01no document linked
Privacy policy last updated2026-11-01no document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity81 starsnone

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.

Paseo

A self-hosted, open-source workspace for running many coding agents on your own machines, scriptable from the CLI and reachable from phone, web or desktop, with no telemetry or forced log-in. It's pre-1.0 and run largely by one maintainer.

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

Paseo

  1. Run the daemon on the machine that has your tools and credentials, and connect from the clients
  2. Script runs from the CLI for repeatable agent jobs

Questions

Which is better for AI agents, Friday or Paseo?

Paseo and Friday score within a point of each other on agent readiness, 65.9 (B) and 65.3 (B). Friday leads on schema & documentation and agent ergonomics.

Are Friday and Paseo open source?

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

Other comparisons with Friday or Paseo

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.