Junie CLI Now Connects to Your JetBrains IDE
Until now, Junie CLI has worked like any other standalone agent. It was powerful, but disconnected from the workflows you set up for your specific projects. That changes today.
Junie CLI can now connect to your running JetBrains IDE and use its full code intelligence, including the indexing, semantic analysis, and tooling you already rely on. The agent works with your IDE the same way you do. It sees what you see, knows what you’ve been working on, and uses the same build and test configurations you’ve already set up.
No manual setup is required – Junie CLI detects your running IDE automatically. If you have a JetBrains AI subscription, everything works out of the box.
What Junie can do with your IDE
Most AI coding agents operate in isolation. They read your files, guess at your project structure, and and attempt to run builds or tests without full context. This can work for simple projects, but it falls apart in real-world codebases, such as monorepos with complex build configurations, projects with hundreds of modules, or test setups that took your team weeks to get right.
Junie doesn’t guess. It asks your IDE, which gives it the power to:
Understand your context
Junie sees what you’re working on right now – which file is open, what code you’ve selected, and which builds and tests you’ve run recently. Instead of scanning your entire repository to understand what’s relevant, it starts with the same context you have.
Run tests without guessing
On a monorepo or any project with a non-trivial test setup, Junie uses the IDE’s pre-configured test runners – no guessing at commands and no broken configurations.
Refactor with precision
When Junie renames a symbol, it uses the IDE’s semantic index to find every usage – searching across files, respecting scope, and handling overloads and variables with the same name that appear in different contexts. This is the kind of refactoring that text-based search gets wrong.
Build and debug complex projects
Junie runs builds and tests using your existing IDE configurations.
Custom build commands, non-obvious test runners, cross-compilation targets – if your IDE understands them, Junie does too.
Use semantic code navigation
From the IDE’s index, Junie accesses the project structure without reading files line by line. Its synonym-aware search finds “variants” when you search for “options”. It navigates code the way you would, not the way grep does.
Installation
Junie CLI’s IDE integration works in all JetBrains IDEs. Support for Android Studio is coming soon.
Make sure your JetBrains IDE is running, then launch Junie CLI in your project directory. It will automatically detect the IDE and prompt you to install the integration plugin. One click, and you’re connected.
If you’re a JetBrains AI subscriber, authentication is automatic, while Bring Your Own Key (for Anthropic, OpenAI, etc.) is also fully supported.
What’s next
This integration is currently in Beta. We’re actively expanding the capabilities Junie can access through your IDE, and your feedback will directly shape what comes next.
Try it out, and let us know what you think.
