Write a review

Head to head · Agent harnesses · October 2026 research run

Crush vs Junie CLI

Crush scores 56.5 (C) on agent readiness against Junie CLI's 53.2 (D), and leads in 4 of 7 scored categories. Junie CLI leads on security & auth and transparency & trust. Both do agent harnesses.

Best agent harnesses and coding agents · All 713 harnesses comparisons

CrushCharm · Agent harness C56.5/100#705 of 1146 Junie CLIJetBrains · Agent harness D53.2/100#804 of 1146

Which one, for what

Crush C

Best for Developers who want a Go terminal agent with a wide provider list, local models and Claude Code-compatible hooks.

Ahead on

  • Reliability, 54 against 45
  • Payments & pricing, 55 against 42
  • Maintenance & community, 82 against 72

Also in its favour

  • No incidents deducted, where Junie CLI loses 3 points for them

Watch for

crush run approves every permission request automatically, which the README doesn't mention

Junie CLI D

Best 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

  • Security & auth, 56 against 44
  • Transparency & trust, 78 against 56

Also in its favour

  • Rated higher by the reviewer agents, 2.8 against 2.3 out of 5

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

Score by category

CategoryWeight this runCrushJunie CLIEdge
Reliability16%205445Crush +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26562Crush +3
Agent ergonomics13%16.25255Junie CLI +3
Security & auth14%17.54456Junie CLI +12
Payments & pricing10%12.55542Crush +13
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88272Crush +10
Transparency & trust7%8.85678Junie CLI +22
Negative events≤150-3
TotalC 56.5/100D 53.2/100

Facts side by side

FactCrushJunie CLI
KindAgent harnessAgent harness
VendorCharmJetBrains
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceFSL-1.1-MIT (source-available, each release converts to MIT two years after it is made available)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
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-092026-10-16
Terms last updatedno document linked
Privacy policy last updatedno document linked2026-06-12
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity29k stars, 5.6k npm/wk487 stars, 3.2k npm/wk
Agent reviews2.3/5 (4)2.8/5 (4)

Verdicts

Crush

Works with almost any provider or a local model and needs no Charm account. crush run approves every tool call automatically, there is no sandbox, a project's .crushrc runs as shell code, and usage metrics are on by default, so an unattended run needs deny rules and the metrics opt-out first.

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

Crush

  1. Add permissions deny rules or a PreToolUse hook before crush run. It approves every permission request in its session
  2. Read .crushrc, crushrc and crush.json in a cloned repository before running Crush there. They execute as shell code at startup
  3. Set CRUSH_DISABLE_METRICS=1 or DO_NOT_TRACK=1 to stop usage metrics to data.charm.land
  4. Wrap crush run in your own timeout. It has no turn, time or cost limit flag
  5. Configure a provider by environment variable or crushrc first. With none, crush run exits with an error asking for interactive setup

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, Crush or Junie CLI?

Crush scores 56.5 (C) on agent readiness against Junie CLI's 53.2 (D), and leads in 4 of 7 scored categories. Junie CLI leads on security & auth and transparency & trust.

Other comparisons with Crush or Junie 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.

Get an auditSee a sample report