JetBrains Air is an open system of products that coordinates agent-driven software development across individual workstations, team workflows, and organizational governance. It bundles three core surfaces - Air in JetBrains IDEs for directing agents and verifying their output, Air Teams for orchestrating team-level automation and workflows, and Air Governance (formerly JetBrains Central) for policy, auditability, and cost management - while offering Junie as JetBrains’ own coding agent. A foundational design choice is multi-vendor support: the Agent Client Protocol (ACP) and ACP Registry let developers discover and run diverse agents and models inside the same ecosystem. The central argument is that agent adoption has outpaced organizational infrastructure, shifting the bottleneck from code generation to understanding, verifying, and owning changes; as a result, visibility, provenance, review responsibility, and cost control are now the critical problems.
Technically and operationally, Air emphasizes shared context, deterministic code intelligence, and a single source of policies, logs, and cost reporting so organizations can run multiple agents without losing control. JetBrains will surface its code-aware intelligence across agents, route work between models and humans, and trigger agent workflows from repository events and schedules. Releases will roll out in stages - with previews and clear scopes - and expand to mobile and remote interfaces so decisions and oversight travel with the work. The goal is to let teams use the best tools while preserving accountability, audit trails, and organizational governance.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.
Formal verification techniques are applied to product specifications written in prose to improve their correctness. Converting specifications into a formal code-like format helps enhance reliability and reduce errors. (alexanderabramovich.medium.com)
Git 2.56 and 3.0 are upcoming versions of the popular version control system. The development community is anticipating new features and improvements in these releases. (lwn.net)
Markdown is increasingly becoming the primary source code, stored alongside the actual code it generates. This shift means that code and tests should be derived from Markdown, which acts as the definitive record of software systems. (htmx.org)
Linear reworked its CI system to address bottlenecks caused by AI-driven code validation, reducing wait times from over 6 minutes to just above 5 minutes. They achieved this by upgrading infrastructure, optimizing jobs, reducing setup redundancies, and making test execution more efficient. (linear.app)
Foremerge is a tool that detects conflicts between parallel coding agents to improve collaboration. It helps developers manage intent conflicts during AI-assisted code creation. (github.com)
Dynamic derivations in build systems allow the build graph to be defined as the process progresses, unlike traditional systems that require the graph upfront. This shifts Nix from an applicative to a monadic approach, enabling more flexible and adaptive build processes. (fzakaria.com)
Today's best Hacker News stories, summarized and screenshotted, one email a day.