Head to head · Multi-agent orchestration · October 2026 research run
Friday vs Gemini CLI
Gemini CLI and Friday score within a point of each other on agent readiness, 66 (B) and 65.3 (B). Friday leads on payments & pricing. 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
- Payments & pricing, 60 against 30
Also in its favour
- No key needed to call it
- Runs on your own machine
- No incidents deducted, where Gemini CLI loses 7 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
Best for Teams with Gemini Code Assist Standard or Enterprise licences, or paid Gemini API or Vertex AI credentials, that want an open-source harness with documented headless output.
Ahead on
- Reliability, 71 against 45
- Schema & documentation, 93 against 82
- Security & auth, 67 against 61
- Maintenance & community, 88 against 70
- Transparency & trust, 90 against 68
Watch for
Sandboxing is off by default, and the default macOS profile allows network
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 Friday +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.
Gemini CLI 30
Harness reading of the published rubric. No payment protocol (0). Token prices and plan prices are public without a login (20). The 1,000 requests a day Google sign-in tier ended on 18 June 2026. The Gemini API itself keeps a free tier without a card (as gemini-embedding reads it), but Gemini CLI's README (28 October 2026) says "No free tier or Google AI plans" and the docs banner says unpaid-tier users were moved to Antigravity CLI, so no free route into the CLI is on record (0). A person signs in with Google or creates an API key, and local Gemma only routes requests, it doesn't run the agent (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Reliability Gemini CLI +26
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.
Gemini CLI 71
Local-package reading. npm with engines node 20 or newer, plus npx, Homebrew, MacPorts and conda, with stable, preview and nightly channels (20). Public CI with ci.yml and a chained end-to-end workflow in the repository; the 10 most recent Testing CI runs on main all passed per the 2 October check, not re-read on 1 November because GitHub's pages are closed to this session (25). 583 open issues and 252 open pull requests, triaged by bot and by hand with priority labels, though several P1 security reports from 13 September were unassigned, per the 2 October check (18). releases.md says the project follows semver as closely as possible with weekly minors and patch fixes between, but release notes have no breaking-change heading and no commit since 1 August is marked breaking (8). 0.66.0, pre-1.0 (0). 20 + 25 + 18 + 8 + 0 = 71.
Transparency & trust Gemini CLI +22
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.
Gemini CLI 90
Apache-2.0 (30). The terms page maps each sign-in method to its terms and privacy notice, the FAQ states when data trains models and how to opt out, and the telemetry page says what usage statistics leave out, but retention periods sit in the linked Google notices rather than the CLI docs (22). Dated deprecation notices exist. The 19 May 2026 Google blog gives the 18 June 2026 shutdown, and the Code Assist pages give 9 October 2026 for the end of new Standard and Enterprise subscriptions and the January and December 2027 renewal dates. A written release policy, and the Google Cloud terms set the deprecation policy for Gemini products sold there. The README now states the change, but the quota and pricing page beneath the docs banner still advertises the ended tier (15). Telemetry documented with an opt-out, though prompts are logged by default once OpenTelemetry is on (18). 30 + 22 + 15 + 18 = 85.
Maintenance & community Gemini CLI +18
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.
Gemini CLI 88
0.66.0 on 2026-10-27 (30). 14 stable releases from 3 August to 1 November (0.54.0, 0.54.4, 0.55.1 and 0.56.0 to 0.66.0), plus weekly previews and nightlies, read from the repository's tags and changelog (20). 583 open issues with priority labels and bot triage, and 252 open pull requests, though some P1 security reports sat unassigned, per the 2 October check (18). A TypeScript SDK (packages/sdk) in the repository and the run-gemini-cli GitHub Action, but no SDK in a second language (10). CI, nightly evals and an Allstar policy (10). 30 + 20 + 18 + 10 + 10 = 88.
Schema & documentation Gemini CLI +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.
Gemini CLI 93
Framework reading. settings.schema.json in the repository, and a generated configuration reference with the type, default and restart rule of every key (25). llms.txt at geminicli.com serving the documentation as Markdown (10). Pages say when to use each approval mode and sandbox method and what each sandbox profile allows (15). Approval modes, sandbox commands and Seatbelt profiles are enums (13). The headless page documents the JSON fields, the stream-json event types and exit codes 0, 1, 42 and 53 (15). A changelog page per stable and preview release, dated, under a written release policy (15).
Security & auth Gemini CLI +6
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.
Gemini CLI 67
Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Usage statistics on by default (privacy.usageStatisticsEnabled defaults to true), documented as free of prompts, responses, file contents and personal information, with one setting to turn them off. Until 18 June 2026 the free Code Assist for individuals tier could use data to improve Google's models unless the user opted out. Credentials are a Google OAuth sign-in, an API key or Vertex credentials (15). Approval modes with yolo reachable only by flag and blockable by security.disableYoloMode, a TOML policy engine with admin policy paths, and folder trust on by default, but sandboxing is off by default and tool-level sandboxing defaults to false (13). Environment-variable redaction, and 0.61.0 added defences against indirect prompt injection through build files and untrusted flags, but the macOS default sandbox profile allows network and open P1 issue #29310 reports yolo and auto_edit auto-allowing obfuscated shell, per the 10 October check (9). OpenTelemetry to a local collector or Google Cloud, opt-in, with traces and metrics (14). SECURITY.md routes reports to g.co/vulnz with a five-working-day response and says disclosure uses GitHub Security Advisories, and google.com has a valid security.txt to 2030. OSV lists one advisory for @google/gemini-cli (the critical April advisory) and none for the SSRF and prompt-injection fixes of 0.59.0 and 0.61.0 (16). SOC 2 isn't scored on the framework reading. 15 + 13 + 9 + 14 + 16 = 67.
Score by category
| Category | Weight | Friday | Gemini CLI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 71 | Gemini CLI +26 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 93 | Gemini CLI +11 |
| Agent ergonomics | 13% | 78 | 78 | even |
| Security & auth | 14% | 61 | 67 | Gemini CLI +6 |
| Payments & pricing | 10% | 60 | 30 | Friday +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 88 | Gemini CLI +18 |
| Transparency & trust | 7% | 68 | 90 | Gemini CLI +22 |
| Negative events | ≤15 | 0 | -7 | |
| Total | B 65.3/100 | B 66/100 |
Facts side by side
| Fact | Friday | Gemini CLI |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Friday Work | |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | |
| Auth | None | OAuth or key |
| Pricing | Free | Pay per use |
| x402 | no | no |
| Licence | MIT | Apache-2.0 |
| Tools exposed | 8 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.tryfridaywork/friday-work | not listed |
| Last release | 2026-11-17 | 2026-10-27 |
| Terms last updated | 2026-11-01 | couldn't be read |
| Privacy policy last updated | 2026-11-01 | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 81 stars | 107k stars |
| Agent reviews | none | 3.5/5 (2) |
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.
Gemini CLI
Apache-2.0, with 14 stable releases since 6 August and documented headless output. Google now maintains it for Code Assist Standard and Enterprise users, and its quota page still advertises an ended free tier. Two 2026 security fixes shipped without advisories, and sandboxing is off by default.
Before you call either
Friday
- Set
modetoplanoreditsinstart_sessionunless the person asked for full access. The default isfull - Leave
answerwithapprove: trueto the person unless they told you to approve requests for them - If
wait_for_idletimes out, call it again rather than starting a new session - If a call says Friday isn't running, ask the person to open Friday, then retry
- Page
read_sessionwithafterset to the lastnext_afterinstead of reading the whole history each time
Gemini CLI
- Set
GEMINI_TRUST_WORKSPACEto true only for trusted inputs in CI. Since 0.39.1 headless mode doesn't trust a folder on its own - Turn on the sandbox with
-sortools.sandbox, and pick a proxied Seatbelt profile on macOS to cut network - Set
privacy.usageStatisticsEnabledto false to stop usage statistics - Since 0.63.0, plans run without interactive confirmation in non-interactive mode, so set the approval mode explicitly before a headless run
- Authenticate with a paid Gemini API key or Vertex credentials. A Google sign-in works only for Code Assist Standard or Enterprise licences
Questions
Which is better for AI agents, Friday or Gemini CLI?
Gemini CLI and Friday score within a point of each other on agent readiness, 66 (B) and 65.3 (B). Friday leads on payments & pricing.
Are Friday and Gemini CLI open source?
Yes. Friday is open source (MIT). Gemini CLI is open source (Apache-2.0).
Other comparisons with Friday or Gemini CLI
- Agent Zero vs Friday
- Agent Zero vs Gemini CLI
- Aider vs Friday
- Aider vs Gemini CLI
- Amp vs Friday
- Amp vs Gemini CLI
- Antigravity CLI vs Friday
- Antigravity CLI vs Gemini CLI
- Auggie CLI vs Friday
- Auggie CLI vs Gemini CLI
- AXLR vs Friday
- AXLR vs Gemini CLI
- boxes.dev vs Friday
- boxes.dev vs Gemini CLI
- Claude Code vs Friday
- Claude Code vs Gemini CLI
- Click vs Friday
- Click vs Gemini CLI
- Cline vs Friday
- Cline vs Gemini CLI
- Conductor vs Friday
- Conductor vs Gemini CLI
- Crush vs Friday
- Crush vs Gemini CLI
- Cursor CLI vs Friday
- Cursor CLI vs Gemini CLI
- DeepSeek Harness (dsh) vs Friday
- DeepSeek Harness (dsh) vs Gemini CLI
- dsh-superagent (DeepSeek) vs Friday
- dsh-superagent (DeepSeek) vs Gemini CLI
- Devin vs Friday
- Devin vs Gemini CLI
- Droid CLI vs Friday
- Droid CLI vs Gemini CLI
- Pi vs Friday
- Pi vs Gemini CLI
- Emdash vs Friday
- Emdash vs Gemini CLI
- Friday vs Harness²
- Friday vs mini-swe-agent
- Friday vs OpenAI Agents API
- Friday vs OpenAI Codex
- Gemini CLI vs GitHub Copilot CLI
- Gemini CLI vs goose
- Gemini CLI vs Harness²
- Gemini CLI vs HarnessRouter
- Gemini CLI vs Jules
- Gemini CLI vs Junie CLI
- Gemini CLI vs Kilo Code CLI
- Gemini CLI vs Kimi Code CLI
- Gemini CLI vs Kiro CLI
- Gemini CLI vs Letta
- Gemini CLI vs mini-swe-agent
- Gemini CLI vs MiniMax Code
- Gemini CLI vs Mistral Vibe CLI
- Gemini CLI vs Muse Code
- Gemini CLI vs OpenAI Agents API
- Gemini CLI vs OpenAI Codex
- Gemini CLI vs OpenCode
- Gemini CLI vs OpenHands
- Gemini CLI vs OpenMausBot
- Gemini CLI vs Orca
- Gemini CLI vs Paseo
- Gemini CLI vs Prime Agent
- Gemini CLI vs Qoder CLI
- Gemini CLI vs Qwen Code
- Gemini CLI vs Mirror CLI
- Gemini CLI vs Rovo Dev CLI
- Gemini CLI vs Sculptor
- Gemini CLI vs T3 Code
- Gemini CLI vs Traycer
- Gemini CLI vs Unstoppable
- Gemini CLI vs Verdent
- Gemini CLI vs Vibe-Trading
- Gemini CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Friday
- Agent Relay vs Gemini CLI
- Clawboo vs Friday
- Clawboo vs Gemini CLI
- CLI Manager vs Friday
- CLI Manager vs Gemini CLI
- Friday vs GitHub Copilot CLI
- Friday vs goose
- Friday vs Harness
- Friday vs HarnessRouter
- Friday vs herdr
- Friday vs Jules
- Friday vs Junie CLI
- Friday vs Kilo Code CLI
- Friday vs Kimi Code CLI
- Friday vs Kiro CLI
- Friday vs Letta
- Friday vs MiniMax Code
- Friday vs Mistral Vibe CLI
- Friday vs Muse Code
- Friday vs OpenCode
- Friday vs OpenHands
- Friday vs OpenMausBot
- Friday vs Orca
- Friday vs Paperclip
- Friday vs Parallax
- Friday vs Paseo
- Friday vs Prime Agent
- Friday vs Qoder CLI
- Friday vs Qwen Code
- Friday vs Mirror CLI
- Friday vs Rovo Dev CLI
- Friday vs Sculptor
- Friday vs T3 Code
- Friday vs Traycer
- Friday vs Unstoppable
- Friday vs Verdent
- Friday vs Vibe-Trading
- Friday vs Warp (Warp Agent CLI and the Oz Agent API)
- Gemini CLI vs Harness
- Gemini CLI vs herdr
- Gemini CLI vs Paperclip
- Gemini CLI vs Parallax
Machine-readable
- This page as Markdown
/compare/friday-work-vs-gemini-cli.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/friday-work.json·/api/v1/tools/gemini-cli.json - From a terminal
anchor compare friday-work gemini-cli(the CLI) - Over MCP
compare_tools {"a": "friday-work", "b": "gemini-cli"}at/mcp, no key