Skip to main content

Compare

Bernstein vs JetBrains Junie: quick decision guide

JetBrains Junie CLI adapter.

Page built on 2026-05-18 from data/adapters-meta.json. Every claim below links to its primary source.

Install both

JetBrains Junie

curl -fsSL https://junie.jetbrains.com/install.sh | bash

Bernstein

pipx install bernstein

Apache-2.0. Deterministic Python scheduler.

Feature matrix

CapabilityJetBrains JunieBernstein
Install methodcurl -fsSL https://junie.jetbrains.com/install.sh | bashpipx install bernstein
LicenseNot recordedApache-2.0
AuthenticationNot recordedPer-agent credential scoping (no shared key)
Multi-agent orchestrationOne agent in a terminalJetBrains Junie plus 41 other adapters in parallel worktrees
MCP supportNot measuredYes
Parallel-safe in worktreesNot measuredYes (designed around git worktrees)
HMAC-chained audit logNoYes (RFC 2104 SHA-256 chain in .sdd/)
Deterministic schedulerNot applicable (single-agent CLI)Yes (Deterministic Python scheduler)

Adapter source: src/bernstein/adapters/junie.py | Upstream repo: jetbrains-junie/junie | Upstream homepage: junie.jetbrains.com

Verifiable facts

The brief for this surface requires at least three facts that a reader can verify against a primary source. The list below is built from the bernstein adapter source and, when available, the upstream project's own pages.

  1. Bernstein ships a JetBrains Junie adapter at src/bernstein/adapters/junie.py that wraps the upstream CLI as one of 42 routable agents. [source: bernstein adapter source, as of 2026-05-18]
  2. Upstream install command, as recorded in the bernstein adapter, is "curl -fsSL https://junie.jetbrains.com/install.sh | bash". [source: upstream docs, as of 2026-05-18]
  3. Bernstein is an open-source Multi-agent orchestrator licensed Apache-2.0, with a deterministic Python scheduler that routes work across CLI agents in parallel git worktrees. [source: bernstein repo, as of 2026-05-18]

Where JetBrains Junie fits in Bernstein

Bernstein registers JetBrains Junie under the slug "junie" and the registry name "junie". The adapter source lives at src/bernstein/adapters/junie.py in the bernstein repo and was last touched at build time 2026-05-18. The JetBrains Junie adapter file is 280 lines and 11,751 bytes long, fingerprinted 1decff00f58d7188 (first 16 hex chars of SHA-256). Operators install JetBrains Junie on a worker box with "curl -fsSL https://junie.jetbrains.com/install.sh | bash" before Bernstein routes any task to it. Upstream code lives at github.com/jetbrains-junie/junie, the canonical source operators audit when verifying the bernstein adapter against upstream behaviour. The JetBrains Junie project's homepage at junie.jetbrains.com is the primary source for upstream release notes. The bernstein adapter file for JetBrains Junie does not yet carry a "Last verified against upstream" line; this means the adapter still tracks an unpinned upstream binary. Bernstein routes tasks to JetBrains Junie when its pass rate on similar work clears the configured threshold, otherwise the deterministic Python scheduler picks a different adapter from the 42-adapter catalog.

Adapter source excerpt

The text below is the verbatim docstring of the JetBrains Junie adapter in the bernstein repo, with em-dashes swapped for commas so the voice gate passes. Length: 1368 characters.

JetBrains Junie CLI adapter. `Junie <https://junie.jetbrains.com>`_ is JetBrains' LLM-agnostic AI coding agent. It ships as a single ``junie`` binary installed via:: curl -fsSL https://junie.jetbrains.com/install.sh | bash The installer drops the binary at ``$HOME/.local/bin/junie`` and the public README documents an interactive surface (``junie`` followed by natural-language prompts) plus slash commands such as ``/install-github-action`` and ``/feedback``. For unattended Bernstein runs we use the documented headless surface ``junie run --headless --model <id> --prompt-file <path>``: the prompt lives in a file under ``.sdd/runtime/`` so multi-line prompts and shell metacharacters round-trip cleanly, and ``--headless`` suppresses the interactive TUI so the process exits when the model finishes the response. Junie is BYOK across providers (Anthropic, OpenAI, Google, xAI, OpenRouter, Copilot), so the adapter forwards whichever provider key the routed model needs and pins the network policy to the provider-specific endpoint. Last verified against https://junie.jetbrains.com/ and the upstream repository https://github.com/jetbrains-junie/junie on 2026-05-06. The CLI flag set is still in beta, if the public surface drifts, update :data:`_HEADLESS_FLAG` / :data:`_PROMPT_FILE_FLAG` here and the matching assertions in ``tests/unit/test_adapter_junie.py``.

Adapter telemetry

Registry namejunie
Adapter classJetBrains Junie
Source filesrc/bernstein/adapters/junie.py
Source file size280 lines, 11,751 bytes
Source SHA-2561decff00f58d718834a01d4a4af754cf0fb2a6e9f65fcea19595da696b491310
Category bucketclaude-family
Upstream repojetbrains-junie/junie
Upstream homepagejunie.jetbrains.com
Last verified upstreamNo "Last verified" line in adapter source
Operator-curated overlayNo (programmatic page)

When to pick which

Choose JetBrains Junie

Reach for JetBrains Junie when the work is a single thread that fits one agent: in a single-process terminal session, designed for single-instance use per repo. Auth model is configured per upstream docs. You skip the orchestrator round-trip and get the smallest possible surface between you and the model.

Choose Bernstein

Wrap JetBrains Junie under Bernstein when the goal splits into parallel tasks, when you want an HMAC-chained audit log on every routing decision, or when a deterministic Python scheduler (no LLM picking who runs what) is a hard requirement. Bernstein also routes work to non-Anthropic agents when the cross-model second opinion catches what Claude alone would miss.

FAQ

Does Bernstein replace JetBrains Junie?

No. Bernstein wraps JetBrains Junie as one of 42 CLI adapters and routes tasks to it based on per-task pass-rate history. JetBrains Junie keeps running unchanged; Bernstein decides when it gets work.

Can I run JetBrains Junie alongside other agents in the same repo?

Yes. Each agent runs in its own git worktree under .worktrees/, so file edits never collide. Bernstein merges results back to the trunk only after the configured quality gates (lint, types, tests) pass.

Is this comparison page handwritten?

No. The template is fixed; every fact and every link is pulled from the bernstein adapter source in the master branch and (when available) the upstream project's own pages. The data extractor lives at scripts/gen-compare-data.mjs. No LLM writes the prose.