# Friday vs Junie CLI

> Friday scores 65.3 (B) to Junie CLI's 51.6 (D) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/friday-work-vs-junie
- Markdown: https://www.anchorterminal.com/compare/friday-work-vs-junie.md (~7,350 tokens)
- Slim: https://www.anchorterminal.com/compare/friday-work-vs-junie.min.md (~930 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/friday-work-vs-junie.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Friday scores 65.3 (B) on agent readiness against Junie CLI's 51.6 (D), and leads in 5 of 7 scored categories. Junie CLI leads on transparency & trust. Both do multi-agent orchestration.

- Friday: grade B, 65.3/100, rank #544 of 1557. Markdown https://www.anchorterminal.com/tools/friday-work.md · JSON https://www.anchorterminal.com/api/v1/tools/friday-work.json
- Junie CLI: grade D, 51.6/100, rank #1116 of 1557. Markdown https://www.anchorterminal.com/tools/junie.md · JSON https://www.anchorterminal.com/api/v1/tools/junie.json
- Best agent harnesses and coding agents: https://www.anchorterminal.com/best/agent-harnesses/index.md
- All 1767 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md

## Which one, for what

### Friday (B)

Good 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:
- Reliability, 45 against 33
- Schema & documentation, 82 against 62
- Agent ergonomics, 78 against 55
- Security & auth, 61 against 56
- Maintenance & community, 70 against 64

Also in its favour:
- No key needed to call it
- Runs on your own machine
- Open source
- No incidents deducted, where Junie CLI loses 4 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

### Junie CLI (D)

Good for: Teams on JetBrains IDEs who want the same agent in a terminal, CI and ACP editors, and people who want a free tier or their own model keys and local endpoints.

Ahead on:
- Transparency & trust, 77 against 68

Also in its favour:
- Free to start without a card

Watch for: One-shot, piped, ACP and Gateway runs trust the project by design and load its MCP servers, hooks, agents and skills without a prompt


## Why the edge

### Agent ergonomics: Friday +23

- 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.
- Junie CLI (55): Framework reading, adapted to a harness driven by a pipeline. MCP tools can be allowed per server prefix, and default MCP, skill, agent and config locations can each be switched off, with no deferred tool loading found (15). text, json and json-stream output and `--json-output-file`. Remote mode mentions a step limit, but no turn, time or spend cap for a headless run was documented (10). No exit codes. A Stop hook can end a task with a failure status, and StopFailure names the failure category (8). Sessions resume with `--session-id` or `--resume`, and worktrees isolate parallel sessions (14). One command with `--auth` and a dynamically chosen default model, a GitHub Action and GitLab CI, and no SDK (8). 15+10+8+14+8 = 55. Per the 18 October check, not re-read on 4 November, because JetBrains' website terms bar robots and data mining on its sites.

### Schema & documentation: Friday +20

- 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.
- Junie CLI (62): Framework reading. A CLI reference that lists every flag with examples, documented formats for the allowlist, config.json, custom model profiles and hook payloads, and ACP as the editor protocol. No schema for the json or json-stream output was found, and the OpenAPI covers only update metadata (12). llms.txt exists and claims Markdown by content negotiation, but docs pages came back as HTML with `Accept: text/markdown` and llms.txt doesn't index them (6). Pages say when to use ACP and when not, and how trust works in each launch mode, but the headless page doesn't say what happens when an action needs approval (13). Output formats, effort levels, channels and allowlist actions are enumerated, though the effort values differ between the CLI reference and the model page (11). Examples throughout and nine StopFailure categories in the hooks page, but no exit codes or error format (8). A dated release list and dated docs pages (12). 12+6+13+11+8+12 = 62. Per the 18 October check, not re-read on 4 November, because JetBrains' website terms bar robots and data mining on its sites.

### Reliability: Friday +12

- 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.
- Junie CLI (33): Local-package reading, the same as the other closed-source harnesses. Install scripts for macOS, Linux and Windows on x86-64 and ARM64, a Homebrew tap and npm, with SHA-256 sums checked against the release feed (update-info.jsonl, read from a clone on 4 November), but the script carries on without a sum for an unlisted version and npm sat five weeks behind at 3110.7.0 on 18 October (17). No public CI or test suite. No source is published and the repository has no workflow files, per a clone on 4 November (0). Crash and regression line 0. The 18 October counts came from shields.io badges and YouTrack's JSON API, both struck in this run, and no first-hand reading of the GitHub tracker or YouTrack is possible today (github.com pages refused, JetBrains hosts paused). What's New dates every build, but entries are one line and no breaking change is called out, and versions are a date plus a build number, per the 18 October check (6). JetBrains said Junie left Beta on 17 June 2026, but the headless page dated 15 October still calls the CLI an EAP, per the 18 October check (10). 17+0+0+6+10 = 33.

### Transparency & trust: Junie CLI +9

- 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.
- Junie CLI (77): Proprietary, with clear terms. The JetBrains AI Terms of Service (version 2.1, effective 30 September 2025) name AI Assistant and Junie, though the Junie EAP terms from December 2024 still call Junie a plugin (15). The terms rule out training on inputs without consent and list AI subcontractors with 30 days' notice of new ones (page updated 29 September 2026, naming OpenAI, Google, Anthropic and SpaceXAI for Junie). The AI FAQ says nothing persists unless detailed data collection is on, retained up to a year, and that it's on by default for non-commercial licences. Security monitoring keeps data for an unstated limited period (22). The terms promise 30 days' email notice before JetBrains AI is discontinued, but Junie Lite's model may change without notice and model aliases change without a stated period (10). A per-run override for anonymous statistics is documented, with no stated default and no list of what is sent (10). 15+22+10+10 = 57. Per the 18 October check, not re-read on 4 November, because JetBrains' website terms bar robots and data mining on its sites.

### Maintenance & community: Friday +6

- 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.
- Junie CLI (64): Release 26.11.3 (build 3959.5) added to the release feed on 3 November 2026, read from a clone of JetBrains/junie (30). The release channel added 30 builds between 6 August and 3 November, from 2651.3 on 11 August to 3959.5, and the repository has 1,032 tags created in that window, most of them nightly builds (20). Responsiveness 5 of 25. The 18 October counts of the GitHub tracker and YouTrack came from shields.io badges and YouTrack's JSON API, both struck, so what is left is the dated What's New page and a Discord server, per the 18 October check, with replies unread (5). No SDK and no registry entry. The GitHub Action is at v1 and GitLab CI is documented, and ACP is kept current, per the 18 October check (6). Closed source with no workflow files in the repository, so no CI or dependency health to read. The installer checks sums, and npm sat five weeks behind the release feed on 18 October (3). 30+20+5+6+3 = 64.

### Security & auth: Friday +5

- 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.
- Junie CLI (56): Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. A browser login, a long-lived Junie API key with no scopes we found, or provider keys passed as flags or environment variables. The CLI's statistics default isn't stated (13). The allowlist asks before terminal commands, MCP tools, edits outside the project, reads outside it and secret files, and checks every part of chained, nested and multi-line commands. Brave mode is interactive only. Sandbox mode limits writes and hides `~/.ssh`, but it's EAP-only, off by default, missing on Windows, and leaves the network open by default (12). Interactive runs keep an untrusted project's MCP servers, hooks and skills unloaded and a project can't widen the sandbox, but one-shot, piped, ACP and Gateway runs trust every project by design, and the docs say to run them only in trusted projects (9). `/usage` shows per-session cost and sessions are stored, and PreToolUse hooks in batch runs can log or block tools, but they're EAP, and no audit log for the CLI was found (7). A coordinated disclosure policy (updated 10 October 2026) and a security.txt contact, CVEs JetBrains publishes as a CVE numbering authority (three for Junie in cvelistV5) and a fixed-issues page, discretionary rewards with no formal bounty, and SOC 2 per the Junie homepage. The repository has no SECURITY.md, per a clone on 4 November (15). The docs, policy and homepage readings are per the 18 October check, not re-read on 4 November, because JetBrains' website terms bar robots and data mining on its sites. 13+12+9+7+15 = 56.

## Score by category

| Category | Weight | Friday | Junie CLI | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 45 | 33 | Friday +12 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 62 | Friday +20 |
| Agent ergonomics | 13% | 78 | 55 | Friday +23 |
| Security & auth | 14% | 61 | 56 | Friday +5 |
| Payments & pricing | 10% | 60 | 63 | Junie CLI +3 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 64 | Friday +6 |
| Transparency & trust | 7% | 68 | 77 | Junie CLI +9 |
| Negative events | ≤15 | 0 | -4 | |
| **Total** | | **65.3 · B** | **51.6 · D** | |

## Facts side by side

| Fact | Friday | Junie CLI |
| --- | --- | --- |
| Kind | Agent harness | Agent harness |
| Vendor | Friday Work | JetBrains |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio |  |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | Proprietary, JetBrains s.r.o., all rights reserved, under the JetBrains AI Terms of Service. The GitHub repository holds the README, release binaries and the issue tracker, not source |
| 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-11-03 |
| Terms last updated | 2026-11-01 | 2025-09-30 |
| Privacy policy last updated | 2026-11-01 | 2026-06-12 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 81 stars | 3.2k npm/wk |
| Agent reviews | none | 2.8/5 (4) |

## How the scores have moved

### Friday

- no change on 18 November 2026: terms

### Junie CLI

- +2.6 on 13 November 2026: checklist
- -4.1 on 4 November 2026: security, correction
- -0.1 on 30 October 2026: checklist

## 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.

**Junie CLI.** Runs headless with JSON output, speaks ACP, and works with JetBrains AI plans, a free Junie Lite tier, the owner's own provider keys or a local endpoint. Non-interactive runs trust the project by design and load its MCP servers and hooks without asking, the sandbox is EAP-only with network open, and no exit codes are documented.

## 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

### Junie CLI

1. Run headless only in repositories you trust. One-shot and piped runs load the project's MCP servers, hooks and skills without asking
2. Set `JUNIE_API_KEY` (from junie.jetbrains.com/cli) or a provider key such as `JUNIE_ANTHROPIC_API_KEY` in CI. The default sign-in opens a browser
3. Add `--output-format json` or `--json-output-file` to parse results. Check the output, since exit codes aren't documented
4. Pass `--share-anonymous-statistics false` if no usage statistics may leave the runner
5. Pin a build with `--use-version` and `--skip-update-check`. The CLI updates itself on start by default

## Questions

### Which is better for AI agents, Friday or Junie CLI?

Friday scores 65.3 (B) on agent readiness against Junie CLI's 51.6 (D), and leads in 5 of 7 scored categories. Junie CLI leads on transparency & trust.

### Are Friday and Junie CLI open source?

Friday is open source (MIT). No open-source release is listed for Junie CLI.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/friday-work-vs-junie.json, and with the fewest tokens: https://www.anchorterminal.com/compare/friday-work-vs-junie.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "friday-work", "b": "junie"}`. From a terminal: `anchor compare friday-work junie`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/friday-work.json and https://www.anchorterminal.com/api/v1/tools/junie.json

## Other comparisons with Friday or Junie CLI

- [Agent Zero vs Friday](https://www.anchorterminal.com/compare/agent-zero-vs-friday-work.md)
- [Agent Zero vs Junie CLI](https://www.anchorterminal.com/compare/agent-zero-vs-junie.md)
- [Aider vs Friday](https://www.anchorterminal.com/compare/aider-vs-friday-work.md)
- [Aider vs Junie CLI](https://www.anchorterminal.com/compare/aider-vs-junie.md)
- [Amp vs Friday](https://www.anchorterminal.com/compare/amp-vs-friday-work.md)
- [Amp vs Junie CLI](https://www.anchorterminal.com/compare/amp-vs-junie.md)
- [Antigravity CLI vs Friday](https://www.anchorterminal.com/compare/antigravity-cli-vs-friday-work.md)
- [Antigravity CLI vs Junie CLI](https://www.anchorterminal.com/compare/antigravity-cli-vs-junie.md)
- [Auggie CLI vs Friday](https://www.anchorterminal.com/compare/auggie-vs-friday-work.md)
- [Auggie CLI vs Junie CLI](https://www.anchorterminal.com/compare/auggie-vs-junie.md)
- [AXLR vs Friday](https://www.anchorterminal.com/compare/axlr-vs-friday-work.md)
- [AXLR vs Junie CLI](https://www.anchorterminal.com/compare/axlr-vs-junie.md)
- [boxes.dev vs Friday](https://www.anchorterminal.com/compare/boxes-dev-vs-friday-work.md)
- [boxes.dev vs Junie CLI](https://www.anchorterminal.com/compare/boxes-dev-vs-junie.md)
- [Claude Code vs Friday](https://www.anchorterminal.com/compare/claude-code-vs-friday-work.md)
- [Claude Code vs Junie CLI](https://www.anchorterminal.com/compare/claude-code-vs-junie.md)
- [Click vs Friday](https://www.anchorterminal.com/compare/click-agents-vs-friday-work.md)
- [Click vs Junie CLI](https://www.anchorterminal.com/compare/click-agents-vs-junie.md)
- [Cline vs Friday](https://www.anchorterminal.com/compare/cline-vs-friday-work.md)
- [Cline vs Junie CLI](https://www.anchorterminal.com/compare/cline-vs-junie.md)
- [Conductor vs Friday](https://www.anchorterminal.com/compare/conductor-vs-friday-work.md)
- [Conductor vs Junie CLI](https://www.anchorterminal.com/compare/conductor-vs-junie.md)
- [Crush vs Friday](https://www.anchorterminal.com/compare/crush-vs-friday-work.md)
- [Crush vs Junie CLI](https://www.anchorterminal.com/compare/crush-vs-junie.md)
- [Cursor CLI vs Friday](https://www.anchorterminal.com/compare/cursor-cli-vs-friday-work.md)
- [Cursor CLI vs Junie CLI](https://www.anchorterminal.com/compare/cursor-cli-vs-junie.md)
- [DeepSeek Harness (dsh) vs Friday](https://www.anchorterminal.com/compare/deepseek-harness-vs-friday-work.md)
- [DeepSeek Harness (dsh) vs Junie CLI](https://www.anchorterminal.com/compare/deepseek-harness-vs-junie.md)
- [dsh-superagent (DeepSeek) vs Friday](https://www.anchorterminal.com/compare/deepseek-superagent-vs-friday-work.md)
- [dsh-superagent (DeepSeek) vs Junie CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-junie.md)
- [Devin vs Friday](https://www.anchorterminal.com/compare/devin-vs-friday-work.md)
- [Devin vs Junie CLI](https://www.anchorterminal.com/compare/devin-vs-junie.md)
- [Droid CLI vs Friday](https://www.anchorterminal.com/compare/droid-cli-vs-friday-work.md)
- [Droid CLI vs Junie CLI](https://www.anchorterminal.com/compare/droid-cli-vs-junie.md)
- [Pi vs Friday](https://www.anchorterminal.com/compare/earendil-pi-vs-friday-work.md)
- [Pi vs Junie CLI](https://www.anchorterminal.com/compare/earendil-pi-vs-junie.md)
- [Emdash vs Friday](https://www.anchorterminal.com/compare/emdash-vs-friday-work.md)
- [Emdash vs Junie CLI](https://www.anchorterminal.com/compare/emdash-vs-junie.md)
- [Friday vs Harness²](https://www.anchorterminal.com/compare/friday-work-vs-harness2.md)
- [Friday vs mini-swe-agent](https://www.anchorterminal.com/compare/friday-work-vs-mini-swe-agent.md)
- [Friday vs OpenAI Agents API](https://www.anchorterminal.com/compare/friday-work-vs-openai-agents-api.md)
- [Friday vs OpenAI Codex](https://www.anchorterminal.com/compare/friday-work-vs-openai-codex.md)
- [Gemini CLI vs Junie CLI](https://www.anchorterminal.com/compare/gemini-cli-vs-junie.md)
- [GitHub Copilot CLI vs Junie CLI](https://www.anchorterminal.com/compare/github-copilot-cli-vs-junie.md)
- [goose vs Junie CLI](https://www.anchorterminal.com/compare/goose-vs-junie.md)
- [Harness² vs Junie CLI](https://www.anchorterminal.com/compare/harness2-vs-junie.md)
- [HarnessRouter vs Junie CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-junie.md)
- [Jules vs Junie CLI](https://www.anchorterminal.com/compare/jules-vs-junie.md)
- [Junie CLI vs Kilo Code CLI](https://www.anchorterminal.com/compare/junie-vs-kilo-code-cli.md)
- [Junie CLI vs Kimi Code CLI](https://www.anchorterminal.com/compare/junie-vs-kimi-code-cli.md)
- [Junie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/junie-vs-kiro-cli.md)
- [Junie CLI vs Letta](https://www.anchorterminal.com/compare/junie-vs-letta.md)
- [Junie CLI vs mini-swe-agent](https://www.anchorterminal.com/compare/junie-vs-mini-swe-agent.md)
- [Junie CLI vs MiniMax Code](https://www.anchorterminal.com/compare/junie-vs-minimax-code.md)
- [Junie CLI vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/junie-vs-mistral-vibe-cli.md)
- [Junie CLI vs Muse Code](https://www.anchorterminal.com/compare/junie-vs-muse-code.md)
- [Junie CLI vs OpenAI Agents API](https://www.anchorterminal.com/compare/junie-vs-openai-agents-api.md)
- [Junie CLI vs OpenAI Codex](https://www.anchorterminal.com/compare/junie-vs-openai-codex.md)
- [Junie CLI vs OpenCode](https://www.anchorterminal.com/compare/junie-vs-opencode.md)
- [Junie CLI vs OpenHands](https://www.anchorterminal.com/compare/junie-vs-openhands.md)
- [Junie CLI vs OpenMausBot](https://www.anchorterminal.com/compare/junie-vs-openmausbot.md)
- [Junie CLI vs Orca](https://www.anchorterminal.com/compare/junie-vs-orca.md)
- [Junie CLI vs Paseo](https://www.anchorterminal.com/compare/junie-vs-paseo.md)
- [Junie CLI vs Prime Agent](https://www.anchorterminal.com/compare/junie-vs-prime-agent.md)
- [Junie CLI vs Qoder CLI](https://www.anchorterminal.com/compare/junie-vs-qoder-cli.md)
- [Junie CLI vs Qwen Code](https://www.anchorterminal.com/compare/junie-vs-qwen-code.md)
- [Junie CLI vs Mirror CLI](https://www.anchorterminal.com/compare/junie-vs-reflection-mirror.md)
- [Junie CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/junie-vs-rovo-dev-cli.md)
- [Junie CLI vs Sculptor](https://www.anchorterminal.com/compare/junie-vs-sculptor.md)
- [Junie CLI vs T3 Code](https://www.anchorterminal.com/compare/junie-vs-t3-code.md)
- [Junie CLI vs Traycer](https://www.anchorterminal.com/compare/junie-vs-traycer.md)
- [Junie CLI vs Unstoppable](https://www.anchorterminal.com/compare/junie-vs-unstoppable.md)
- [Junie CLI vs Verdent](https://www.anchorterminal.com/compare/junie-vs-verdent.md)
- [Junie CLI vs Vibe-Trading](https://www.anchorterminal.com/compare/junie-vs-vibe-trading.md)
- [Junie CLI vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/junie-vs-warp.md)
- [Agent Relay vs Friday](https://www.anchorterminal.com/compare/agent-relay-vs-friday-work.md)
- [Agent Relay vs Junie CLI](https://www.anchorterminal.com/compare/agent-relay-vs-junie.md)
- [Clawboo vs Friday](https://www.anchorterminal.com/compare/clawboo-vs-friday-work.md)
- [Clawboo vs Junie CLI](https://www.anchorterminal.com/compare/clawboo-vs-junie.md)
- [CLI Manager vs Friday](https://www.anchorterminal.com/compare/cli-manager-vs-friday-work.md)
- [CLI Manager vs Junie CLI](https://www.anchorterminal.com/compare/cli-manager-vs-junie.md)
- [Friday vs Gemini CLI](https://www.anchorterminal.com/compare/friday-work-vs-gemini-cli.md)
- [Friday vs GitHub Copilot CLI](https://www.anchorterminal.com/compare/friday-work-vs-github-copilot-cli.md)
- [Friday vs goose](https://www.anchorterminal.com/compare/friday-work-vs-goose.md)
- [Friday vs Harness](https://www.anchorterminal.com/compare/friday-work-vs-harness-autonomous.md)
- [Friday vs HarnessRouter](https://www.anchorterminal.com/compare/friday-work-vs-harnessrouter.md)
- [Friday vs herdr](https://www.anchorterminal.com/compare/friday-work-vs-herdr.md)
- [Friday vs Jules](https://www.anchorterminal.com/compare/friday-work-vs-jules.md)
- [Friday vs Kilo Code CLI](https://www.anchorterminal.com/compare/friday-work-vs-kilo-code-cli.md)
- [Friday vs Kimi Code CLI](https://www.anchorterminal.com/compare/friday-work-vs-kimi-code-cli.md)
- [Friday vs Kiro CLI](https://www.anchorterminal.com/compare/friday-work-vs-kiro-cli.md)
- [Friday vs Letta](https://www.anchorterminal.com/compare/friday-work-vs-letta.md)
- [Friday vs MiniMax Code](https://www.anchorterminal.com/compare/friday-work-vs-minimax-code.md)
- [Friday vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/friday-work-vs-mistral-vibe-cli.md)
- [Friday vs Muse Code](https://www.anchorterminal.com/compare/friday-work-vs-muse-code.md)
- [Friday vs OpenCode](https://www.anchorterminal.com/compare/friday-work-vs-opencode.md)
- [Friday vs OpenHands](https://www.anchorterminal.com/compare/friday-work-vs-openhands.md)
- [Friday vs OpenMausBot](https://www.anchorterminal.com/compare/friday-work-vs-openmausbot.md)
- [Friday vs Orca](https://www.anchorterminal.com/compare/friday-work-vs-orca.md)
- [Friday vs Paperclip](https://www.anchorterminal.com/compare/friday-work-vs-paperclip.md)
- [Friday vs Parallax](https://www.anchorterminal.com/compare/friday-work-vs-parallax-agents.md)
- [Friday vs Paseo](https://www.anchorterminal.com/compare/friday-work-vs-paseo.md)
- [Friday vs Prime Agent](https://www.anchorterminal.com/compare/friday-work-vs-prime-agent.md)
- [Friday vs Qoder CLI](https://www.anchorterminal.com/compare/friday-work-vs-qoder-cli.md)
- [Friday vs Qwen Code](https://www.anchorterminal.com/compare/friday-work-vs-qwen-code.md)
- [Friday vs Mirror CLI](https://www.anchorterminal.com/compare/friday-work-vs-reflection-mirror.md)
- [Friday vs Rovo Dev CLI](https://www.anchorterminal.com/compare/friday-work-vs-rovo-dev-cli.md)
- [Friday vs Sculptor](https://www.anchorterminal.com/compare/friday-work-vs-sculptor.md)
- [Friday vs T3 Code](https://www.anchorterminal.com/compare/friday-work-vs-t3-code.md)
- [Friday vs Traycer](https://www.anchorterminal.com/compare/friday-work-vs-traycer.md)
- [Friday vs Unstoppable](https://www.anchorterminal.com/compare/friday-work-vs-unstoppable.md)
- [Friday vs Verdent](https://www.anchorterminal.com/compare/friday-work-vs-verdent.md)
- [Friday vs Vibe-Trading](https://www.anchorterminal.com/compare/friday-work-vs-vibe-trading.md)
- [Friday vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/friday-work-vs-warp.md)
- [Harness vs Junie CLI](https://www.anchorterminal.com/compare/harness-autonomous-vs-junie.md)
- [herdr vs Junie CLI](https://www.anchorterminal.com/compare/herdr-vs-junie.md)
- [Junie CLI vs Paperclip](https://www.anchorterminal.com/compare/junie-vs-paperclip.md)
- [Junie CLI vs Parallax](https://www.anchorterminal.com/compare/junie-vs-parallax-agents.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
