Junie CLI vs HagiCode: Features and Comparison

Junie CLI is JetBrains' terminal coding agent, and HagiCode is a desktop and web workbench that runs Junie as its executor. Stay with Junie alone for terminal, IDE and CI work; add HagiCode when you want parallel sessions, spec proposals and managed commits around it.

Actualizado: 16 oct 2026

Esta pagina se muestra temporalmente en inglés estadounidense mientras se prepara la version localizada.

Short answer

Junie CLI is JetBrains' agentic coding tool: you run junie in a project directory and give it tasks in a terminal UI. HagiCode is a desktop and web AI programming workbench that drives agent CLIs, Junie among them, as its executor. It does not replace Junie. Junie still does the coding, and HagiCode adds sessions, proposals and commit handling around it.

If you work in a terminal, a JetBrains IDE or CI pipelines and one task at a time is enough, Junie alone is the simpler choice. If you juggle several tasks or repositories and want each change tied to a written proposal, HagiCode is worth adding on top. HagiCode does not sell models; Junie keeps its own sign-in and billing.

Junie CLI vs HagiCode at a glance

Dimension	Junie CLI	HagiCode
What it is	JetBrains' LLM-agnostic coding agent for the terminal, IDE and CI	Workbench that runs agent CLIs, Junie included, as executors
Interface and platforms	Terminal UI on Linux, macOS and Windows; IDE plugin; GitHub Actions and GitLab CI	Desktop app (Windows, macOS, Linux), Docker Compose container, Microsoft Store edition
Pricing and licensing	Billed through a JetBrains plan (free Junie Lite model, AI Pro, AI Ultimate credits), a Junie API key or your own keys; see JetBrains' pricing page	Desktop and Container free; Store edition free with optional one-time TurboEngine purchase; model cost stays with Junie
Model and provider access	Default model, or BYOK: OpenAI, Anthropic, Google, xAI, OpenRouter, GitHub Copilot, custom endpoints (LiteLLM, Ollama, LM Studio)	Hosts no models; uses whatever Junie is signed in to; optional OmniRoute routing
Parallel work	One session per terminal or CI job; you coordinate parallel runs yourself	Several sessions at once, each a named Agent with visible status
Spec and planning workflow	Plan mode writes a design document from read-only analysis	OpenSpec proposals: propose, validate, apply, archive (3 concurrent free, 32 with TurboEngine)
Git and commit handling	/review inspects changes in a Git repository; --review for CI	AI-composed commit messages with the repository locked during the commit; Git and GitHub integration
Setup effort	One install command, then sign in	Desktop install, plus Junie installed and signed in first
Best for	Developers who want a JetBrains-backed agent in terminal, IDE or CI	People running several agent tasks or repositories with traceable specs

What Junie CLI does well

One agent across terminal, IDE and CI

Junie runs interactively in the terminal, as an IDE plugin, and headless in GitHub Actions and GitLab CI. A CI step can be as short as junie --auth="$JUNIE_API_KEY" "Fix any failing tests", or --review for a code review. You learn one tool and use it in all three places.

Billing and model choice you control

Junie signs in three ways: a JetBrains account, a Junie API key with usage-based billing, or your own keys from providers such as OpenAI, Anthropic, Google, xAI, OpenRouter and GitHub Copilot. Custom endpoints such as LiteLLM, Ollama and LM Studio also work. JetBrains states that BYOK usage is billed at provider rates with no markup, and effort levels are available for models that support them.

Graduated approval controls

Brave mode has three levels: Off asks before sensitive actions, Auto approves commands classified as safe, On runs them without asking. Sandbox mode (Early Access) wraps terminal commands in an OS-level sandbox on macOS and Linux. Plan mode produces a design document from read-only analysis, and Debug mode works with a connected JetBrains IDE.

Update channels and status

You can run another channel for a single launch, for example junie --eap or junie --nightly, without changing your installed default. JetBrains announced Junie CLI as a beta in March 2026; current docs do not state a status, so check junie.jetbrains.com before relying on it for production CI.

When to choose Junie CLI, and when to choose HagiCode

Elige Junie CLI cuando

• you work in a terminal or JetBrains IDE and one task at a time is enough;
• you want the same agent in CI, using a Junie API key with --review or a headless task;
• you prefer to manage provider keys, custom endpoints and effort directly in Junie;
• you want Junie's own three-level Brave setting and sandbox mode instead of a wrapper's switch;
• you want the fewest moving parts.

Elige HagiCode cuando

• you run several Junie tasks across repositories at once and want each as a named, trackable Agent;
• you want every change to start as a written OpenSpec proposal with validation and archive;
• you want Junie's changes committed with composed messages and tweaked in an editor inside the same window;
• you use more than one agent CLI and want a single workspace around them;
• you want a shared knowledge base (Vault) and multi-repo specs (Monospecs) around your agent.

Where HagiCode is not the right tool for Junie users

Headless CI or scripted one-shot runs: call junie directly with your API key; HagiCode is a desktop and web app.

If you only want a terminal or live in a JetBrains IDE, HagiCode is an extra layer to install and learn.

It needs Junie installed and signed in first, so setup is longer than running Junie alone.

Free editions cap concurrent proposals at 3, and teams that do not want spec discipline will find proposals overhead.

The embedded Code Server is not a replacement for a JetBrains IDE in deep manual editing.

HagiCode exposes provider, model, effort and a Brave on/off switch for Junie; Junie's three-level Brave cycling and sandbox mode are not among those settings.

Using Junie CLI together with HagiCode

HagiCode is a workbench on top of the CLI. It starts junie in ACP mode inside the repository you open, so your own Junie install and sign-in do the work. HagiCode has no Junie credential fields and adds no model billing.

Nothing is locked in: Junie stays a normal install that you can still run in any terminal.

1. Install Junie (macOS/Linux: curl -fsSL https://junie.jetbrains.com/install.sh | bash; Windows: the PowerShell installer on the Junie docs page), then run junie once and sign in.
2. Install HagiCode Desktop (Windows, macOS or Linux; free).
3. In the Agent CLI settings, choose Junie as the executor and optionally set provider, model, effort and Brave.
4. Open a repository and start a session or an OpenSpec proposal.
5. Expect Junie to run with Brave on unless you turn it off, and a changed provider or model to start a compatible new session rather than resume the old one.
6. To go back to plain Junie, run junie in the same directory; your Junie install and sign-in are untouched.

What works for Junie inside HagiCode

Parallel sessions, Agents management, OpenSpec proposals, AI commit, Code Server, Monospecs, Vault and the unified tool-call view apply to Junie sessions. OmniRoute routing is a HagiCode feature, and how far it reaches Junie depends on Junie's own provider settings.

Interactive questions are limited to Claude, Pi, OMP and Reasonix, and the agent work panel is Claude only, so neither is available with Junie.

What HagiCode adds on top of any agent

Parallel sessions and Agents management

Run several Junie sessions side by side, each with its own context, and see which Agent is running, waiting or finished. Without HagiCode that means several terminals you track yourself.

OpenSpec proposals

Each task can start as a proposal that Junie implements within agreed constraints. Plan mode gives you a design document inside one session; a proposal keeps the reasoning, discussion and code changes together and archivable across sessions.

AI commit and Code Server

HagiCode drafts the commit message from your diff and locks the repository while committing. The embedded Code Server lets you open the file Junie edited and adjust it without leaving the workbench.

Monospecs and Vault

Monospecs declares sub-repositories in .hagicode/monospecs.yaml so Junie sees the whole change surface. Vault registers reference projects and notes once and injects them into new proposals.

OmniRoute, tool-call view and usage

OmniRoute can route model traffic centrally when Junie is configured to use it. Junie's tool calls appear in the same typed view as every other agent, and the optional TokenMonitor integration shows today's tokens and cost in the status bar.

The bottom line

• Junie CLI is a capable terminal, IDE and CI agent from JetBrains; for single tasks it needs nothing else.
• HagiCode adds parallel Agents, OpenSpec proposals, AI commits and a shared knowledge base around Junie, at the cost of one more install and a 3-proposal cap on free editions.
• Pick Junie alone for CI and terminal-first work, HagiCode plus Junie for multi-task, multi-repo work with traceable specs.

Preguntas frecuentes

Is Junie CLI free?

The Junie CLI itself runs on a JetBrains subscription plan (a free Junie Lite model is included with a JetBrains account), a usage-billed Junie API key, or your own provider keys billed at provider rates. See the pricing page at junie.jetbrains.com for current plans.

How do I install Junie CLI?

On macOS or Linux run curl -fsSL https://junie.jetbrains.com/install.sh | bash, then cd into your project and run junie. Windows uses a PowerShell installer listed on the Junie docs page; Homebrew and npm (@jetbrains/junie) are alternatives in the repository README.

Can I use Junie CLI with HagiCode?

Yes. Install and sign in to Junie first, then choose Junie as the Agent CLI in HagiCode. HagiCode runs it over ACP and never asks for Junie credentials.

Does HagiCode replace Junie CLI?

No. HagiCode is a workbench around the CLI; Junie still writes the code, and you can run it directly at any time.

Is Junie CLI still in beta?

JetBrains announced Junie CLI as a beta in March 2026. The current docs do not state a status, so check junie.jetbrains.com for the latest.

Junie CLI vs HagiCode: which should I pick?

Use Junie alone for CI, terminal and IDE work on one task at a time. Add HagiCode when you run several tasks or repositories and want proposals, commits and Agents managed in one place.

Prueba HagiCode sobre el agente que ya usas

Instala HagiCode Desktop, conecta tu CLI actual y sigue trabajando como hasta ahora.

Instalar HagiCode Desktop

Más comparativas

• Claude Code vs HagiCode
• CodeBuddy CLI vs HagiCode
• Codex CLI vs HagiCode
• GitHub Copilot vs HagiCode
• DeepAgents vs HagiCode
• DeepSeek Harness (dsh) vs HagiCode
• Gemini CLI vs HagiCode
• Hermes Agent vs HagiCode
• Kimi CLI vs HagiCode
• Kiro CLI vs HagiCode
• OMP CLI vs HagiCode
• OpenCode vs HagiCode
• Pi CLI vs HagiCode
• QoderCLI vs HagiCode
• Reasonix CLI vs HagiCode