JetBrains Air Governance extends cost and visibility tracking across AI providers
Six months after introducing JetBrains Central, JetBrains has renamed it Air Governance and made it the place an organization sees and caps what agents from any vendor cost it. The IDE becomes one surface of several.
The Engineer · Build desk
What happened
- JetBrains announced JetBrains Air on 22 September 2026, describing it as an open, multi-surface system of products for developers, teams and organizations, inside and beyond its own IDEs.
- Three products carry the name today: Air in JetBrains IDEs, Air Teams, and Air Governance, which is JetBrains Central renamed, with further products promised as the system develops.
- Air Governance covers organizational policy, visibility, auditability, cost management and accountability for AI-assisted and agent-driven development.
- The company said it has spent 26 years focused primarily on the individual developer workbench, and is now building for the wider system where agentic work is initiated, executed, coordinated, reviewed and governed.
- JetBrains said developers have been adopting agents faster than organizations can build the infrastructure around them, and that different models and agents have proven useful for different tasks.
Why it matters
- What it limits constraint A team that allows a different agent per task needs one reporting path for all of them, and ACP is the only path JetBrains names.
- Who's exposed exposure Extending cost governance across providers puts a policy and finance owner in the path of tool choices that used to end at a developer's machine.
- What it costs cost A platform team can scope a pilot of Air Governance now, but it cannot budget the layer: JetBrains did not publish pricing or licensing terms.
Next story · Build · Sep 15
Java 27 couples post-quantum TLS 1.3 to two newly flipped JVM defaultsConfirmed4 publishers
The Agent Client Protocol is where the design decision sits. JetBrains says ACP standardizes the connection between an IDE and an agent's full harness, including its planning, logic, tools, model routing, and observability [4]. Model routing therefore sits on the agent's side of that boundary. The IDE is a client. For a dollar figure to reach a cost view, the harness has to report which model it called and what the call cost, and the post does not list the usage fields that cross the boundary.
Practical coverage of a cross-vendor cost report is then the set of ACP agents that actually report usage. JetBrains says developers can discover and run a growing range of compatible agents through the ACP Registry while continuing to work inside JetBrains IDEs [5]. A pilot can measure that directly: run two agents from two vendors for a week, then check whether both appear in Air Governance with spend attached.
Air Governance is JetBrains Central under a new name [2]. Central arrived alongside the company's first public experiments with agentic development environments, six months before this post [8]. The post also dates its own progress "Since March" [10]. That puts the governance product at roughly six months old [17]. In between, JetBrains rolled out a Central CLI, shared context, cloud agents, automations, governance, and AI cost controls for teams and organizations [9]. Renaming a control plane is cheaper than building one, and this one was built first.
"The era in which the whole software development system can be contained in one window is ending," JetBrains wrote [15]. The same post says the IDE remains important to the company's future, and that the foundational agentic experience is being brought into JetBrains IDEs [16].
On who chooses the tools, the post argues against a handover. Developers "can choose the agent, model, or service suited to the task without forcing the organization to give up context, visibility, or control," JetBrains wrote [7]. Selection stays with the developer. The reporting and the policy move up a level. The company gives as a core belief that no single model, agent, or service will be right for every developer, team, or task [12].
For a team already on JetBrains IDEs, adopting this costs a second product to configure and a named owner for its policies. Junie, JetBrains' coding agent for professional software development, will be supported across all Air surfaces [11], which makes the all-JetBrains path the shortest one to a working pilot.
What to watch
- Whether ACP Registry listings state which usage and cost fields each agent reports back, or only that the agent runs.
- Whether Air Teams and Air Governance are licensed per developer seat or per agent run when terms appear.
- Whether the additional Air products JetBrains promised ship, or the three named ones carry the system.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence64
- Adoption20
- Hype gap+30
- Incentives74
- Confidence66
Perspective Coverage
3 publishers- Builder
- Builder 40%
- Operator
- Operator 37%
- Investor
- Investor 23%
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
JetBrains announced JetBrains Air in a blog post dated 22 September 2026, describing it as an open, coherent system of products for developers, teams, and organizations, inside and beyond JetBrains IDEs, and as multi-surface and multi-service.
- [2]
JetBrains Air includes Air in JetBrains IDEs, Air Teams, and Air Governance (formerly JetBrains Central), with products available today alongside others that will be introduced as the system develops.
- [3]
Air Governance covers organizational policy, visibility, auditability, cost management, and accountability for AI-assisted and agent-driven development.
- [4]
The Agent Client Protocol (ACP) standardizes the connection between an IDE and an agent's full harness, including its planning, logic, tools, model routing, and observability.
- [5]
Through the ACP Registry, developers can discover and run a growing range of compatible agents while continuing to work inside JetBrains IDEs.
- [6]
Air Governance is designed to extend visibility and cost governance across providers and the different tools through which agentic work takes place.
- [7]
"This means developers can choose the agent, model, or service suited to the task without forcing the organization to give up context, visibility, or control."
- [8]
Six months before the Air post, JetBrains began publicly experimenting with agentic development environments, and around the same time introduced JetBrains Central as an open control and execution system for agent-driven development.
- [9]
JetBrains subsequently began rolling out JetBrains Central CLI, shared context, cloud agents, automations, governance, and AI cost controls for teams and organizations.
- [10]
The post states: "Since March, our products have progressed significantly, but so has our understanding of what agentic development requires."
- [11]
Junie is JetBrains' coding agent for professional software development, and it will be supported across all Air surfaces.
- [12]
JetBrains states as a core belief that the future of agentic development will be multi-vendor, and that no single model, agent, or service will be right for every developer, team, or task.
- [13]
Air in JetBrains IDEs gives developers the environment to direct agents and verify their output using JetBrains' code intelligence; Air Teams turns individual agent activity into coordinated team workflows.
- [14]
JetBrains said that for 26 years it focused primarily on the individual developer workbench, and is now building for the wider system through which agentic work is initiated, executed, coordinated, reviewed, and governed.
- [15]
"The era in which the whole software development system can be contained in one window is ending."
- [16]
JetBrains said the IDE remains important to its future, and that it is now bringing the foundational agentic experience into JetBrains IDEs, giving professional developers an environment where they can work with agents while understanding, changing, and verifying the resulting code.
- [17]
The product now called Air Governance is roughly six months old at the time of the Air announcement, dating to about March 2026.
- [18]
The announcement does not include pricing, licensing, or seat terms for any Air product.
- [19]
JetBrains said developers have been adopting agents faster than organizations can build the infrastructure around them, and that different models and agents have proven useful for different tasks.
Sources
2 independent publishers whose own reporting we read for this story.
- blog.jetbrains.comJetBrains Air: Building a System of Products for Agentic Software Development
1 article · September 22, 2026
- runtimewire.comJetBrains expands Air into a control system for rival coding agents
1 article · September 24, 2026
- thenewstack.io“One of the most significant steps in our 26-year history”: JetBrains goes big on agentic development — and bets the IDE still matters
1 article · September 22, 2026