Air, Junie, or plain IntelliJ: untangling JetBrains' three AI things

A teammate asked me last week what actually separates Junie from Air, and I gave an answer so muddled that I went home and wrote this to get it straight in my own head. JetBrains now ships three AI products with overlapping territory and names that help nobody, so here's the layout the way I finally understood it.

• AI Assistant is the chat-and-completion layer baked into IntelliJ: inline suggestions, a chat panel, the stuff you'd recognize from any modern editor.
• Junie is the agent — it takes a task and executes across your project, and it runs either inside IntelliJ or as a standalone Junie CLI.
• Air is the new standalone environment built around the agent, where Junie is only one of several agents you can point at a task.

the mental model that finally stuck

What clicked for me was seeing these as a ladder of autonomy. AI Assistant answers questions and finishes lines while you drive. Junie takes the wheel for a whole task while you stay in the car. Air is the car rebuilt on the assumption that the agent is usually driving and you're the one reviewing the route.

Same company. Three rungs, one ladder.

AI Assistant helps you type; Junie does the task; Air is the room built for an agent doing the task.

where each one actually fits

For daily work in a codebase I know cold, I still live in IntelliJ with AI Assistant and Junie a keystroke away, because the muscle memory is worth more to me than the novelty. Junie inside IntelliJ is my default for anything agentic I want to watch closely, and I put it up against the terminal-based tools in Junie versus the terminal crowd if you want that fight in detail.

Air earns its keep when the work is naturally parallel or naturally hands-off: three tasks running in isolated workspaces while I review, rather than one agent I'm babysitting in my editor. If your day is mostly deep, single-threaded surgery, Air is overkill and IntelliJ plus Junie is the better seat.

the mistake I made recommending it

I told a junior engineer to start in Air because it was the shiny new thing. Wrong call. He was two weeks into the codebase and didn't yet have the IntelliJ instincts to sanity-check what an agent handed him, so an agent-first environment just let him ship confident nonsense faster. He needed the slower, more legible loop of IntelliJ first. Air rewards people who already know what a good diff looks like; give it to someone still building that judgment and you've handed them a quicker way to be wrong.

the overlap nobody has resolved

The uncomfortable bit is that these three genuinely overlap, and JetBrains hasn't drawn a clean line between them yet. Some days I could do the same task in any of the three and I pick on instinct rather than principle. That's a preview-era smell, and I expect the edges to sharpen over the next few releases. For now the Air first look carries my full take on the environment itself; this piece is only the map.

So: AI Assistant if you want a smarter editor. Junie if you want an agent you can watch. Air if you want a place designed for agents you review instead of watch. Pick by how much of the driving you're willing to hand over, not by which logo shipped most recently.