JetBrains can unify agent surfaces. That is coordination. I’ve shipped FTNS.ai, KnowCap, Conquest, and 3D Trading Chart, and I founded Cryudine Group, an AI agency for U.S. SMBs — enough times through the merge to know the hard part is still who owns verification, approval, and rollback. I have not used JetBrains Air or Junie. This is not a product review.
What JetBrains Air is (vendor surfaces — not a product trial)
On September 22, 2026, JetBrains published the launch of JetBrains Air. Kirill Skrygan’s post frames Air as an open, multi-surface system of products for agentic software development — inside and beyond JetBrains IDEs.
Per that post:
- Air in JetBrains IDEs — directing and orchestrating agents and verifying their work inside JetBrains IDEs.
- Air Teams — coordinating and automating software-delivery workflows involving developers and autonomous agents.
- Air Governance (formerly JetBrains Central) — organizational policy, visibility, auditability, cost management, and accountability for AI-assisted and agent-driven development.
Junie is JetBrains’ coding agent; the vendor says it will be supported across all Air surfaces. ACP standardizes the IDE-to-agent connection; the ACP Registry is how developers discover and run compatible multi-vendor agents inside JetBrains IDEs — per the vendor post.
I am attributing that map. I have not used JetBrains Air or Junie.
The shipper filter — who owns the merge?
When I ship, the filter is blunt: after the agent produces a change, who owns the merge? Who verifies the diff? Who approves? Who owns rollback if production breaks? Who gets the call when the “almost right” change is wrong?
JetBrains’ own launch post lands near that line. It says code becomes cheaper to generate but more expensive to verify. It says accountability cannot be delegated — an agent will not get the call at 3:00 am when something breaks, and responsibility for what ships still belongs to the people and organizations that ship it. That is vendor framing. I am quoting the problem they named, not endorsing that Air solves it.
Unifying agents does not answer those ownership questions. Visibility is not merge authority. Same filter as Muse and Jev: distribution is not shipping, typed decisions are not the button, orchestration is not the merge. See Muse hit #1. That isn’t the hard part of shipping an app. and Jev grades decisions. It still doesn’t get the button.
Unifying agents is coordination, not merge authority
Air’s multi-vendor pitch — ACP, the ACP Registry, governance across providers — is coordination infrastructure on the vendor’s description. Shared context, policies, a cost view, a record of what happened: organizational claims, not merge authority.
The person who presses merge owns the landing. The person who can roll back owns the failure mode. The person who answers when production breaks owns the accountability. No agent registry or IDE surface changes that unless a human still decides yes or no on what ships.
Orchestration can help. It is not the hard part. Verification, merge approval, and rollback are.
Continuity — same ownership line as Muse and Jev
Charts are not a new filter. Confidence scores are not a new filter. Unified agent surfaces are not a new filter.
Muse hit #1 measured distribution; shipping still meant who owns the action after the tap. Jev returned typed decisions with confidence; analysis shape is not execute authority. Air unifies agents across IDEs, Teams, and Governance. Unifying orchestration is not owning the merge.
Different launches. Same line. I have not used JetBrains Air or Junie.
Key takeaways
- JetBrains launched Air on September 22, 2026 as a multi-surface agentic system — vendor post, not a product trial.
- Surfaces to attribute: Air in JetBrains IDEs, Air Teams, Air Governance (formerly JetBrains Central); Junie across surfaces; ACP + ACP Registry.
- Vendor thesis to attribute: code gets cheaper to generate and more expensive to verify; an agent will not get the call at 3:00 am.
- Shipper filter unchanged: orchestration ≠ who owns verification, merge approval, rollback, or production accountability.
- I have not used JetBrains Air or Junie. Same ownership line as Muse and Jev.