IntelliJ IDEA 2026.3 Puts AI Agents Center Stage — But Developers May Prefer to Disable Air
IntelliJ IDEA 2026.3 introduces an Agent-centric UI with Air, native Git Worktree support, improved debugging with persistent logpoints, and a libghostty-based terminal, yet the author prefers the external Orca environment and shows how to disable Air for a traditional coding experience.
Upgrading to IntelliJ IDEA 2026.3 marks a watershed moment. For years IDEA evolved incrementally — adding language features, framework support, and fixing performance issues — while developers simply wanted faster startup, lower memory use, and smoother Java coding. Version 2026.3 visibly pivots: from the splash screen to the main project window, JetBrains places its Agent (branded as Air) front and center, signaling a shift from a tool that helps you write code to a place where an Agent writes code for you.
01 Home, Worktree, and Air
The splash screen now carries a “powered with air” tagline.
The familiar Welcome screen is replaced by a new Home view that lets you edit files, open terminals, and run Git operations without fully loading a project.
Git Worktree receives first-class support. Worktree — a long-standing Git feature that checks out multiple branches into separate working directories — maps naturally to parallel Agent workflows. Multiple Agents working in the same directory would read each other’s half-written files and produce tangled diffs; isolating each Agent in its own Worktree keeps changes cleanly separated, and a misbehaving Agent’s tree can be discarded without touching the main workspace. Air sessions can also run inside temporary Worktrees.
Inside a project, the center of the window is now occupied by Air’s task input box, flanked by the project tree and Maven toolbar.
Air is positioned as an end-to-end Agent environment: it offers session entry points, supports multiple ACP-compatible Agents, allows custom API keys or existing model subscriptions, and grants Junie Lite quotas via JetBrains Account login. The goal is to keep you in the main window from first prompt to final merge.
02 Running and Debugging Improvements
Beyond the Agent hype, 2026.3 delivers practical debugging gains. The new ij-debugger skill lets an Agent read run/debug configurations, set non-blocking logpoints, and collect diagnostic data. Crucially, logpoints and historical process output persist in the panel after the debug session ends, unlike the previous behavior where stopping the process erased everything.
The built-in terminal has been reimplemented on top of libghostty, yielding noticeably smoother rendering and lower input latency. Terminal tabs can now be dragged into the main editor area, sitting side-by-side with code files. Remote development gains system-level OpenSSH support, and Linux remote environments start with a lightweight transitional UI that loads basic interaction first while the full service spins up in the background.
Other scattered updates include Java and Kotlin extensions for Cursor and VS Code, early Java 28 EA syntax support, cross-database joint queries, and a batch of stability fixes (UI freezes, idle CPU spikes, incomplete memory release after closing large projects). For Java developers, these stability improvements outweigh a persistent chat dialog.
03 JetBrains’ Agent Playbook Feels Behind
The author’s lack of enthusiasm for the central Air pane isn’t anti-Agent sentiment — it’s that a more comfortable Agent workflow already exists elsewhere. Daily tasks like requirement drafting, code structure reasoning, and multi-file refactoring have migrated to Orca.
Orca’s terminal-centric layout lists projects and task workspaces on the left, the current session with terminal output in the middle, and a full file tree on the right. The Agent runs commands, executes automated tests, and inspects changed-file context directly in the terminal. Interaction is clean and direct, and the environment carries none of the full IDE runtime overhead.
04 Disabling Air to Reclaim a Traditional IDE
Since the author doesn’t need two Agent managers, the immediate step after upgrading is to turn Air off. In Preferences → Plugins → Installed, find Air (bundled with 2026.3). No Uninstall button is provided, but the dropdown menu offers Disable. After disabling and restarting, the plugin shows an Enable button and the top-right master switch grays out.
Air and the pre-existing AI Assistant are separate components: AI Assistant focuses on code completion and inline interactions, while Air is the full-task Agent shell. Disabling Air only removes the central Agent input UI and multi-Agent session management; the classic coding environment remains intact.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
