JetBrains launches Air with remote VM swarms and Git Worktrees

• JetBrains launched Air as an “agentic development environment” where Claude, Gemini, Codex, and Junie can work “side-by-side with you,” according to the launch thread, with task execution spanning local host, Docker, Git Worktrees, and remote VMs architecture post.
• The implementation detail that matters most is Air’s shared, out-of-process state: JetBrains says “all of Air's data lives in a synced database” shared by workspace, UI, and code insight, which is what enables local UI over remote execution state architecture remote dev model.
• JetBrains is also positioning Air as a cross-platform client stack, saying it is “fully Kotlin Multiplatform” across desktop, mobile, and web via WASM, with desktop rendering on a Skia-backed canvas using Compose Multiplatform platform post desktop stack.
• Air’s most unusual storage primitive is a checkout-free filesystem on a Git server: JetBrains says the IDE can treat a server-side repo “as a normal file system” without checking it out, framing it as “Google Docs, but for your monorepo” git filesystem thread.

JetBrains is pitching Air less as an autocomplete upgrade and more as a control plane for parallel coding agents. The launch thread says developers can run Claude, Gemini, Codex, and Junie “side-by-side with you,” while the product page at air.dev describes isolated task execution, review, and switching between concurrent jobs.

The concrete workflow change is where those agents can run. According to the architecture post, agents can edit code alongside the developer “on host, in Docker, or via Git Worktree,” and Air can also “run a swarm of agents on a remote VM” while you inspect progress from a native client. That makes Air closer to multi-workspace orchestration than a single-pane chat interface.

JetBrains says the key architectural move is that “state lives out of process.” In the thread, it describes “a synced database shared across every process” for workspace, UI, and code insight, instead of binding state tightly to one local IDE instance.

That design is what enables the remote setup: JetBrains says the file-system daemon can run on the remote machine while the native UI stays local, including on the web client. The same post claims that because interactions are represented as state changes, with conflict resolution handling collisions, Air gets “real-time collaboration for free.” A later follow-up post says this extends to “separate workspaces — one per agent,” where you can watch “cursors, files changing, shells running.”

JetBrains is using a custom client stack to make the same environment portable. In its platform post, the company says Air is “fully Kotlin Multiplatform” and targets desktop, Android, iOS, and web via WASM; another post adds that desktop rendering uses a Skia-backed canvas with Compose Multiplatform.

The more novel piece is storage. JetBrains says in the Git filesystem thread that it implemented a filesystem “on a Git server,” which Air treats like a normal filesystem even though “nothing is ever checked out.” If that holds up in practice, it could reduce the local checkout and branch-management overhead that usually comes with multi-agent work across large repos.