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

Friday vs Mistral Vibe CLI

Friday scores 65.3 (B) on agent readiness against Mistral Vibe CLI's 62.1 (B), and leads in 1 of 7 scored categories. Mistral Vibe CLI leads on reliability, agent ergonomics, payments & pricing and transparency & trust. 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.

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • No incidents deducted, where Mistral Vibe CLI 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

Mistral Vibe CLI B

Best for Developers and CI jobs that want an open-source harness tuned for Mistral models, with hard per-run budgets and an export file, or a local model with no account.

Ahead on

  • Reliability, 69 against 45
  • Agent ergonomics, 84 against 78
  • Payments & pricing, 90 against 60
  • Transparency & trust, 81 against 68

Also in its favour

  • Free to start without a card

Watch for

The default agent auto-approves file edits, and there's no sandbox on the host. Isolation needs the experimental --agent-socket server or a container

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 Mistral Vibe CLI +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.

Mistral Vibe CLI 90

Harness reading of the published rubric, as for openai-codex and qwen-code. No payment protocol (0). Plan prices (Pro $14.99 a month, Team $24.99 a user a month) and per-token API prices for the default model ($1.5 and $7.5 per million) are public without a login (20). A Free plan includes limited coding sessions, and the docs document a fully offline set-up with a local model and no Mistral account. Whether the Free plan asks for a card wasn't checked (20). An agent can install the CLI and run it against a local OpenAI-compatible server with no sign-up, since a llama.cpp provider on 127.0.0.1:8080 is in the defaults (20). 0+20+20+20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Reliability Mistral Vibe CLI +24

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.

Mistral Vibe CLI 69

Local-package reading. PyPI, uv, pip, Homebrew at 3.0.4 and an install script, with Python 3.12 or later stated and UNIX the supported target (20). A public CI workflow on push and pull request to main runs pre-commit, the test suite and a build and install smoke matrix, but GitHub's pages and API were refused in this session, so whether main is passing is unchecked (15 of 25). The 18 October issue counts came from shields.io badges, a third-party copy of GitHub data this run bars, so they are struck. Every release has a Fixed section in the changelog, and how many open issues are crashes or regressions, and how fast they're answered, couldn't be read (10 of 25). The changelog states Keep a Changelog and semver and marks breaking changes, but the hooks rename shipped in minor 2.21.0, patch 2.11.1 changed the -p approval default, patch 2.26.1 removed the bundled local model, and patches 3.0.3 and 3.0.4 carry marked config, model and session breaks (9). 3.0.4, classified Production/Stable (15). 20+15+10+9+15 = 69.

Transparency & trust Mistral Vibe CLI +13

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.

Mistral Vibe CLI 81

Apache-2.0, with LICENSE and pyproject in agreement (30). The README sends readers to Mistral's privacy policy (effective 3 September 2026), which names Vibe. The commercial terms (effective 25 September 2026) say no training on customer data unless a product's default or an opt-in allows it, and the pricing page lists model training as opt-out on Free, Pro and Team. The configuration reference calls telemetry anonymous without listing its fields. The offline guide now names enable_update_checks = false with enable_telemetry = false, as the source reads them (16 of 30; 14 on 18 October, when it named a key the source defines but never reads). Removals are listed in the changelog, deprecated settings are named in the configuration reference and warned about at startup, the agent socket may change without notice, and custom Python tools and the bundled local model were removed in patch releases with warnings (10 of 20). Telemetry is disclosed with an opt-out in the README and the configuration reference, and the README names the server-managed shell-tool rollout, but its fields are only in the source (14 of 20). 30+16+10+14 = 70.

Agent ergonomics Mistral Vibe CLI +6

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.

Mistral Vibe CLI 84

Framework reading, adapted to a harness driven by a pipeline. --enabled-tools and --disabled-tools with globs and regex (in -p the first disables everything else), per-tool and per-MCP-tool permissions, and switches for subagents and background processes (20 of 25). --max-turns, --max-tokens, --max-price and --time-limit, with text, json and streaming output and an export file with usage and cost (20). Exit codes 0 to 4 with named outcomes, refusals reported with a code, and config problems listed under warnings (18). --resume SESSION_ID and --continue, SIGTERM stops a run so it can be resumed, and model API failures are retried before exit 2 (16). One required input (the prompt), a GitHub Action and the ACP server, but no SDK, and the app-server's JSON-RPC protocol isn't documented for outside use (10). 20+20+18+16+10 = 84.

Score by category

CategoryWeightFridayMistral Vibe CLIEdge
Reliability16%4569Mistral Vibe CLI +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8285Mistral Vibe CLI +3
Agent ergonomics13%7884Mistral Vibe CLI +6
Security & auth14%6158Friday +3
Payments & pricing10%6090Mistral Vibe CLI +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7073Mistral Vibe CLI +3
Transparency & trust7%6881Mistral Vibe CLI +13
Negative events≤150-14
TotalB 65.3/100B 62.1/100

Facts side by side

FactFridayMistral Vibe CLI
KindAgent harnessAgent harness
VendorFriday WorkMistral AI
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceMITApache-2.0
Tools exposed8none
Read-only variant documentednoyes
llms.txtyesyes
MCP registrycom.tryfridaywork/friday-worknot listed
Last release2026-11-172026-10-30
Terms last updated2026-11-012026-09-25
Privacy policy last updated2026-11-012026-09-03
Customer content may train modelsnot found in the textyes, with an opt-out
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 textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity81 stars5.1k stars, 332k PyPI/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.

Mistral Vibe CLI

Apache-2.0 with releases most weeks, and headless runs capped by turns, tokens, price and wall time, with typed exit codes and an export file. File edits are auto-approved by default, the host has no sandbox, telemetry is on by default, and patch releases 3.0.3 and 3.0.4 shipped marked breaking changes.

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

Mistral Vibe CLI

  1. Pass --agent on every -p run (plan is read-only). The default is accept-edits, and an experiment can switch it to smart-approve
  2. Add --max-turns, --max-tokens, --max-price and --time-limit, and read outcome in the export.json that --output-dir writes. Exit 3 means a limit or a refusal
  3. Run in a container or behind --agent-socket before using --auto-approve, and set outside_workdir = "deny" to refuse paths outside the working directory
  4. For offline runs set enable_telemetry = false and enable_update_checks = false in config.toml
  5. Pin a version and read the changelog before upgrading, since patch releases can carry marked breaking changes; serve token usage from third-party model servers (stream_options.include_usage)

Questions

Which is better for AI agents, Friday or Mistral Vibe CLI?

Friday scores 65.3 (B) on agent readiness against Mistral Vibe CLI's 62.1 (B), and leads in 1 of 7 scored categories. Mistral Vibe CLI leads on reliability, agent ergonomics, payments & pricing and transparency & trust.

Are Friday and Mistral Vibe CLI open source?

Yes. Friday is open source (MIT). Mistral Vibe CLI is open source (Apache-2.0).

Other comparisons with Friday or Mistral Vibe CLI

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.