AI coding agents

JetBrains has introduced Air, described as a system of products for agentic software development, where AI agents take on coding tasks alongside developers. The announcement is drawing attention from developers debating how far agentic tools should be integrated into professional IDEs and what it means for JetBrains' flagship products.

Engineering teams using AI coding agents are finding that continuous integration pipelines have become their biggest constraint, according to a report circulating among developers. As agents generate far more code and commits than human programmers, test suites and CI infrastructure struggle to keep up, forcing teams to rethink how they validate machine-written code at scale.

Developers working with AI agents are separating an agent's decision-making logic from the component that generates code or text, a pattern being discussed under the name Jev. The split lets a reasoning model plan while a writing model executes, and people in the field are debating whether this two-brain architecture improves reliability or just adds complexity to agent workflows.

The phrase 'Plan mode is dead' is spreading on Hacker News, attached to a blog post by Aymann Nadeem. Plan mode is a feature in AI coding tools, notably Claude Code, that lets the model sketch an approach before writing code. The post argues this way of working with AI assistants has run its course, apparently because newer agent capabilities make upfront planning less necessary. Commenters on the thread are debating the claim and what it means for developer workflows, though the full reasons are not clear from the snippet alone.