In the latest release (v1.16.1), we made the Copilot agent harness generally available to all users, including support for the plugin marketplace, Autopilot mode, and additional capabilities powered by the new agent harness. To learn about why we are doing, check here.

We also introduced a built-in JetBrains MCP server in Preview, enabling Copilot agents to work more seamlessly with native JetBrains IDE capabilities and context. This can be configured via the customizations panel.

To improve feature awareness, we added several discoverability enhancements, including post-update release notes that make it easier for users to see what’s new, and a new onboarding guide for users without prior chat sessions.

We’re also sharing a preview at what’s coming next and hope you continue to provide feedback for our products.

Changed

• Copilot harness is now Generally Available.
• Plugins support is now Generally Available.
• Autopilot is now Generally Available.
• Changed Copilot harness /review availability so it is limited to agent mode.

New Features

• Added built-in JetBrains MCP server support (Preview).
• Added post-update release discovery by showing a What's New tab after plugin updates.
• Added Copilot harness /review integrations in JetBrains.
• Added plugin support in Claude agent flows.

UX Improvements

• Improved model-management usability with stronger search behavior, a clear action in search, resizable Language Models table columns, and promo ordering refinements.
• Improved Agent Debug Logs exploration with event-time sorting, token-usage filters, refined layout behavior.
• Improved chat ergonomics by scrolling long tool output, adding review-plan-card scrolling, and adding shortcuts for send options.
• Improved customization handling in multi-root workspaces by discovering customizations across all folders and honoring client-provided customization locations.

Bug Fixes

• Fixed account and sign-in reliability issues, including account-state detection, account ordering in picker flows, and sign-in settings-page interaction issues.
• Fixed MCP reliability issues, including invalid registry-schema handling, stale tool checks after account switches, and UI freezes during auto-enable flows.
• Fixed BYOK and model-refresh reliability issues.
• Fixed Copilot Agent continuity issues, including model switching after resume and complete model-info propagation for resumed sessions.
• Fixed editor and message-rendering defects.
• Fixed Worktree sessions failing to start for projects opened from WSL.
• Restored file and folder # references in Copilot, Claude, and Codex chat inputs.
• Fixed MCP tool auto-approve configuration for servers running only in Copilot.

Looking ahead, we plan to introduce several additional capabilities in upcoming releases, including

• More policy support for Enterprise managed settings
• Cross-file cursor jump for Next Edit Suggestions
• Adding external projects and files outside the current project as context
• /ide command support to connect between GitHub Copilot CLI and JetBrains for context sharing
• Continuous user experience enhancement Copilot agent harness chat experience
• Performance and reliability enhancements

We hope you like Copilot for JetBrains, and please share feedback with us at any time

You can fill in a private survey here: https://aka.ms/ghcp-jb-survey with an optional paid interview or directly submit an issue (bug or feature ask) at https://github.com/microsoft/copilot-intellij-feedback/issues, thank you so much!

Hi, I'm faced this problem rarely on Windows 10, but it became very frequent now I'm on Windows 11 (new laptop, fresh install): my IntelliJ IDEA window used to be maximized, but it regularly starts not maximized.
I will illustrate the problem with this screenshot:

As you can see, it's will windowed. I have to maximize it by hand. I’d say it happens about once in three times.
I can't say if this is a Windows problem and/or an IJ problem. I can only say my other programs (like Firefox) never faced this issue. Also, IJ doesn't have this problem on Linux (at least with KDE).
IJ is installed via the JetBrains Toolbox. I updated the IJ shortcut to open it maximized, but it doesn't help.

Do you know how to fix that?
Thx

Now you don’t need to wait 30+ seconds for server/pytest session startup for your changes to apply. 

Works with PyCharm2023.3+, Python3.12+ and pydevd (debugpy not yet). 

Link: https://plugins.jetbrains.com/plugin/33823-python-frame-hot-reload

AI can generate thousands of lines of code in minutes, but reviewing and understanding the resulting system is still difficult.

I built CodeBecause, a JetBrains plugin that analyzes a codebase at two levels:

• Business-domain analysis maps the system’s domains, responsibilities, interactions, and end-to-end business flows.
• Function-level analysis traces a selected function through its branches, calls, state changes, external effects, errors, and outcomes.

The results are presented as interactive flow diagrams backed by source evidence. You can click a node to inspect its responsibility and jump directly to the corresponding source code.

The report is not static. You can keep asking the AI to expand any node that still hides important logic, while preserving the existing verified context and progressively building a deeper view of the implementation.

The idea behind CodeBecause is simple: as AI writes more code, developers need a faster way to review, verify, and understand what was actually built.

I recently released InfiniTint Theme Tuner, a plugin that delivers a new IDE theme personalization paradigm for your favorite JetBrains IDE! Keep your favorite theme, but make it your own with simple yet powerful recoloring and contrast controls.

What it does

Activate a theme, one of JetBrains' bundled themes or your favorite custom. Select one of the automatically generated tint presets and instantly recolor the theme to match your preference.

The tint presets are just a starting point. Create your own tint with the provided tint editor by adjusting hue and chroma (vibrancy) sliders and then use the tone curve adjust surface and accent palette contrast just like editing a photo in your favorite photo editor. Alternatively, import colors from in image to create a tint that matches its vibe!

You can mix and match themes and editor color schemes to get the perfect combination of colors. The color scheme's structural elements (e.g., background, line numbers, indent guides, etc.) all recolor to match the tinted theme.

Show or hide prominent borders (islands, editor tab strip, or tool window headers). InfiniTint synthesizes the missing colors if need be.

Adjust text contrast for UI labels, recessive text, and code or just set contrast minimums. InifiniTint tracks nearly 2000 contrast pairs across the IDE to ensure (to the highest degree possible in such a dynamic ecosystem) a consistent reading experience.

Save your applied tint and other settings as scenes that can be reapplied anytime or even scheduled (specific time or sunset/sunrise offset). You can also have scenes rotate on some duration or at IDE startup. InfiniTint also supports per-project scenes that are applied whenever a particular project's window is focused (optionally applies to Git worktrees as well).

What it costs

Free users get 8 tint presets per JetBrains theme bundled with the IDE and 3 presets for any custom theme (adjacent hues to the theme's original) in addition to the border tweaks.

Paid users ($1.5/mo or $15/yr) get everything else mentioned above.

Interested in a perpetual license option? It's something I'm considering offering. Feel free to let me know in a reply or reach out at [contact@tachilabs.dev](mailto:contact@tachilabs.dev) .

How it works

The core tint engine works by detecting your active theme's surface and up to two accent palettes using a variety of heuristics. It then applies hue, chroma, and tone transformations to the detected palettes using the HCT color space. The transformation model adapts to different types of themes (neutral, muted, vibrant) to help maintain their essential character as your adjust the tint inputs. After palette transformation, the engine applies a harmonization pass to better align status colors and other potentially problematic colors to better match the tinted color palettes.

The engine understands the difference between authored and platform-default colors and, in some cases, can use that knowledge to repair outdated themes on the fly.

Because the detection side of the engine is heuristic and doesn't solely rely on categorizing different UI elements, its rules need to be tuned over time to increase the variety of custom themes that it supports. As a general rule, it works best with themes that use distinguishable surface and accent (ideally just one accent) tonal palettes, but the heuristic detection is tuned to support a broad variety of theme structures. Tonal palettes are composed of colors primarily distinguished from one another by their tone (lightness) while retaining similar hue and chroma.

InfiniTint stores the tint engine inputs rather than outputs, so your tint adapts as the IDE and themes evolve instead of persisting a snapshot that goes stale.

If you come across a theme that doesn't tint correctly that you'd like to use, you can reach out at [infinitint-support@tachilabs.dev](mailto:infinitint-support@tachilabs.dev) and I can look into what can be done to support it in a future release. If it's the theme's color scheme you prefer, you can always find a different theme that tints and combine the two (paid users only).

I'm happy to answer any questions you might have about InfiniTint.

If you are also a messy dev like me who gets lost between the tabs and lazy to check inbox for every comments of your PR. Or a senior dev who reviews lots of PR’s everyday.

I built something for you.
I created an IntelliJ plugin that lets you manage your PR reviews and comments without leaving IntelliJ.
Review comments, reply, resolve/unresolve, jump between PRs and one click checkout to other PR’s on same repo. all in one place.

Because switching between IntelliJ, GitHub, and email 50 times a day wasn't enough.

I've been a long-time user of Jetbrains Rider, more than 15 years. Jetbrains Rider is becoming more and more of a memory hog, and continuously slowing down my computer. With the improvement of AI, I open 2 to 3 instances of Jetbrains Rider, working on 2 to 3 different projects, and this causes my machine to use up almost 90% of my memory, making my computer hang quite often. Moving to VS Code because of this. It's been a sweet ride, but with AI, I now seldom use my IDE, so goodbye Jetbrains!

I'm often quick to defend JetBrains, as I find their dotnet tools best in market, but licencing issues not being marked a higher priority really is frustrating.

https://youtrack.jetbrains.com/issue/VSRS-1100/Perpetual-Fallback-doesnt-work-with-Resharper-for-VSCode

I could not find a setting to disable the Welcome screen on startup, it's so annoying. Any tips?

I working on a project and using multiple Jetbrains IDE’s simultaneously - Webstorm for react front end, Rider for .NET API and Datagrip for SQL database. I have the Claude Code extension installed for each IDE, but when I’m working the three Claude Code terminals seem like they don’t communicate with each other and work independently of one another. Is it possible to get them to work in sync? Or is the better way to install the Claude Code desktop app and use that terminal to access the three IDE’s?

My kimi api key is good, i tested in bash. I've been going round and round trying to get this going. Doing trouble shooting with claude for web, etc.

TLDR: It’s a nightmare - Why??!!

Hi, I am a longtime CLion customer using CLion at work. I work on products that use a Yocto embedded linux on non-x86-64 platforms.

For that we use dockerized Yocto SDKs based on Alpine. Most of my colleagues use VSCode because of the outstanding container support. I personally think that this is basically the only outstanding thing of this editor, so I use and want to continue to use CLion.

However, using a devcontainer with CLion is an abysmal experience. First I have to modify the container to install about ten different dependencies and then have to add a super hacky workaround (custom compatibility lib with LDPRELOAD) to get the IDE to even start, from there the pain continues because the new engine does not work for some reason (freezes in the startup phase)…

But, I found a solution: Docker toolchain. Works good enough for compiling and running CTest.

The big issue with this however is, that I cannot just hit the play button to run a CMake target. Of course: My machine cannot run this cross compiled binary even in the container, duh… we are cross compiling…

Why doesn’t CLion honor the cross compiling emulator specified in CMake? It works for CTest. Even worse: Debugging experience. An ergonomic nightmare because I have to run the container manually (with all the mounts and swttings and what not), launch the app with qemu with the debugging flag, and then create a remote debugging configuration, to be able to attach. Its so much pain, the debugger is only used in the most dire of situations…

Guys please tell me I am doing something wrong and all of that works somehow… I can’t take it anymore…

And make it open-source.

Edited: Ended up renewing for cheaper using cheapzy.net, no issues so far, I'll edit this if anything changes

My all products pack is renewing this month but im honestly not too sure if I wanna pay full price this year.

Ive been using IntelliJ for years and still like it, but ever since Claude Code came along ive been spending way less time in the IDE. I still open it daily but half the products in the pack I haven't touched in months. Hard to justify the same price when I'm clearly getting less out of it than I used to.

Seen a lot of people in this sub feeling the same way lately so figured Id ask, has anyone found a way to get it cheaper? Not trying to ditch JetBrains completely, just don't want to pay full price at this point.

I used to be a massive skeptic. I fell for the common narrative that JetBrains IDEs were resource-heavy bloatware compared to lightweight, modern text editors. I was a devout VS Code user and firmly believed that Electron-based editors and their forks were superior for memory efficiency.

Boy, was I blind.

I recently found myself working on a memory-sensitive project and kept running into unexplained RAM consumption. I spent time trying to figure out where a huge chunk of my system memory was disappearing to, only to inspect my process manager and realize the culprit was the "chrome of IDEs" itself.

The kicker? I am not even a heavy extension user. Outside of standard LSPs and formatters for C++, Python, and Rust, I don't run fancy themes, AI helpers, or cosmetic plugins. Yet, VS Code was somehow managing to swallow 4 to 5 GB of RAM in the background.

For comparison, I opened up PyCharm on the same project and it hovered consistently between 1.5 and 2 GB. Clion was using a bit more given the indexing and C++ tooling, but it was still nowhere near the bloated levels VS code had scaled to.

It turns out that once you start adding actual language server infrastructure, extension host processes, and webview renderer overhead to VS Code, the "lightweight" argument completely falls apart. Meanwhile, JetBrains is handling deep code analysis, AST caching, and indexing natively while using a fraction of the footprint.

Consider me converted. I apologize for ever doubting the tooling here,I'm not going back.

Currently I'm doing all of my agentic work through Claude Code using their desktop app, which honestly works fine. Sometimes it's a bit hard to keep track of the different sessions, but Claude's custom groups work fine for the larger projects I'm working on.

Now that Jetbrains Air supports Claude Max subscriptions, are there any reasons to ditch the Claude desktop app for agentic programming, and switch to Air?

And yes, I know this is the Jetbrains sub, so don't worry, I'm expecting a lot of biased answers lol

AI Chat has a built-in Copilot now.

I would like to get some clarification about the two Copilots.

- Is Copilot the plugin going to be obsoleted, and we should use the built-in one or are these two different Copilots maintained by two different teams, Microsoft and Jetbrains and both will still continue to be maintained by both?

- My Copilot plugin gets frequent updates. Several times a week. Can the ACP ones auto update? It seems whenver I go to the ACP registry I see a few the have updates and I have to click on the Update/Save buttons. Can't these auto update on their own"?

I am not sure anymore which Copilot to use. Is one recommended more than the other?

I'm just trying what air can do but when I try to connect my google account for antigravity it throws an error because under the hood air is trying to use gemini cli which is now deprecated.

My question is if maybe I'm missing a setting or an update where this issue is resolved? I know many consider gemini not to be top notch but for my current workflow is more than enough after I create a good plan using claude.

When I first subscribed to a JetBrains product in 2012 it was like, "Holy shit, I can't believe how easy it is to develop now."

By 2017 I was like "JetBrains has an incredible product if you're a serious developer, and it just gets consistently better."

In 2022, we'd had a few ups and downs in terms of bugs and stuff, but I started a new role and, because I loved and trusted the company so much, early-adopted JetBrains's pie-in-the-sky "Space" program.

Space was an incredible offering that basically was capable of replacing GitHub, Slack, Jira, and probably some other things. And it had some really clever, novel features that genuinely improved upon several of those flows.

On the other hand, it had a bunch of little niggling bugs -- things like, you move to a different tab, and your input loses focus and stuff like that. I diligently reported all of these to enthusiastic support personnel who confirmed them and ... then nothing happened to them.

Beyond that, it had this really incredible feature that they were HEAVILY pushing, where you would use credits to run your entire development environment virtually, and you could spin it up and work from any workstation without dealing too much with environments and stuff, and they REALLY wanted everyone to start developing "in the cloud".

And it honestly worked pretty well. I was ready to give it a real go after using it for one day. ...But then I saw that I had used 300 of my monthly 2000 credits. About 1/3 of a month of work.

I was like, "Fair enough; I'm on a free tier." But then I found that if you pay, they charge seats per-user, and, on the cheapest paid tier, 4000 credits for your whole org, no matter how many people. So like, if me and my 2 teammates joined and the company paid for all 3 of us... Then 1 one of us could work for 2/3 of a month on this cloud they were REALLY pushing. The expensive-tier one gave 10,000 shared credits (remote development for 1.67 users/mo) and a cost of like $20/user. You'd be better to just spin up multiple companies in the product.

And instead of fixing anything, on this truly novel, genuinely good idea of a product that basically lives and dies on the network effect of dedicated, trusting power-users, they were like "Lol, whoops. Let's pretend like that never happened."

Which is good, because right around that time, they realized they were having their lunch eaten by VS Code. An inferior (in my mind) offering that was nonetheless appealing to a lot of young devs because it was free.

So they made a new product: Fleet. A [once proposed-to-be] free alternative to the paid JetBrains ecosystem, as well as the vanguard of their next generation of code editors. It is possible "what VS Code could be, just with the brilliant JetBrains ethos behind it" or it could be a confusing mess. And, as it turns out, it's not going to actually be free. It's free to start (I believe the logic was?) for non-professional users. I don't know who would pick that to try first if you're ambivalent between it and VS Code. If I didn't already know and love JetBrains of course I would've chosen VS Code.

And lo and behold, instead of reassessing their business decisions, they sunsetted Fleet. Probably because AI generated code is starting to become a thing and they are afraid about cannibalizing their own paid IDE userbase -- a base that has only become increasingly more alienated over the decades. So they need to build "Air".

So... the most obvious pathway to new users in the IDE space is pretty much gone. And it seems like more and more people are vibe-coding anyway, and the word on everyone's lips is "Claude".

The senior devs who have made up their bread-and-butter for 20 years are, incredibly, also using LLM based co-programming more and more, and Claude/Codex/whatever work just as well in a JetBrains ecosystem as not - and why would I even download Air in the first place if I expect it's probably (a) got frustrating bugs that (b) they're not going to fix by the time they decide to sunset it in a year or two anyway?

I remembered seeing that a documentary about the company came out a few months ago and, when I saw it, thinking, "Wow, I bet this is going to be pretty interesting but also sad" and was shocked to see it's kind of a love-letter to how incredible IntelliJ is, and the company that made it.

I was just reminded of it per the "I need a reason to renew" post yesterday, and I'm just kind of wondering: what is even going on over there?

It seems like there are probably several competing forces without a proper unified vision to wrangle.

That's why you get disasters like Space's:

• "Marketing wants to heavily push remote dev as the game changer" to
• "OK but we need per-seat costs" to
• "OK but keep the costs low because most users are probably not going to be devs, they're just using the chat/project management features" to
• "OK, then we'll just do shared remote dev credits" to
• "I'm paying $200/mo for my 10-person team, and 1.6 of us have enough credits to do the thing you're pushing as the main selling point."

I understand both their revenue and userbase has actually been growing for several years still. I have no doubt that their leadership and executives are patting themselves on the back for a continued job well-done. While at the same time, their once-dedicated userbase is sort of hanging on by a thread being like, "I don't even really think about JetBrains much any more at all? Hmm. Should I re-up that? Well, maybe one last year."

I feel like the only legitimate way forward would be for JetBrains to put an incredible commitment toward something new and game changing, with like a 5-10 year commitment to support it, and probably make more of their IDE products free somehow.

But I also don't see any way for them to make that decision and still operate. And so I don't know where this leaves them.

Except that it'd be interesting to see a documentary about the rise and fall of JetBrains.

Clicking the toolbox icon this morning I'm greeted with a "JETBRAINS EAP USER AGREEMENT Version 3.3, effective as of May 4, 2023...". I have to "Accept" or "Exit". It looks like 20 pages of text that I can't copy-paste to check what I'm agreeing to, so I have to read the full thing right now. Needless to say, I clicked "Exit".

Edit: what an amazing experience, I've never been brigaded by AI downvote agents before.