Key details

  1. Air in IDEs is bundled starting in JetBrains IDE 2026.3; it was optional in 2026.2.
  2. ACP-compatible agents and locally installed agents can share an IDE-based session workspace.
  3. Existing subscriptions may work, but authentication and charges depend on the agent and interface.
  4. Air is separate from JetBrains AI Assistant and is described as experimental.
  5. Enterprise administrators can manage approved agents, models, providers and MCP servers.

What builders should take away

  1. Test Air with the coding agents and subscriptions you already use before changing provider billing.
  2. Use session diffs and IDE review rather than accepting agent changes automatically.
  3. Check the Claude chat-versus-terminal authentication distinction if using a Claude subscription.
  4. In managed IDE fleets, validate central policy enforcement and provider data-processing terms.

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.

What to watch next

  • Plugin stability and migration of session history across IDE updates.
  • Additional ACP agents and provider authorisation options.
  • Changes to enterprise governance and agent-execution safeguards.

Still unclear

  • Independent measured productivity or reliability improvements were not established.
  • Agent feature availability varies with third-party agent versions and authorisation.
  • JetBrains describes Air as experimental, so interface and compatibility may evolve.

Sources

Direct reading behind this dossier.

3 sources
Air in IDEs overview
JetBrains primary

Current first-party workflow, subscriptions, governance, version bundling and limitations.

PhpStorm 2026.3 coverage
Laravel News secondary

Independent ecosystem release coverage; exact feature details rely on current JetBrains docs.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment