JetBrains Air in WebStorm - one place to run your agents and verify their work
- As of this release, WebStorm ships with Air, a new layer for agentic development. Work with the coding agents of your choice, and run, track, and verify multi-agent workflows inside your IDE, where code intelligence helps agents make fewer wrong turns and gives you the tools to review every change before it ships.
- Your agents, your models, your subscriptions – with Junie Lite for free
- Air works with Claude Agent, Codex, Gemini, GitHub Copilot, Junie, OpenCode, and other ACP-compatible agents. It detects the agents already installed on your machine so you can connect them in a click, and you can add more from the agent registry.
- Your existing setup carries over, too: provider subscriptions, API keys, and even a custom base URL all work, with no JetBrains AI subscription required. Run Claude Agent on your Claude subscription in the terminal or in a full-screen IDE tab, use other agent subscriptions in the chat or terminal, and switch between subscriptions at any moment, even mid-session.
- Air includes free AI with the Junie Lite configuration, so you can use an agent without a subscription. You only need a JetBrains Account.
- A central workspace to review changes and guide the agent
- Review an agent's changes with the surrounding code and your project tools in view, and send feedback straight back to the agent. Anchor a note to a specific line in the diff, or comment directly from the code, so the agent gets concrete context about the change you want. Work in the chat or the terminal, whichever suits you.
- Agents that check their work in the browser
- Code that compiles isn't necessarily code that works. With the Chrome DevTools Connect plugin, your agent tests what it builds in a real browser and fixes problems before giving you the result. When you spot something that needs tweaking, you can show your agent exactly where to make the change.
- With the bundled Chrome DevTools CLI skill, your agent can move through application flows, inspect the DOM and rendered UI, read console logs and network requests, take screenshots, and interact with page elements. It can also reproduce runtime issues and confirm fixes in the browser.
- Ability to inspect designs without leaving WebStorm
- Stop copying values from Figma manually. With Figma Connect, you can browse Figma layers in the IDE, inspect the selected layer, and send screenshots, URLs, and design values to any agent.
- The Inspect panel shows the exact CSS values, colors, and design tokens for the selected layer, so you can build components without opening another tool. Figma Connect needs one-time setup.
- Build with the components you already have
- The Storybook Connect plugin brings Storybook into WebStorm, so you and your agents stay in one window. Browse and search stories in a dedicated tool window, jump between a story and its source, and start your own local Storybook server or set one up in one click. Your changes stay in sync with the Storybook app.
- Storybook Connect also finds components without stories, and its AI-assisted tools generate the missing ones without a detailed prompt. Bundled CLI and skills make the same capabilities available to CI scripts and AI agents. Storybook Connect is a separate plugin and requires Storybook 10 or later.
Platform updates
- Sound cues for IDE events and editor line marks
- Screen reader users now get audio cues for editor line marks: errors and warnings, lines added, changed, and removed under version control, and code folding. You can also hear when things finish. Builds, tests, and other time-consuming background tasks report their results with distinct sounds for success, warning, and error states, and breakpoint hits come with a sound too. And if you work across multiple monitors or several projects at once, enable these sounds so you don't have to glance at the screen to check statuses.
- With screen reader support enabled, line-mark cues and sounds for the most important events (builds, tests, and breakpoint hits) are enabled by default. Agents in Air come with sound cues of their own, and they're enabled by default for everyone, whether or not you enable screen reader support. You'll hear when an agent finishes, stops with an error, or needs your input, and when dictation starts or stops. Everything else is opt-in. You can explore and preview the sounds on the new Accessibility settings page, and use the Play sound checkbox on the Notification settings page to enable cues for a specific notification group.
- Automatic error and freeze reporting
- WebStorm 2026.3 automatically sends error and UI freeze reports to JetBrains, helping identify the problems that interrupt your work and prioritize fixes based on their impact.
- Reports contain only technical data. Personal details such as file paths, URLs, and usernames are removed from report messages before they leave your machine.
Framework and ecosystem updates
- TypeScript 7 support for Angular and React – no migration required
- TypeScript 7 support is stable in WebStorm, including in React and Angular projects. It swaps the Node.js-based language service for a Go-based engine, so coding assistance has less overhead in large projects. You can select it without migrating or changing your project's TypeScript version. On the Kibana codebase, project load time dropped from about 12 seconds to three.
- Angular
- WebStorm now infers correct template types when you work with Angular in WSL, instead of falling back to any. Furthermore, @default never; inside @switch is no longer reported as an unknown block.
- Sass and CSS
- JetBrains have fixed several issues with Sass and CSS support. Namespaced functions and variables inside calc() no longer trigger Unexpected term. In addition, JetBrains removed 161 non-shipping properties from the CSS syntax data. Finally, pseudo-selectors are no longer flagged as unknown when the Images plugin is disabled.
- Testing and tooling
- Single-test runs work again in Vitest 5, and Mocha 12 (ESM) no longer shows a reporter warning for them. The Tailwind CSS language server also works with a remote Node interpreter in Docker on macOS.
Performance and quality improvements
- Find Usages on huge codebases
- Find Usages no longer stalls the IDE for minutes in very large monorepos. JetBrains tested it on Kibana, which has more than 1,000 tsconfig files.
- Angular performance
- Resolving Reference no longer hangs in workspaces with several Angular projects. JetBrains also fixed a memory leak in Angular on TypeScript 7 that was causing CPU spikes of 800% – 900%.