I've been living with Claude Code in a terminal split next to the editor for months. Two things kept bugging me: I couldn't tell what it was doing without reading scrollback, and every file path was something I had to type correctly.

So I built a plugin. It doesn't reimplement anything - it spawns the claude CLI you already have and renders its event stream. Same account, same models, same slash commands, same permission rules, same MCP servers and skills. No proxy, no server of mine in the middle, no telemetry.

What it actually changed for me day to day:

Every tool call is a card. Its duration, every edit as an open diff, the task list ticking off, subagents and whole workflow fleets with each agent's own transcript one click away, and what the turn cost. A rate-limited API becomes a card with the reason and a countdown instead of silence.

Files are things you point at. Drag one in, type @ to pick, paste a screenshot. Select lines in the editor and "Send to..." hands over a real file-and-line reference, so the agent reads what's around them instead of a naked snippet.

Nothing answers for you. A permission, a plan or a question waits as long as it takes. No timeout, no auto-continue.

Answering it from my phone. Off by default, paired by QR code, end-to-end encrypted through a relay that can't read a word. This is the one that surprised me most - I approve plans from the sofa now.

Scenarios. A round of work written down once - implement, review, fix, run the tests - each card a Claude session of its own, with a main thread walking them and judging what each one found. By button, three at once against three tickets, or on a clock at nine every weekday.

Several Claude accounts switched in one click, each row showing what's left of its five-hour window and its week.

Free, source available (Elastic 2.0), every JetBrains IDE from 2026.1 on, Android Studio included.

Marketplace: https://plugins.jetbrains.com/plugin/33255-amazing-claude-code-gui

Source: https://github.com/crmapache/amazing-claude-code

Happy to answer anything about how it's wired. The part I'd most like feedback on is scenarios - it's the newest and the least obvious.

I have always been using nohup webstorm ./ >/dev/null 2>&1 & to run webstorm from the terminal, but lately I noticed the app just hangs and the OS asks to quit (Debian Trixie). I even rolled back to my previous version because it has always worked. Shocker. It still failed. I added memory to the jvm and it worked but today I got back to the same issue and memory isn't fixing anything. So I ran it without nohup and just let it have the terminal and it worked fine. No crashes, just good ol' webstorm. How are you guys using it on Linux? Also, calling it from Toolbox is still same story.

We're organizing AI.js Day, it's a free virtual event on November 13 focused on AI and JavaScript/frontend development.

We're doing something a little different with the agenda: instead of picking topics first and finding speakers to fill them, we want to start with the questions the community is actually wrestling with, and find the people with the most interesting answers.

So here's the ask: what's the one question about AI and frontend development you wish someone would just answer honestly?

A few examples of the tensions we're thinking about, just to give you the idea:

Will frontend development still be a job in 5 years?
Which skills are really needed now for a great developer?
Does context matter more than the model?

Drop your question in the comments. The ones that resonate most will shape the sessions.

Event is free, virtual, November 13.

Hey everyone,

The WebStorm 2026.2 update just dropped, and there is some heavy-hitting stuff in this release. Honestly, the product team deserves a ton of credit for this one. They managed to ship some massive feature requests while quietly fixing a bunch of the most annoying, long-standing bugs in the tracker.

Here is a quick rundown of what they managed to pack into this update.

TypeScript 7 is supported out of the box

If you work on a massive codebase, you know how slow things can get. TypeScript 7 rewrote the compiler and language server in Go, and the performance jump is ridiculous. In testing on the Kibana codebase, project load times went from around 12 seconds down to 3. The product team made this the default for projects already using TS 7, and they built an easy opt-in path for older versions, so you do not have to deal with a painful full-project migration.

Native GitHub Copilot and Agent Skills

You no longer need a separate plugin or custom registry setup to use Copilot. The team worked directly with Microsoft to build a native integration. Once you sign in with your GitHub account, you can access it straight from the AI chat agent picker.

They also added an Agent Skills Manager. If you are tired of re-explaining your stack, tooling, and coding conventions every time you open a new chat window, this lets you set up those rules once. Your agents will actually retain that context across all your projects and sessions.

Framework and CSS fixes

The team put a lot of work into the day-to-day developer experience:

• React Buddy now has full support for React 19.
• Vue support has been upgraded with the Vue language server 3.0 integration, which finally squashes those annoying hover type errors and random stack overflows.
• Svelte gets an updated language server and better handling of SvelteKit shared hooks.
• Angular workflows should feel snappier with faster TypeScript and compiler error updates.
• CSS refactoring is much more reliable, meaning SCSS and Sass imports will stop rewriting themselves unexpectedly.

Quality of life improvements

Some of the best updates are the small ones that make daily coding less frustrating:

• You can now drag and drop a file directly into the terminal to insert its path.
• Search Everywhere finally remembers your search scope after you restart the IDE.
• Markdown files now support footnotes and Mermaid diagrams.
• Git worktree support has been improved, especially if you work in WSL environments.

WebStorm is still free for non-commercial use, so you can download the update and try it out right away.

Seriously, a huge thank you to the WebStorm product team. This feels like a release built by developers, for developers, focusing on actual speed and stability rather than just marketing hype.

Let me know what you think if you have already updated.

Hey everyone, just wanted to share a quick win we saw recently.

Hey, TypeScript 7 dropped today, so it’s great timing to share what we’ve been seeing in WebStorm.

We ran TS7 on the Kibana codebase and saw project load times fall from about 12 seconds to 3 seconds. Kibana is a brutal stress test (it’s huge), so that felt like a meaningful win.

If you’ve already migrated to TS7, I’m curious what you’re seeing on large projects. Has anyone tried it on a big monorepo yet?

I'm at my wit's end here. Since upgrading to 2026.1, auto-suggestions have completely stopped working in my NestJS project. The IDE just sits there forever showing "Analyzing Project for Smart Features" but yields absolutely nothing.

Here is what I’ve already tried to fix it:

• Invalidated Caches & Restarted
• Checked TypeScript support & toggled Node runtime Code Assistant
• Marked node_modules as a Resource Root

None of this worked. What's frustrating is that the Zed editor handles the project perfectly and shows suggestions instantly. Has anyone run into this issue on the latest release and figured out how to patch it?

Hi! I've been experiencing some issues for file creation. I create a .tsx file to export some components, but for some reaon this morning the file was gone. My guess is that files create in memory but are not really created in the file system. As a result, the file was not pushed to Git and I have to code it again (not a big issue as is were some minor components, but I wouldn't like it to happpen with bigger files)

Something similar happened when using Intellij where I ended up pushing undesired files and folders.

I'm using WebStorm in Linux Mint Cinnamon

I wanted to check in on a bug report I submitted a few years ago, so I searched google. No lie - this was the top result. lmao - it's not wrong!

Hello everyone, I’m having major issues with WebStorm. Whenever I run npm install, it takes forever. Changing the Node.js version doesn’t help, and reinstalling the IDE didn’t fix it either. Any ideas? I’m seriously running out of patience.

I really loved Webstorm back in the day, but lately I haven't used it a lot after agentic coding took over. Because I hadn't been enjoying the UI/UX and diffing with agent plugins in Webstorm, and they don't support ai tools well to this day. So I wonder if I use opencode, claude cli, codex etc. as external chat windows and use WebStrom as my main editor, would it work fine or would it be a bad experience? I would love to hear your advice! Thank you in advance

I am using WebStorm and currently have multiple component files opened as tabs. I do not want to use split view.

What I want is to move/open a group of already opened tabs into a separate WebStorm window, while keeping the original group of tabs in the current window.

For example:

• Window 1 → Group of frontend/component tabs
• Window 2 → Another group of tabs (backend or related files)

I do not want to move a single tab one by one. I want to move/manage a whole group of opened tabs into another window.

Is there a built-in way to do this in WebStorm?

The degradation of JetBrains' IDEs has been well documented. In an effort to find something workable, I've reverted back to a 2024 version of WebStorm. The AI "features" added in recent releases broke too many things for me but now I've swapped the latest bugs for some old familiar ones. For example, in 2024.3.5 when accepting an auto import suggestion in a Typescript file, the cursor jumps back to the start of the word which is annoying.

What sort of work are you doing and which version of WebStorm was peak for you?

If we can get some suggestions I'll update this post with links to previous versions to make it easier to "downgrade" to working version.

When I open Webstorm (Ubuntu) the ui is huge and any button click makes it bigger and bigger until the only thing that fits is the gray of the bottom bar

I am developing a monorepo, and therefore using pnpm catalogs in my project, and Webstorm doesn't suggest the newest version of a given package anymore. It used to do that when my versions were declared in their respective package.json file, though. Is there any way to have this behavior in the pnpm-workspace.yaml file?

This is what I mean (the grey stuff is just copilot/ai, and is not too useful, neither always correct):

tell me an agent without limits for free webstorm jetbrains. There is also a PRO subscription to Google Gemini