What changed
JetBrains' 2026.3 IDE line bundles Air in IDEs, previously a separately installed plugin on 2026.2. Air detects locally installed coding agents such as Codex or Junie and can install compatible agents from an ACP registry. It offers agent-session management, presets, parallel runs, change review and IDE tooling while using existing agent authorisation or provider accounts. Air is a separate plugin/workspace, not a replacement for JetBrains AI Assistant or an AI model service.
Why it matters
Developers using several coding agents can coordinate work and review diffs without changing IDEs or buying an additional JetBrains AI subscription. Agent compatibility, subscription billing, data processing and enterprise policy are still provider-dependent. In particular, a Claude subscription does not authenticate Claude Agent in Air's chat surface: JetBrains documents a terminal-surface route for Claude Code subscription use, while chat requires JetBrains AI or Anthropic API-key billing.
What the bundled workspace does
Air in IDEs can discover agents already installed locally, use ACP-compatible agents from a registry, start and monitor sessions, and offer structured chat or agent terminal surfaces. Sessions can run in parallel; users can save presets pairing an agent, model and operation mode. Generated changes can be reviewed using the IDE's diff, debugger, refactoring and version-control tools. JetBrains says the plugin is bundled starting with IDE version 2026.3, with no separate Air licence.
Not a new model or a replacement for AI Assistant
Air is a workspace for running third-party or JetBrains agents, not a model endpoint. AI Assistant continues as a distinct supported plugin with inline completion, chat and code insight. JetBrains describes Air as an experiment in agentic development, so organisations should test workflow and stability before standardising on it.
Provider subscriptions and data handling
Air may use an existing installed agent's authorisation, JetBrains AI, or a configured third-party provider. JetBrains states that when using a third-party subscription, code is sent directly to that provider rather than via JetBrains; provider terms govern handling. JetBrains' documentation explicitly distinguishes Claude Code in a terminal using a Claude subscription from Claude Agent in chat, which needs a different billing route. Cost and model availability therefore cannot be assumed from the fact that Air itself has no separate licence.
Enterprise controls and practical rollout
JetBrains Console and IDE Services can restrict approved agents, providers, models and MCP servers, with centrally enforced settings in managed environments. Teams should establish which agents may execute commands, review diffs before merging, test the chosen authorisation flow, and verify whether their policy prevents personal credentials from bypassing organisation rules. Migration of earlier agent chat history should not be assumed.