JetBrains released WebStorm 2026.3 on November 5, 2026. The update to its JavaScript and TypeScript IDE centers on one idea: keeping the full frontend loop, from a Figma design through component code to a running page, inside the editor and within reach of AI coding agents.
The release adds the JetBrains Air agent layer, three integrations named Figma Connect, Storybook Connect and Chrome DevTools Connect, and Stable TypeScript 7 support for React and Angular. It also fixes slow Find Usages runs in huge monorepos and a CPU-hungry Angular memory leak, so even teams that skip the AI features have reasons to upgrade.
JetBrains Air arrives in WebStorm
Air is the new agentic development layer that JetBrains now ships across its IDEs. In WebStorm it lets you start several agent sessions at once, follow their progress, and review the resulting changes with the IDE's code intelligence beside you. The same layer appears in the IntelliJ IDEA 2026.3 release.
Air is not tied to a single vendor. It supports agents that speak the Agent Client Protocol (ACP), and the blog post names these:
- Claude Agent, Codex and Gemini
- GitHub Copilot, Junie and OpenCode
- Other ACP-compatible agents, found automatically if installed or added from an agent registry
Existing provider plans, API keys and custom base URLs carry over, and a JetBrains AI plan is not required. A free Junie Lite configuration only needs a JetBrains Account. Review happens in a shared workspace where you can pin a note to a line in the diff and send it back to the agent as feedback.
Users of the older AI Assistant will see a trial offer for Air. Switching hides AI Assistant, though JetBrains documents a way back. Skills, MCP settings, ACP agents, login details and chat history move across automatically, but history from chat mode does not.
The design-to-production workflow
The three Connect tools target the time developers lose jumping between Figma, Storybook, the editor and a browser. Each one feeds context to whichever agent you use, and all of them run inside Air.
- Figma Connect with the Inspect panel: browse Figma layers in the IDE, pull screenshots, links and design values into the agent context, and read the precise CSS, color and token values of the selected layer. It needs a one-time connection setup.
- Storybook Connect: a tool window to search stories, move from a story to the matching source file, and run or create a local Storybook server. It spots components that lack stories and can generate them with AI. It is a separate plugin and needs Storybook 10 or newer.
- Chrome DevTools Connect: a bundled plugin and CLI skill that let an agent open pages, walk through flows, inspect the DOM, read console and network output, click elements and take screenshots, so it can confirm a fix before handing it back.
Storybook Connect also ships a command line interface under the webstorm storybook-connect command. It can list component props, suggest possible stories, report missing ones and create them, which makes the same checks usable in CI scripts. For Chrome DevTools Connect, WebStorm asks to install a required package on first use, with no manual MCP wiring.
TypeScript 7, frameworks and fixes
TypeScript 7 support is now marked Stable, including for Angular and React projects. It replaces the Node.js language service with a Go-based engine and does not force you to change your project's TypeScript version. JetBrains reports that loading the Kibana codebase fell from roughly 12 seconds to about three.
Several smaller fixes round out the framework work:
- Angular template types are inferred correctly under WSL instead of becoming any, and an @default never; branch in @switch is now recognized.
- Namespaced Sass functions and variables inside calc() stop raising errors, and 161 properties that never shipped were removed from the CSS data.
- Running a single test works again in Vitest 5, Mocha 12 in ESM mode drops a reporter warning, and Tailwind CSS language support now runs on macOS when Node is a remote interpreter inside Docker.
On performance, Find Usages stops locking up the IDE for long stretches in giant monorepos. JetBrains verified this on Kibana, a codebase with over 1,000 tsconfig files. Reference resolution stays responsive when a workspace holds several Angular projects, and a leak that drove CPU use to 800-900% on TypeScript 7 is fixed.
Platform changes: sound cues and automatic reports
For accessibility, WebStorm adds sound cues. Screen reader users hear line marks such as errors, warnings, version control changes and folds, plus distinct sounds when builds and tests finish or a breakpoint hits. Air agents also play sounds when they finish, fail or need input, and these are on for everyone.
WebStorm now uploads crash and UI freeze data to JetBrains on its own. The company says personal details like paths, links and user names are removed before reports leave the machine. You can turn this off under Settings, Appearance and Behavior, System Settings, Data Sharing.
What it means for developers
For frontend teams already using coding agents, the biggest change is that agents can now see the design, reuse existing components and test their output in a real browser. That should cut the number of rounds where an agent returns code that compiles but looks or behaves wrong.
Because Air accepts your current agent plans and keys, you can try it without a new subscription. Start with one small UI task, hand the agent the Figma layer and related stories, and let it verify the page in Chrome. Keep human review; the browser check is a first filter only.
Teams on large TypeScript or Angular monorepos should test the Stable TypeScript 7 engine early, given the load time and Find Usages gains. Check your privacy rules too, since automatic crash and freeze reporting is now on by default and some companies will want it disabled.
How to get WebStorm 2026.3
You can update through the Toolbox App or download the release from the JetBrains website. Storybook Connect must be installed separately from JetBrains Marketplace, and Figma Connect needs its connection set up once before use.
Conclusion
WebStorm 2026.3 pushes JetBrains' agent strategy into frontend work by joining design, components and browser testing around Air. Stable TypeScript 7 and the monorepo performance fixes give the release value beyond AI. Teams should try the new workflow on small tasks and review the new data sharing default.
Sources
See my articles more often when you search Google.
