Coding-Agents

JetBrains Air and the Case for the Agent-Native IDE

JetBrains Air, launched in public preview in early March, is one of the more interesting answers yet to a question the AI tooling market keeps circling: do we really want agents bolted onto traditional editors, or do we eventually need environments designed around them from the start?

Air is betting on the second path.

Why Air Is Interesting

Most current AI coding tools still inherit the shape of the pre-AI IDE. There is a primary editor, maybe a chat pane, maybe an agent sidebar, and the user is still clearly the central operator of a mostly traditional workspace.

Cursor Automations and the Shift from Prompting to Policy

One of the most current product shifts in AI development tooling is Cursor Automations, which turns coding agents into event-driven workflows instead of one-off assistants. The feature can trigger work from commits, Slack messages, timers, and operational events, then route the agent through review, checks, and deployment-style steps with humans only stepping in at key points.

That may sound like just another convenience layer. It is not. It reflects a deeper change in how teams are thinking about AI tooling.

VS Code's New Agent Features Show What 'Practical' Actually Means

One of the better AI tooling posts of the month came from Microsoft itself: “Making agents practical for real-world development.” That framing is useful because it captures what the market is moving toward. The interesting releases are no longer just about whether an agent can generate code. They are about whether the agent can survive contact with a messy, real workflow.

VS Code 1.110 is a good example of that shift. The March release adds native browser control for agents, better session memory, context compaction for long conversations, installable agent extensions, and a real-time Agent Debug panel. None of those features are flashy in isolation. Together, they show what “practical” now means in agentic development.

OpenAI Symphony and the New Bottleneck: Orchestrating Agents Well

OpenAI’s new Symphony project is one of the most revealing open-source releases in the current coding-agent cycle.

At the surface level, it is an orchestration framework for autonomous software development runs. It connects to issue trackers, spins up isolated implementation runs, coordinates agents, collects proof of work, and helps land changes once they are verified. It is built in Elixir on the BEAM runtime and is clearly optimized for concurrency and fault tolerance.

The OpenAI Codex App and What Multi-Agent Development Actually Looks Like

In February 2026, OpenAI shipped a standalone Codex app. The headline is straightforward: it lets you manage multiple AI coding agents across projects, with parallel task execution, persistent context, and built-in git tooling. It’s currently available on macOS for paid ChatGPT plan subscribers.

But the headline undersells what’s actually happening. The Codex app isn’t just a better chat interface for code—it’s an early, concrete version of what multi-agent software development looks like when it arrives as a consumer product. Understanding what it actually does (and doesn’t do) matters for any team thinking seriously about AI-assisted development in 2026.

SERA and the Case for Open-Source Coding Agents That Know Your Repo

If your team has tried Cursor, Copilot, or other AI coding tools and found them underwhelming on your codebase—wrong conventions, missing context, generic suggestions—you’re running into a fundamental limit: those models are trained and optimized for the average repo, not yours. In early 2026, AI2 (Allen Institute for AI) released SERA (Soft-Verified Efficient Repository Agents), an open-source family of coding agents built for something different: specialization to your repository through fine-tuning, at a cost that makes it realistic for more teams.

Prompt Injection Is Coming for Your Coding Agent

In early 2026, a critical vulnerability in Anthropic’s Claude Code made the rounds: CVE-2026-24887, which let an attacker bypass the user-approval prompt and execute arbitrary commands via prompt injection. Around the same time, researchers demonstrated prompt-injection-to-RCE chains in GitHub Actions—an external PR could trigger Claude Code in a workflow and, with a malicious payload in the PR title, achieve code execution with workflow privileges. Real incidents have shown agents exfiltrating SSH keys and credentials from hidden instructions in docs or comments. NIST has called prompt injection “generative AI’s greatest security flaw,” and it’s #1 on the OWASP LLM Top 10. If your team is rolling out AI coding assistants or agentic workflows, this isn’t theoretical. It’s the threat model you need to plan for.