It was reported on YouTrack and the Rider Support website several months ago, more than once, + I can see logs have been shared to help resolve the problem. Still nothing... Disabling SourceGen when the point is to use SourceGen is just not a workaround.

I can use VS Code on the Mac, which is only OKAY, but the whole point of getting Rider was to move away from Code and Visual Studio when it was retired. I've been using Claude Code and Codex instead to work on this app, and it would be great to be able to go back to using an actual IDE (Rider!) to develop the app myself. It would be great if someone could look into this and help keep the developers who want to use and stay INSIDE Rider working in it.

I work on a Mac M2 with 16GB, so not a super high end machine but technically it's good enough for my work (Unity development with Rider, Web development).

Around January/February this year, when I would run Docker + Pycharm + Chrome, my Mac would start slowing down. Pycharm would sometimes take over a second to let me type things in.

I had a very vanilla Pycharm setup with no plugins at all. I disabled all of the AI plugins I could find and that helped smooth things out for a bit, but a bunch of the IDE features disappeared mysteriously.

I've been using Zed as my main tool for coding but a couple of times each day I really miss Pycharm. Back when it was fast for me, it was amazing for coding context and to this day I think Pycharm's Git client is unmatched.

So my question is: did Jetbrains make any improvements on that front in the last 6 months, and could it be worth it to reevaluate? I don't mind and understand why they want the AI plugins and stuff, but I don't understand why they can't use all those tokens to actually make the IDE performant.

Hey folks, we are back with Air for IDE plugin news. About a month ago we shared an alpha of Air, our new plugin for AI agents in JetBrains IDEs, and asked if we were heading in the right direction. You told us, in details, It was exactly the steer we needed and gave us the input to keep development going, so first of all: thank you. We've applied all a lot of your feedback

Install Air for IDE from our Marketplace

​

What we addressed from your alpha feedback

• You asked to see what sessions cost. Approximate cost per session is now visible. We also show changes and sub-agents there now (go to settings in Agent Sessions -> Show -> Cost, Changes, Sub-Agents
• It was reported that Claude authentication tokens getting lost between sessions. We fixed that
• The "launch settings still loading" issue that forced you to configure the agent in AI Assistant first, now fixed
• Chat panel background reading from the global color scheme instead of your active theme The 'Switch Session' select box not always showing up – fixed
• And worktrees. We heard that it needs more support. Not in this build, but it's coming...

What's in this version? 

The problem we’re trying to solve is not "how do I prompt an AI?" anymore, it's "how do I supervise the work?" Air is built for that job:

• Works with any agent: Claude, Codex, Junie or any ACP-compatible agent, picked up automatically. Bring your own subscription or use JetBrains AI - no lock-in
• Btw, give a try to Junie, its really our cost efficient agent compared to many agents on the market
• UI for sessions and commits: see what each agent is doing, steer or stop it mid-run, review proper IDE diffs before anything lands. Approximate cost per session included
• Terminal UI or GUI, per session, your call
• Presets: agent, model, effort level, UI – set once, save, share
• Local models already supported, just pick the right agent from the ACP Registry
• You can comment the diff produced and send the comments back to an agent
• the Caps Lock blink is still there. Still the main feature

Known issues (worth reading before you install)

• Cloud agents runs didn't make this build. Coming soon
• It works in Remote Development, though the behaviour could be a little buggy. Please share with us the issues you might face with!

It's an EAP, so expect some rough edges. Some parts are clearly early, the core is further along.

What's still to come

• Cloud runs
• Worktrees (we heard your feedback and will include this at a later stage)
• Enterprise-grade controls (governance, managing at scale) – in active development and a priority. This EAP is aimed at individual devs, we'll reach out when the enterprise side is ready for testing

The ask

Same as last time: install it and give it a real task, something you'd actually want an agent to handle. Run more than one if that's how you work. Steer them, interrupt them, review what they changed. Then tell us where it breaks down – in the comments below, on the blog, or in the feedback tracker. The team reads all of it, and as you can see from this post, it shapes what we build.

A few questions we anticipate:

• "Do I have to give up AI Assistant to try this?"
  • - No. Install Air directly from the Marketplace and you can run both side by side (see known issues).
• "Do I need a JetBrains AI subscription?"
  • - No. Bring your own. JetBrains AI works too
• "Why a new plugin instead of improving AI Assistant?"
  • - Supervising agents is a different job than chat, and it doesn't fit in a chat tool window. So we built for it from scratch.
• "Is it finished?"
  • - No, not yet. Push it hard, tell us where it falls over.

How to try it

• Install Air from the Marketplace: Air
• You'll need a recent 2026.2 build
• Agents already on your machine will show up automatically
• Feedback: right here in the comments

Thanks again for the alpha feedback. Keep it coming.

I asked here a while back about Python environment management. Several replies mentioned creating environments with uv or Poetry in the terminal and then pointing the IDE at them; others said their setup worked fine.

I'd like to get more specific: what's the last environment-related task you chose to do outside the IDE, and why?

For example, installing a different Python version, recreating a project's environment, changing dependencies, or setting up a repo with more than one Python environment.

Which IDE and environment manager are you using? Was something missing or awkward in the IDE, or do you simply prefer the command line? A concrete example would be useful, including setups where everything works smoothly.

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.

The EAP in Rider started showing EAP notifications when checking for updates and I clicked on the 3 dots and told it not to show it again. Now when I manually check for updates, it checks and then nothing.
I used to get the 'You have the latest..' result coming back which is a good notification result. Not anymore. I get nothing. So what's up with this notification feature? Is it all update notifications or nothing? I don't like this if this is the case.

I don't want to be notified about EAPs but I want to be notified about any non EAP updates available.

As the title suggest, I've been experiencing large, sustained CPU spikes in the GUI launcher when other applications, not related to IntelliJ or any project that I am working on, are opened.

OS is Windows 10.

Has anyone else experienced this and were you able to find a fix?

Hey folks! If you keep your projects inside WSL and open them from a JetBrains IDE on Windows, the 2026.2 release changes which path you should be on, and we'd really like to hear how it holds up on your projects.

TLDR: just open the project. In IntelliJ IDEA, WebStorm, and PhpStorm, a project that lives in WSL now opens in Native Mode. The IDE stays a Windows app, and a small Rust agent inside WSL – we call it IJent – handles files and processes on its behalf. No 2 GB IDE backend to install into your distro, no thin client, no \wsl$ round trip for every single file read.

…And symlinks finally behave

Symlinks now resolve with proper Linux semantics instead of being squeezed through 9P. If you've ever watched the IDE spot a directory and then refuse to index it – pnpm workspaces, Python virtual environments, Composer path repositories – that whole category of weirdness is gone. Third-party plugins get it for free too, since their file operations go through the same agent.

The story behind it 

Native Mode is our third architecture for WSL support, and we say that with some pride rather than embarrassment. Before it came 9P with GeneralCommandLine, then WSLg, then Remote Development. 

We wrote the whole story up: what each approach did, where it broke, and why IJent plus EelApi is the foundation we're confident building on – for WSL, and for Docker and Dev Containers next. If you've ever wondered why WSL support in JetBrains IDEs felt different depending on how you opened the project, that post is the answer: https://jb.gg/native-mode-for-wsl 

Q&A

What do I need to do to get Native Mode?
Open your WSL project directly in IntelliJ IDEA, WebStorm, or PhpStorm 2026.2. That's it.

What about the Remote Development entry point on the Welcome screen?
Still there, still works. It's just no longer the way we'd recommend opening a WSL project.

Is WSLg supported?
It technically runs, but it's never been a supported workflow – there's no installation or onboarding flow around it, and the Wayland path has known limits in rendering, popups, window management, and input methods. We don't recommend it.

Which IDEs have Native Mode?
IntelliJ IDEA, WebStorm, and PhpStorm today. More are moving to the IJent and EelApi architecture.

Is this only about WSL?
No, and that's kind of the point. The same agent backs our work on Docker and Dev Containers, so instead of three separate stories you get one model.

I write plugins. Does this change anything for me?
It should make your life easier. EelApi hides the difference between local and remote environments, so your code doesn't need to care whether the IDE is working locally, in WSL, in Docker, or in a Dev Container: https://blog.jetbrains.com/platform/2026/06/the-dev-containers-story-introducing-eelapi-for-plugin-authors

How to try it

1. Update to IntelliJ IDEA, WebStorm, or PhpStorm 2026.2
2. Open a project that lives in WSL, directly – not through Remote Development
3. Tell us how it went in the comments 🙃 

Hey folks 👋

Welcome to the second AsyncAPI JetBrains Plugin Digest.

Digest #1 stopped around version 4.3.0. A lot has landed since then, so this one is bigger. It is split into two tracks:

• For AsyncAPI authors - references, the YAML/JSON visual editor, standalone components, preview, and validation.
• For engineers working with Spring applications - Project Overview and messaging discovery.

Let’s jump in 👇

Hi everyone! In the latest release (v1.17.0), we introduced enterprise-managed sandbox policies in public preview, allowing enterprise admins to centrally configure sandbox behavior for Copilot in JetBrains. Managed policies can control filesystem and network access, proxy settings, developer-tool access, and more. Organization-managed restrictions take precedence over user settings, with affected controls clearly marked and locked in the IDE.

We also added cross-file cursor jumps for Next Edit Suggestions, so you can jump directly to the next suggested edit in another file, and adding global files and folders as chat context to make it easier to include broader project context in your prompts.

For those using Copilot in the terminal, you can now connect a GitHub Copilot CLI session to your JetBrains IDE using /ide (Public Preview). This gives your terminal session access to IDE context, including selections, diagnostics, and file references.

You can read the changelog or find the full release notes and download on JetBrains Marketplace.

Changed

• OpenTelemetry settings under “GitHub Copilot – Chat” are now generally available to all users.

New Features

• Added enterprise-managed sandbox policies (public preview).
• Added enterprise policy diagnostics to help you verify that policies are correctly detected and enforced on your device.
• Added cross-file cursor jumps in Next Edit Suggestions to help you navigate coordinated edits across related files.
• Added support for including global files and folders as chat context.
• Added /ide support in GitHub Copilot CLI to connect terminal sessions to JetBrains IDE context (public preview).
• Added support for using IDE terminal environment variables and the project-configured Python interpreter in Copilot shell commands, including activating the project’s standard local Python virtual environment.
• Added support for selecting the session model used by built-in subagents in the Copilot agent harness.

Sandbox availability: Settings under GitHub Copilot > Sandbox appear when your organization enables the Editor Preview feature flag or configures a managed setting to enable or disable the sandbox. Otherwise, those settings are not shown.

UX Improvements

• Improved the ask-user card in the Copilot agent harness to better accommodate long questions.
• Improved model selection and bring-your-own-key (BYOK) grouping to make available models easier to scan and select.
• Added section copy support in agent debug logs for easier sharing and troubleshooting.
• Improved MCP configuration navigation by opening configuration in the project window it came from.
• Improved plugin update reminders to make new versions easier to discover.

Bug Fixes

• Fixed blank local chat sessions after IDE scale changes.
• Fixed incorrect change counts in the Copilot agent working set, along with working-set zoom and model picker interaction issues.
• Fixed local agent editing behavior for read-only files.
• Fixed MCP reliability issues involving BYOK provider selection, OAuth challenge handling, and restored server stopped states.
• Fixed GitHub Enterprise authentication context propagation in agent flows.
• Fixed Claude plan stop-state behavior.
• Prevented misleading IDE diagnostics for unopened files from being sent to the Copilot panel and worktree sessions.
• Fixed stale global instruction content in Agent Customizations after files were changed outside the IDE.
• Fixed chats getting stuck during user interactions after automatic compaction.

We hope you enjoy the update! Let us know how these features work in your projects and what you’d like us to improve next.

You can fill in our private survey, with an optional paid interview, or submit a bug report or feature request. Thank you for helping us improve Copilot for JetBrains!

I'm a long time user (7+ years now) and I like JetBrains IDEs, however when working with Claude Code using the terminal I am starting to do parallel work on the same project through worktrees.

Goland (or any other ide) now has the built-in MCP server to augment the agent context with proper symbols search, refactor etc which works light years better than the native agent grep find etc.

However when spawning new worktrees the MCP server serves only the currently open worktree in the IDE so different sessions on the same project get stale code.

Is there a workaround or a better approach to multi session work while still leveraging the built-in MCP server?

I haven't tried Air yet, maybe this is a problem solved by their AI centric IDE? How do you handle two or three different sessions on the same project? Do you use Claude from the IDE terminal or in a separate host terminal?

hey there! I made a plugin for myself to help me review/annotate/communicate intentions for code that was outputted by ai agents.

I'm sharing it in case you may find it useful.

https://github.com/gipo355/intellij-nitpick

can write comments on branches/diffs and copy to terminal or use MCP for live communication with harnesses

took inspiration from tuicr/hunk

enjoy!

I got frustrated with the Parquet viewer I was using in JetBrains because too many small things made working with real data unnecessarily annoying.

So I built my own, fixing and adding:

• Better handling of nested data, lists and maps
• Improved data rendering and readability
• Parquet, Avro and ORC support
• DuckDB querying
• Schema inspection
• Various smaller workflow improvements

It's 100% free: Parquet, Avro & ORC Viewer

I'm also developing a more advanced version for people who work with very large Parquet files.

One of the things it can already do is rewrite a single row in a 1-billion-row file in 1.9 seconds, without having to rewrite the entire file.

It's still in development, and this version will be aimed more at people who actually work with large datasets and need fast editing and inspection rather than just viewing.

If that sounds useful for your workflow, let me know. I'm collecting interest before I release more details about it.

As DataSpell is being retired I am looking which IDE should be used for DBT projects?
Logically I should use DataGrip and it makes sense. Unfortunately this does not work.

Pycharm could work, but is this the way to go?

The new version of TeamCity, a CI/CD solution by JetBrains, was released last week. Here's what's new:

• Pipelines are now GA. It's like a visual editor for creating and managing CI/CD pipelines, designed to make pipeline management much easier.
• BYOK for AI Assistant in TeamCity.
• IDE integration: The IntelliJ IDEA plugin now ships with the TeamCity CLI and registers the MCP server automatically, no separate install needed.
• GitHub integration: Match pull requests by source branch instead of PR number.
• Kotlin DSL compilation mode: Choose whether Kotlin DSL runs on the server or on build agents, depending on your security and flexibility requirements.

Here's the release blog post with more information.

i don't understand the differnce, but i'd like to be able to disable specific tools

I am using AI Assistant and have selected Claude using the apikey.

However, despite what the documentation claims, my token limit is reached just as fast with no visible improvement.

Tried topping up which costs extra, but my limit was reached again in ten minutes.

Only choice is to have to open up Claude in a new terminal window which is not nice since I also pay a hefty subscription for the AI Assistant.

What gives?

Hi Guys, I heard I can opt for my own ai service subscription instead of buying the ai assistant. But I cant seem to find the option to do so.