JetBrains
A suite of intelligent development tools
4.9•69 reviews•1.7K followers
A suite of intelligent development tools
4.9•69 reviews•1.7K followers
Powerful IDEs for most programming languages and technologies along with products for team collaboration.
This is the 26th launch from JetBrains. View more
JetBrains Air
Launched this week
JetBrains Air is built for agent-driven development. It brings your favorite coding agents – Codex, Claude Agent, Gemini CLI, and Junie – into one coherent workflow designed for real codebases.
Air helps you define tasks precisely, run them in isolation, and review the results with full code intelligence – all in one place.
Download Air – free for macOS. Windows and Linux versions coming soon.
Launch Team
A recent thread [1] suggested running more coding agents in parallel. Products like @Axel and @Superset initiated the movement. This is @JetBrains' response. LFG
[1]: How many Claude Codes do you run in parallel?
Product Hunt
Been juggling Claude Code and Codex on the same codebase and they keep stepping on each other's files. So the isolation part — does each agent get its own worktree, or is it more branch-per-task? Curious how the review works when two agents touch the same file.
Confs.tech
@alan_silverstreams hi, Alan! I'm Ekaterina from the Air team. Right now Air supports three ways of running agents: local (your main working copy with the active branch you have selected), git worktree (a new copy of your project sources with a new worktree-assigned branch created) and Docker (similar to worktree but since the workspace is inside the container, you can run multiple instances of your application without port conflicts). It depends where you run review by default it will review task-specific changes, but you can also run review slash command and specify what you want to review (all changes, specific file, commit, or branch).
As a JetBrains subscriber for over a decade (grandfathered, still using WebStorm + AI Ultimate), I’m curious: what’s the one key improvement or use case in JetBrains Air that justifies switching from my current workflow, especially given the reported stability issues i'm seeing down below?
Good luck on the launch. Hope it smooths out quickly for longtime users like me
Confs.tech
@marcelino_gmx3c thanks! The review flow: you can see the whole file that was changed and not only the diff, you can leave comments to the agent right in the code, you can review the code with another agent. We don't see Air is not a replacement for an IDE (if you still use it), more like a companion that is build around agents like CLIs but has a more convenient UI.
@katyaprigara Thanks for that explanation.
How does Air handle agent conflicts or differing outputs when running multiple agents like Codex vs. Claude on the same codebase task? Any built-in diff tools or voting mechanisms to streamline reviews?
Confs.tech
@swati_paliwal hi, I'm Ekaterina from the Air team. For running multiple tasks at the same time Air supports using git worktrees or Docker containers to isolate agents from each other. At the end of the task, you'll be able to review the results, providing agent the feedback, before you bring changes back to the local copy (at this stage you might need to resolve the merge conflicts if main has been updated).
Air shows changes in a diff view. To streamline the review flow, there's a built-in agentic review flow where another agents checks the code (either all changes or specific files only via /review command in chat) and leaves comments. You can also provide agent's comments right in the code, like in a regular code review.
MacQuit
Really cool to see JetBrains tackling the multi-agent workflow problem. As a Mac developer, I've been running Claude Code heavily for my projects and the biggest friction is exactly what you described — context switching between agents and terminals. Being able to define tasks precisely and run them in isolation is key. Curious about the review experience: does Air give you a unified diff view across all agents, or do you review each agent's output separately? Also, any plans for Linux support timeline? Love that it's free — will definitely give it a spin.
Confs.tech
@lzhgus hi! I'm from the Air team. Thanks for your feedback! In Air you work with tasks (and one task is one agent's session) and then you review the task's results as a diff. For tasks we provide a different level of isolation - task/agent is fully isolated if you're using git worktree or Docker container and you will review only the results of this task before bringing changes to the main copy (in this case merge conflicts can occure). If several tasks are running in a local copy, we try to show changes groupped per task if possible.
Linux version is planned for Q2, please stay tuned.
This is exactly the workflow we've been doing manually.
We're 3 people building Vidtreo — a video recording API (also launching on PH today). Our daily reality is running Claude agents across three repos simultaneously: backend on Cloudflare Workers, browser SDK with WebCodecs transcoding, and a React dashboard. The context switching between terminals and agents is brutal.
The idea of referencing a specific line or method when defining a task for an agent — that alone would save us hours. Right now we paste file paths and line numbers into prompts like cavemen.
Sandboxing agents in worktrees is the other killer feature. We've had agents step on each other's changes more times than I'd like to admit.
Really excited to try this with our stack. Multi-agent development isn't hypothetical anymore — teams are shipping production infrastructure this way today.