Junie Merges Into JetBrains AI Chat: One Interface to Rule Them All

TL;DR

• JetBrains is merging Junie into the main AI chat interface, ending the two-UI split
• Junie is now available as a selectable agent in AI chat (Beta), with the standalone plugin staying active during transition
• Settings remain separate for now — changes in AI chat won't affect Junie plugin, but Junie updates apply to both
• If you use Junie daily in JetBrains IDEs, this matters — your workflow is about to consolidate

The Big Picture

JetBrains shipped two separate chat interfaces for AI assistance: one for Junie, their coding agent, and one for general AI chat. It was confusing. Developers had to context-switch between UIs depending on whether they wanted agentic coding help or quick AI queries. Now JetBrains is fixing it.

Starting today, Junie is available directly inside the JetBrains AI chat as a selectable agent. You open one interface, pick Junie from a dropdown, and go. The standalone Junie plugin isn't disappearing immediately — this is a transition period — but the writing is on the wall. JetBrains plans to fully deprecate the separate Junie UI and consolidate everything into a single AI chat experience.

This isn't just UI cleanup. It's JetBrains acknowledging that the industry has settled on clearer UX patterns for coding agents. When Junie first launched, nobody knew how agents should integrate into IDEs. JetBrains ran parallel experiments. Now they're converging on one answer: agents live inside chat, not in separate windows.

For developers already using Junie's LLM-agnostic CLI, this change signals JetBrains' commitment to making Junie a core part of their AI stack, not a side project.

How It Works

The integration is straightforward. Open the AI chat in any JetBrains IDE. You'll see an agent selector — a dropdown that now includes Junie alongside other AI options. Select Junie, run a prompt, and the agent downloads and installs automatically if you don't have it yet.

Under the hood, this Beta version of Junie in AI chat is functionally equivalent to the standalone plugin. Same capabilities, same model support, same agentic behavior. JetBrains claims the user experience is "on par" with the plugin version, though they're promising more improvements as the integration matures.

The tricky part is settings. Right now, Junie and AI chat maintain separate configurations. If you tweak something in the AI chat settings, it won't affect Junie. But if you change Junie settings, those updates apply to both the standalone plugin and the chat-integrated version. It's asymmetric, and JetBrains knows it. They're planning to merge settings fully, but for now, you're managing two config surfaces.

Your existing Junie setup — active models, Action Allowlist, MCP server configurations — carries over. JetBrains is retaining those settings and gradually merging them into the unified interface. The standalone plugin stays available during this transition, so you can switch back if the chat version doesn't work for you yet.

This is a Beta rollout, which means JetBrains is testing the waters. They're watching for edge cases where the chat integration breaks workflows that worked fine in the standalone plugin. If you hit friction, they want to hear about it before they kill the old UI entirely.

What This Changes For Developers

If you're a Junie user, your workflow just got simpler — eventually. Right now, you're in a transition period where both UIs exist. You can keep using the standalone plugin, or you can try the chat-integrated version. Most developers will probably stick with what they know until JetBrains forces the switch.

The real benefit comes when the merge is complete. One interface means one place to configure AI settings, one place to check chat history, one place to manage context. No more "which UI do I need for this task?" decisions. You open AI chat, pick the tool (Junie or something else), and work.

For teams standardizing on JetBrains IDEs, this consolidation makes onboarding easier. New developers don't need to learn two separate AI interfaces. They learn one chat UI that handles multiple agents. That's a win for consistency.

The downside? If you've customized the standalone Junie plugin heavily, you're going to have to re-verify that those customizations work in the chat version. JetBrains says settings will migrate, but "gradually merged" is not the same as "instantly compatible." Expect some manual reconfiguration.

Try It Yourself

If you already have JetBrains AI chat installed, open it and look for the agent selector. Choose Junie, run a prompt, and the agent installs automatically. If you don't have AI chat yet, follow JetBrains' installation guide.

No code example here — this is a UI integration, not an API change. The workflow is point-and-click. If you want to test whether the chat-integrated Junie behaves identically to the plugin version, try a multi-file refactor or a complex code generation task. Those are where agentic behavior matters most.

The Bottom Line

Use the chat-integrated Junie if you want to simplify your JetBrains AI workflow and don't mind Beta quirks. Stick with the standalone plugin if you need stability and can't afford to troubleshoot settings migration right now. The real risk is waiting too long — JetBrains will deprecate the standalone UI eventually, and you'll be forced to switch anyway.

This move makes sense. Two UIs for AI assistance was always a temporary state. The industry has settled on chat-based agent interfaces, and JetBrains is following that pattern. If you're heavily invested in Junie, start testing the chat version now so you're ready when the standalone plugin goes away. If you're new to Junie, skip the plugin entirely and go straight to the chat integration.

The opportunity here is consolidation. One interface, multiple agents, cleaner workflows. The risk is that JetBrains rushes the deprecation before the chat integration is fully baked. Watch the Beta closely, file bugs when you hit them, and don't assume your settings will migrate perfectly.

Source: Junie