The Pulse

JetBrains Adds Figma, Storybook and Browser Tools to WebStorm

WebStorm 2026.3 brings Figma, Storybook and browser testing into the IDE and makes JetBrains Air available for running and reviewing coding-agent sessions. The release also includes accessibility features and fixes across TypeScript, Angula

AI.info Team · Written with AI · fact-checked · 2026-11-06

WebStorm 2026.3, now available from JetBrains, brings design references, reusable interface components and browser testing into the IDE and connects those steps to coding agents. The release also makes JetBrains Air, a workspace for running agents and reviewing their changes alongside project code, available in WebStorm.

JetBrains Air puts agent sessions inside WebStorm

Air supports JetBrains and third-party agents, including Claude Agent, Codex, Gemini, GitHub Copilot, Junie and OpenCode, as well as other agents compatible with ACP. It can detect agents already installed on a developer’s machine, or users can add agents from the registry. Existing provider subscriptions, API keys and custom base URLs work in Air, and no JetBrains AI subscription is required.

Developers can run multiple sessions in parallel and choose between chat and terminal workflows. Air provides a view of an agent’s changes with surrounding code and project tools, and lets developers send feedback directly to the agent. Comments can be attached to a particular line in a diff or entered from the code itself.

The release also includes free AI through the Junie Lite configuration, requiring a JetBrains Account. For developers moving from AI Assistant, Air can migrate IDE skills, MCP configuration, ACP-installed agents, authentication and chat history; chat mode history is not migrated.

Figma details and Storybook components enter the workflow

Figma Connect lets developers add screenshots, URLs and design values to agent context from WebStorm, browse Figma layers and inspect a selected layer while working in Air. Its Inspect panel surfaces CSS values, colors and design tokens for the selected layer. The connection can pass design context to agents including Claude Code, Codex and Cursor, and requires a one-time setup.

Storybook Connect adds a dedicated tool window for searching and browsing stories, jumping between a story and its source code, and starting a local Storybook server. Its tools analyze component props, identify components without stories and generate missing stories with AI assistance. The plugin is distributed separately and requires Storybook 10 or later.

Chrome DevTools Connect gives agents a browser to test

With Chrome DevTools Connect, an agent can open pages, move through application flows, inspect the DOM and rendered interface, and read console logs and network requests. It can also take screenshots, interact with page elements, reproduce runtime issues and check whether fixes work in the browser. WebStorm prompts users to install a required package the first time an agent uses the bundled Chrome DevTools CLI skill.

JetBrains presents Figma Connect, Storybook Connect and Chrome DevTools Connect as connected stages from design through implementation to a working page, all running in Air within WebStorm. The release notes describe TypeScript 7 support as stable in WebStorm, including for React and Angular projects, and say users can select it without migrating or changing their project’s TypeScript version. Project load time on the Kibana codebase fell from about 12 seconds to three, JetBrains reports.

WebStorm adds accessibility and framework fixes

WebStorm 2026.3 adds sound cues for events including builds, tests, breakpoint hits and agent status changes. With screen reader support enabled, cues for editor line marks and key events are on by default; other sounds can be enabled in settings. The IDE also automatically sends technical error and UI-freeze reports, with file paths, URLs and usernames removed from report messages before they leave the machine.

Other updates cover Angular, Sass, CSS, Vitest, Mocha and Tailwind CSS. JetBrains removed 161 non-shipping properties from CSS syntax data, single-test runs work again in Vitest 5, and it fixed a memory leak in Angular on TypeScript 7 that was causing CPU spikes of 800% – 900%.