GILD verdict
Choose Junie for JetBrains IDEs, where its agent uses the IDE itself with models from several providers.
It runs on JetBrains licenses. Choose Claude Code if Anthropic's models cover the work and engineers work across the terminal, editors, the desktop app, and the web. A JetBrains shop can also run Anthropic's agent as Claude Agent in AI Chat on JetBrains AI Credits. Pilot both on the same repositories and compare accepted, reviewed changes and spend per engineer.
Junie goes deeper into the IDE, and Claude Code reaches more places; both now run inside JetBrains IDEs. Junie is built into the IDE's AI Chat and works through the IDE's own index, inspections, test runners, and debugger. Claude Code's JetBrains plugin runs the claude CLI in the IDE terminal and opens its diffs in the IDE.
Choosing between Junie and Claude Code
Choose Junie if
- Engineers work in JetBrains IDEs and you want the agent to search through the IDE index and drive the IDE debugger.
- You want models from several providers per task, plus your own keys, a free tier, or a local model on a Mac.
- You want agent spend and access governed in JetBrains Central, with a shared credit pool and per-user monthly limits.
Choose Claude Code if
- Engineers want Anthropic's agent as their main tool across the terminal, editors, the desktop app, and the web.
- You want agent usage to share plan limits with Claude chat on a Team seat at US$25 per month, or US$20 billed annually.
- You want a classifier-reviewed auto mode, or OS-level sandboxing of agent commands, in production builds today.
Side by side
| Dimension | Junie | Claude Code |
|---|---|---|
| Where it runs | JetBrains IDEs (AI Chat and the Junie tool window), Junie CLI, JetBrains Air, ACP editors, GitHub Actions, and GitLab CI/CD | Terminal CLI, VS Code and JetBrains extensions, desktop app, web, mobile, Slack, GitHub Actions, and GitLab CI/CD |
| Inside a JetBrains IDE | Uses the IDE's semantic index, run configurations, test runners, and debugger; Debug mode drives a live debug session | Plugin runs the claude CLI in the IDE terminal, shows diffs in the IDE diff viewer, and reads inspection diagnostics when asked |
| Individual priceList prices in US dollars. Included usage differs by plan and is not directly comparable. | AI Pro: US$10 per month with 10 AI Credits; AI Ultimate: US$30 per month with 35 | Included in Claude Pro: US$20 per month, or US$17 per month billed annually; Max from US$100 per month |
| Team price | Organization AI Pro US$20 or AI Ultimate US$60 per user per month; JetBrains Central Business adds US$20 per AI seat for governance | Claude Team: US$25 per seat per month, or US$20 billed annually; Enterprise US$20 per seat billed annually, plus usage at API rates |
| How usage is metered | AI Credits worth US$1 each, charged in your local currency; own-key requests bill at the provider | Plan usage limits shared with Claude chat, or API usage; Anthropic reports about US$13 per developer per active day across enterprise deployments |
| Models | Anthropic, OpenAI, Google, and xAI models through JetBrains AI or your own keys, Junie Lite on Qwen 3.6 27B, and local models | Anthropic's Claude models |
| Permissions | Asks before sensitive actions; Action Allowlist; Brave mode Off, Auto, or On; no OS sandbox in release builds | Auto mode, where a classifier blocks unsafe actions, or manual mode that starts read-only; optional sandboxed bash with filesystem and network isolation |
| Project instructions | .junie/AGENTS.md, or the root AGENTS.md with .junie/rules; legacy .junie/guidelines.md still loads | CLAUDE.md; reads AGENTS.md only when no CLAUDE.md is present |
| Admin controls | JetBrains Central: AI access, a shared credit pool, and per-user monthly limits; AI policies for agents, MCP servers, and BYOK providers on Business | Spend limits and spend reports in admin settings on Team and Enterprise |
What practitioners report, side by side
Each product's figures come from its own practitioners, for the group you pick.
Overall signal
All practitioners rate Claude Code +45, 17 points above Junie at +28. Most of the gap is in praise, with 64 of Claude Code's 110 sources positive against 38 of Junie's 80. Claude Code has 13 negative and Junie 16.
The score counts the authors from all practitioners that take a side, one vote each with their latest view, and is how far positive votes lead negative ones, per 100 votes, so Junie's +28 rests on votes split 36 positive, 23 mixed and 15 negative and Claude Code's +45 on 60, 32 and 13.
A lead of a fifth of the votes reads positive and a lead of half strong positive, with the same lines below zero. The dots show each source, positive, mixed, negative. Use a task pilot to measure accepted work and review time.
Footprint on the Agentic Software Development stack
They differ on one of 12 layers. On Tool execution, Junie supports it and Claude Code is core. Coverage is each product's placement on this stack, as its product page shows it. Core is a job the product owns; Supports and Touches are jobs it helps with. Coverage says nothing about how well a product does them.
| Layer | Junie | Claude Code |
|---|---|---|
| Build | ||
| Tool execution | Supports | Core |
The 11 layers where they match
| Layer | Junie | Claude Code |
|---|---|---|
| Plan | ||
| Work planning | Supports | Supports |
| Build | ||
| Codebase context | Core | Core |
| Coding | Core | Core |
| Agent runtime | Core | Core |
| Validate | ||
| Debugging | Supports | Supports |
| Testing | Supports | Supports |
| Code review | Supports | Supports |
| Application security | Touches | Touches |
| Ship | ||
| Source control | Touches | Touches |
| CI/CD | Touches | Touches |
| Operate | ||
| Observability | Touches | Touches |
What practitioners praise
Among all practitioners, Claude Code alone has six praise themes that reach 5 sources from 3 authors. Multi-Step Execution and Developer Experience lead, at 17 of 19 and 15 of 21. Both carry Codebase Understanding. It is praised in 14 of the 19 Junie sources that discuss it, against 16 of 16 for Claude Code. Junie alone has four praise themes that reach 5 sources from 3 authors. Code Quality and IDE Integration lead, at 17 of 30 and 11 of 15.
| Praised for | Junie | Claude Code |
|---|---|---|
| Codebase Understanding | 14 of 19 | 16 of 16 |
| Code Quality | 17 of 30 | Not a theme in its sources |
| IDE Integration | 11 of 15 | Not a theme in its sources |
| Test Writing | 10 of 14 | Not a theme in its sources |
| Planning & Control | 8 of 16 | Not a theme in its sources |
| Multi-Step Execution | Not a theme in its sources | 17 of 19 |
| Developer Experience | Not a theme in its sources | 15 of 21 |
| Large Refactors | Not a theme in its sources | 9 of 10 |
| Value for Money | 4 of 4 so far | 9 of 14 |
| Enterprise Administration | Not a theme in its sources | 5 of 8 |
| Stability | Not a theme in its sources | 1 of 6 |
Each count is the sources that praise a theme, or raise it as a concern, out of those that discuss it. A row pairs the two products when both carry a theme under the same or an equivalent name.
A count ending in "so far" has under 5 sources from 3 authors among all practitioners. "Not a theme in its sources" means GILD found no theme of that name in that product's sources.
What practitioners raise as concerns
Claude Code's sources raise Credits & Cost more often than Junie's. It is raised in 7 of the 22 Junie sources that discuss it, against 19 of 31 for Claude Code. Speed and Stability reach 5 sources from 3 authors only for Junie, at 13 of 19 and 10 of 10. Claude Code needs a pilot on the same repository tasks before you choose on either. Claude Code alone has four concern themes that reach 5 sources from 3 authors. Context Management and Permissions & Safety lead, at 17 of 28 and 10 of 20.
| Raised as a concern | Junie | Claude Code |
|---|---|---|
| Inconsistent Results | 17 of 20 | 16 of 18 |
| Credits & Cost | 7 of 22 | 19 of 31 |
| Needs Close Steering | 6 of 6 | 7 of 9 |
| Requires Strong Review | 5 of 12 | 26 of 40 |
| Speed | 13 of 19 | Not a theme in its sources |
| Stability | 10 of 10 | Not a theme in its sources |
| Context Management | Not a theme in its sources | 17 of 28 |
| Permissions & Safety | Not a theme in its sources | 10 of 20 |
| Reliability | Not a theme in its sources | 9 of 10 |
| Day-to-Day Friction | Not a theme in its sources | 5 of 6 |
16 sources
- JetBrains AI docs: Plans and usage
- JetBrains AI docs: Junie by JetBrains in AI Chat
- JetBrains AI docs: Agents
- Junie docs: Integration with JetBrains IDEs
- Junie docs: Junie CLI quickstart
- Junie docs: Model selection
- Junie docs: Action Allowlist in Junie CLI
- Junie docs: Guidelines and memory
- JetBrains Central Console docs: Plans and pricing
- JetBrains Central Console docs: AI credit consumption
- Claude pricing
- Claude Code docs: Costs
- Claude Code docs: Platforms
- Claude Code docs: Security
- Claude Code docs: Memory
- Claude Code docs: JetBrains IDEs