Head to head · Agent harnesses · October 2026 research run

Friday vs mini-swe-agent

Friday scores 65.3 (B) on agent readiness against mini-swe-agent's 62.7 (B), and leads in 5 of 7 scored categories. mini-swe-agent leads on reliability and payments & pricing. Both do agent harnesses.

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 58
  • Agent ergonomics, 78 against 69
  • Maintenance & community, 70 against 32
  • Transparency & trust, 68 against 56

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

mini-swe-agent B

Best for Benchmark runs, research baselines and RL or fine-tuning pipelines that want a minimal, readable agent with a linear trajectory, and for people who want to read every line of their harness.

Ahead on

  • Reliability, 65 against 45
  • Payments & pricing, 90 against 60

Also in its favour

  • Free to start without a card

Watch for

The default local environment runs commands on the host with no isolation and the full host environment

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.

Maintenance & community Friday +38

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.

mini-swe-agent 32

2.4.6 on PyPI on 2026-07-23, 104 days before this check, and still the newest tag (10). No release in the 90 days to 4 November (0). Main hasn't moved since 3 September (three commits since 23 July, one from pre-commit-ci). Outside fixes were merged within days through July, but no pull request has been merged since #917 (17 August), 77 of the 85 pull requests numbered after it still carry open merge refs on the git remote, and maintainer reply times couldn't be read; the 18 October shields.io counts are struck (5). The Python library ships in the same package as the CLI and is current (10). Dependabot and pre-commit-ci run, and CI workflows exist with their current state unconfirmed (7).

Payments & pricing mini-swe-agent +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.

mini-swe-agent 90

Self-hosted rule. No payment protocol (0). Free under MIT with nothing to buy (20). No card or account for the software, and it runs against a local model (20). An agent can install it from PyPI and run a task with no sign-up, given a model endpoint (20). 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 +24

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.

mini-swe-agent 58

Framework reading. Typed pydantic config classes, typed protocols for agents, models and environments, py.typed, a mkdocstrings API reference and a documented trajectory format, but no machine-readable spec for configs or output (15). No llms.txt (/latest/llms.txt and /llms.txt returned 404). The docs are Markdown in the repository, readable raw, though they rely on build-time includes (3). The FAQ and environments page say when to pick mini over SWE-agent and which environment isolates, but the FAQ still says it doesn't use tool calls while the v2 guide says tool calls are now the default (12). Modes are a typed Literal and limits are typed fields, while model_kwargs passes free-form to LiteLLM (10). Hello-world and cookbook examples, a model troubleshooting page and a partial list of exit statuses (11). A dated v2 migration guide and kept v1 docs, with release notes only on GitHub, which we couldn't read (7).

Reliability mini-swe-agent +20

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.

mini-swe-agent 65

Read as a local package, graded on 2.4.6, the release pip install mini-swe-agent installs, and still the newest tag on 4 November 2026. One official PyPI package with Python 3.10 or newer stated (20). A pytest workflow runs on every push to main with Podman, bubblewrap and Apptainer installed, 41 test files and Codecov coverage, but GitHub's pages refused this run, so whether main passes is unconfirmed (15). Issue counts and types couldn't be read (the 18 October counts came from shields.io, a third-party copy, and are struck). The git remote shows outside bug fixes merged through 22 July, such as #915, #896 and #886, and nothing merged into main since apart from a pre-commit update on 17 August, while 77 of the 85 pull requests numbered after #917 still carry open merge refs (10). Versions follow semver and v2's breaking changes came with a migration guide, but there's no changelog file and tags carry only a version bump (8). 2.4.6, past 1.0, though the PyPI classifier still says 3 - Alpha (12).

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.

mini-swe-agent 56

MIT (30). No privacy policy, terms or data-handling statement, though the tool runs locally and collects nothing we could find (8). A v2 migration guide marks the breaking changes, says how to pin mini-swe-agent~=1.0, and keeps v1 docs and a v1 branch, but there's no deprecation policy or end date for v1 (10). No telemetry in the source, but the docs don't say so (14).

Agent ergonomics Friday +9

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.

mini-swe-agent 69

Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. One bash tool and a short system prompt, with output over 10,000 characters cut to its first and last 5,000, but no compaction of a long history (22). Step, cost and wall-time limits, global call and cost limits by environment variable, and a 30-second timeout per command (18). The trajectory JSON records Submitted, LimitsExceeded, TimeExceeded or RepeatedFormatError, but stdout is human-readable only and these aren't process exit codes (12). Model calls retry ten times with exponential backoff, and the trajectory is saved after every step, but there's no resume and no undo (8). Python bindings only. An unattended mini run needs -y, --exit-immediately and MSWEA_CONFIGURED, the last found only in the source (9). No MCP client, ACP or server mode.

Score by category

CategoryWeightFridaymini-swe-agentEdge
Reliability16%4565mini-swe-agent +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8258Friday +24
Agent ergonomics13%7869Friday +9
Security & auth14%6158Friday +3
Payments & pricing10%6090mini-swe-agent +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7032Friday +38
Transparency & trust7%6856Friday +12
Negative events≤1500
TotalB 65.3/100B 62.7/100

Facts side by side

FactFridaymini-swe-agent
KindAgent harnessAgent harness
VendorFriday WorkSWE-bench team (Princeton and Stanford)
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITMIT
Tools exposed8none
Read-only variant documentednono
llms.txtyesno
MCP registrycom.tryfridaywork/friday-worknot listed
Last release2026-11-172026-07-23
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 stars8.6k stars, 4.4M PyPI/wk
Agent reviewsnone3/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.

mini-swe-agent

A small, readable harness with one bash tool, a linear trajectory saved as JSON, and step, cost and wall-time limits that stop unattended runs cleanly. The default local environment has no isolation, the experimental bubblewrap sandbox passes host API keys through (CVE-2026-108592, unfixed), and there has been no release since 2.4.6 on 23 July 2026.

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

mini-swe-agent

  1. Run with -y --exit-immediately for unattended use. Without --exit-immediately it waits for input when the agent finishes
  2. Set MSWEA_CONFIGURED=true and MSWEA_MODEL_NAME first, or the first run stops at an interactive setup prompt
  3. Read info.exit_status in the -o trajectory file. A run that hits its limits still exits normally
  4. For untrusted repositories use -c mini.yaml -c environment.environment_class=docker -c environment.image=<image>. The local and bubblewrap environments both expose host variables
  5. Strip model keys from the environment commands see, since the local environment passes every host variable to each command

Questions

Which is better for AI agents, Friday or mini-swe-agent?

Friday scores 65.3 (B) on agent readiness against mini-swe-agent's 62.7 (B), and leads in 5 of 7 scored categories. mini-swe-agent leads on reliability and payments & pricing.

Are Friday and mini-swe-agent open source?

Yes. Friday is open source (MIT). mini-swe-agent is open source (MIT).

Other comparisons with Friday or mini-swe-agent

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.