JetBrains announces JetBrains Air, an open software development system

Summary

JetBrains has consolidated its 2026 agentic development experiments (JetBrains Central, cloud agents, CLI tools) into a single product family called JetBrains Air. This family encompasses in-IDE agent orchestration, team workflow coordination, and enterprise governance. At the core of this structure is the Junie coding agent and the new Agent Client Protocol (ACP) for interacting with third-party agents.

Why it matters

JetBrains is transitioning from being a single IDE provider to a multi-surface platform for agent-assisted software delivery. This move demonstrates that the IDE is no longer the sole center of development work. The company's multi-vendor philosophy and ACP standardization efforts aim to position JetBrains not as a closed ecosystem, but as a neutral orchestration layer. This could reshape how teams integrate AI coding tools. For the broader software tools market, this is a direct challenge to the assumption that a single vendor (or single model) will dominate agentic workflows.

Highlights

• JetBrains Air unifies three layers: in-IDE agent control, Air Teams for coordinated multi-agent workflows, and Air Governance (formerly JetBrains Central) for enterprise-level policy, auditing, and cost visibility.
• The Agent Client Protocol (ACP) and registry aim to allow developers to integrate non-JetBrains agents and models into the system while preserving JetBrains' code intelligence and governance rules.
• JetBrains frames this transition as the end of the era where 'the entire software development system could fit into a single window.' The company positions the IDE not as a central element, but as one of many surfaces.

Critical take

The announcement reads largely as a rebranding and consolidation of features that were already available in public experiments. Terms like 'open' and 'multi-vendor' serve more as a targeted framework than proven capabilities. No concrete ACP adoption metrics, third-party agent examples, or independent benchmarks are provided. The article is nearly a verbatim press release, lacking critical analysis, user feedback, or competitive context. Consequently, it is difficult to assess whether this represents a genuine architectural transformation or merely a marketing-driven repackaging of existing tools.