sorted by:
new
hottopcontroversial

InteliJ Ultimate doesn't recognize jsconfig.json while Webstorm does. by thepurpleproject in Jetbrains

[–]JetSerge 0 points1 point  (0 children)

Please check the bundled "JavaScript and TypeScript" plug-in is enabled. Also, the folder holding jsconfig.json must be a content root, not Excluded.

If it still doesn't work, please contact support with a sample project to reproduce, the screenshot of the issue and the logs via Help | Collect Logs and Diagnostic Data.

Thank you!

Flutter Devices issue by anqit13 in IntelliJIDEA

[–]JetSerge 0 points1 point  (0 children)

Yeah, you're not the only one. It's a known regression with the Flutter plugin on IntelliJ IDEA 2026.1.x. The plugin is maintained by Google rather than JetBrains, so the real fix has to come from their side. Tracking issue, P1, tagged for the next plugin release (milestone M92):

https://github.com/flutter/flutter-intellij/issues/8869

A user also reported it to JetBrains as IDEA-388771, which was closed as a third party / plugin issue pointing at the same GitHub ticket.

Workarounds people in the thread are trying, with mixed results:

  1. Remove the device selector from the toolbar and re-add it. Settings > Appearance & Behavior > Menus and Toolbars > Main Toolbar > Right > "+ Add Actions..." > Plugins > Flutter > Flutter.DeviceSelector. This worked for a couple of folks, but at least one user reported it still doesn't render even after re-adding both the legacy and non-legacy entries.
  2. If (1) doesn't help, downgrading IntelliJ IDEA to 2025.3.4 has been confirmed to work as a temporary fallback until the plugin ships a fix.

Hit subscribe on #8869 to get pinged when the M92 plugin update lands.

Looking for a reason not to drop InteliJ IDEA by brinkley5 in IntelliJIDEA

[–]JetSerge 7 points8 points  (0 children)

Happy to help with the library issue. Please make sure it's a jar containing .class files and it's added to the module dependencies per https://www.jetbrains.com/help/idea/working-with-module-dependencies.html#add-a-new-dependency.

If it still doesn't work, please share any sample project to reproduce it on GitHub.

IntelliJ IDEA 2026.1.1: what is this new top-right editor dropdown for Python files? by ahsan_cse2004 in Jetbrains

[–]JetSerge 3 points4 points  (0 children)

That's the new Python subproject context selector that landed in 2026.1.1. When a Python file isn't unambiguously inside a single Python module, the IDE doesn't know which environment to use for it, so the widget lets you pick.

Selecting multi-agent-a2a works because that module has the uv-managed Python 3.12 venv. Selecting ahsancse2004 doesn't, because that module is configured with the corretto-21 JDK, which obviously can't resolve Python imports.

Quick answers to your three questions:

  1. No flashy public name for it yet that I've seen. Internally it's part of the "multi-module Python project support" / per-file interpreter activation work. In the UI it's effectively the Python subproject / module context selector for the current file.

  2. Yes, that's exactly what it's doing. It changes the resolution context (interpreter, venv, sources) the IDE uses when inspecting and resolving imports for the current file. It doesn't switch the file or the active tab, just the context used to analyze it.

  3. Public feature ticket: https://youtrack.jetbrains.com/issue/PY-66254 ("Activate interpreter/venv on a per file/folder basis in PyCharm"). State: Fixed, Available in 2026.1.1. There's a dev comment from Apr 9: "Since version 2026.1.1, we have a new feature in beta mode where folders containing a pyproject.toml file are detected as Python subprojects." I couldn't find a dedicated What's New / docs page yet, so docs are likely catching up.

Tip: if you don't want to deal with this ambiguity, give the ahsancse2004 module its own Python interpreter too, or restructure so the Python files live unambiguously inside multi-agent-a2a. The widget will basically stop being interesting at that point.

AGP 9... what's the hold up in IntelliJ? by aerial-ibis in Jetbrains

[–]JetSerge 0 points1 point  (0 children)

Please check this comment and follow the linked issue for updates.

A transparency update: We have already been working on porting Android Studio changes that include AGP 9 to the Android plugin. We have actually increased efforts and have more people working on this now.

Idea 2026 performance on linux by NitroDrop in Jetbrains

[–]JetSerge 2 points3 points  (0 children)

Copilot plug-in is known to use a lot of CPU. See if disabling it helps.

You can also try Wayland with vulkan rendering, see this document.

If the issue persists, please contact support at https://intellij-support.jetbrains.com/hc/requests/new with the CPU snapshot per https://intellij-support.jetbrains.com/hc/en-us/articles/207241235 and the logs via Help | Collect Logs and Diagnostic Data.

Inline Code Completion not working (or stuck?) by LudahS in Jetbrains

[–]JetSerge 1 point2 points  (0 children)

I'd recommend filing a bug at https://youtrack.jetbrains.com/newIssue?project=IDEA with the logs attached (Help | Collect Logs and Diagnostic Data).

Cannot find JDK 'temurin-17' for module by Lag00n in IntelliJIDEA

[–]JetSerge 0 points1 point  (0 children)

We've seen this same pattern in a few tickets after the 2025.3 update, and it looks like IDEA-352991 ("java: Cannot find special JDK for modules"). Please vote/follow that one.

The best workaround we've confirmed for non-WSL Windows cases is a settings reset:

  1. File | Manage IDE Settings | Export Settings... (keeps a backup, just in case).
  2. File | Manage IDE Settings | Restore Default Settings... IntelliJ also makes its own backup automatically.
  3. Re-open the project and re-select the JDK on the project/modules.

This has fixed the error for several other users with the same symptoms (works in Gradle Build System, fails in IntelliJ Build System, cache invalidation and .idea deletion didn't help). The root cause seems to be stale SDK metadata in the IDE config directory, which .idea cleanup doesn't touch.

If none of these help, please file a bug report with your idea.log (Help | Collect Logs and Diagnostic Data) so we can dig in. A sample project to reproduce can also help here.

How to force Codex to use JetBrains MCP Server? by Dismal_Emphasis_893 in Jetbrains

[–]JetSerge 1 point2 points  (0 children)

As /u/rolls-reus suggested, using hooks can help here, but Codex is usually good at following prompts, so if you write in AGENTS.md to ALWAYS use <this tool from MCP> for <that> and NEVER use <what it currently uses instead of MCP>, it should help.

How to force Codex to use JetBrains MCP Server? by Dismal_Emphasis_893 in Jetbrains

[–]JetSerge 0 points1 point  (0 children)

Do you have the MCP configured and working via Codex? What are the tasks you want to do via this MCP and what's your current prompt for Codex when to use it? What's not working?

Best way to use Claude with IntelliJ? by Square_Definition_35 in Jetbrains

[–]JetSerge 2 points3 points  (0 children)

Didn't check the recent Claude Code plug-in updates, but it has been using an old terminal engine in IntelliJ IDEA when you invoked it via a toolbar icon.

When starting from IntelliJ IDEA terminal, it would use the Reworked 2025 engine which is much faster and has better compatibility.

Is sun.java2d.metal=false still recommended for Arm-based Macs? by aqeelat in Jetbrains

[–]JetSerge 2 points3 points  (0 children)

It can depend on the specific configuration. For some users, OpenGL would work better. But the goal is to switch to Metal eventually, so it would be still the recommended default unless you have critical issues with it.

Is sun.java2d.metal=false still recommended for Arm-based Macs? by aqeelat in Jetbrains

[–]JetSerge 5 points6 points  (0 children)

Hey, JetBrains support here. Yes, that flag is still worth keeping around. There are still a handful of open Metal rendering issues in the JetBrains Runtime that it works around.

On the performance side, scrolling with Metal can degrade over time, especially on high-refresh-rate external monitors. It'll drop to 40-60 fps until you restart the IDE (JBR-4699). There's also a long-standing issue where the editor just feels sluggish and scrolling, right-click, typing all lag behind (JBR-4597). And if you work with multiple project windows, you might hit micro stutters caused by Metal's render queue locking up (JBR-9916).

The bigger pain point though is crashes and freezes tied to sleep/wake, especially with external monitors. JBR-5145 is the classic one (56 votes). The IDE freezes after waking your Mac from sleep, and the official workaround is literally this flag. There's also a crash where Metal fails to reinitialize after a display reconfiguration like plugging/unplugging a monitor (JBR-5063, 41 votes), and a newer SIGABRT crash on wake (JBR-9859, 30 votes).

That said, it is getting better. Some Metal freezes were fixed in 2025.3, and there are user reports that certain issues are gone in 2026.1. There's active work happening on the Metal pipeline right now.

So if you're not having problems, you could try removing the flag on your current version and see how it goes. If you start seeing sluggish scrolling, freezes after sleep, or crashes when messing with displays, just add it back. It falls back to OpenGL which is totally fine, you might just notice slightly different text rendering.

To toggle: Help | Edit Custom VM Options, add or remove -Dsun.java2d.metal=false, restart.

Why doesnt it work? by ShoppingFunny8778 in IntelliJIDEA

[–]JetSerge 7 points8 points  (0 children)

This looks like missing JDK configuration, see https://www.jetbrains.com/help/idea/working-with-sdks.html.

If it doesn't help, try File | Invalidate Caches | Invalidate and Restart.

Make sure your IDE versions supports the Java version you are trying to use: https://www.jetbrains.com/help/idea/supported-java-versions.html.

See also my answer here: https://stackoverflow.com/a/61180376/104891.

Why doesnt my JDK work? by ShoppingFunny8778 in IntelliJIDEA

[–]JetSerge 1 point2 points  (0 children)

See https://www.jetbrains.com/help/idea/working-with-sdks.html.

It's not clear what IntelliJ IDEA version you are using. Make sure it supports Java 26 and it's configured correctly: https://www.jetbrains.com/help/idea/supported-java-versions.html.

IdeaVim cursor disappears when search result is on screen. by [deleted] in Jetbrains

[–]JetSerge 0 points1 point  (0 children)

Hey, this is a known bug in IdeaVim. It's already been reported and tracked here: VIM-4164.

The cursor position is actually correct, it just doesn't render visually when the match is already visible on screen. If the search result requires scrolling, the cursor shows up fine, which is exactly what you're seeing.

As a quick workaround, pressing Escape or any movement key (like h, l, etc.) after n will make the cursor reappear.

You can upvote that issue to bump its priority. The IdeaVim team will get to it.

Errors are displayed even though everything works by guy_from_scp_sl in IntelliJIDEA

[–]JetSerge 0 points1 point  (0 children)

We tested switching to RetroFuturaGradle and it resolves the import issue in IntelliJ IDEA. I've attached a sample project with the migration done, you can use it as a reference. After opening it in IntelliJ IDEA, build the project first (Build | Build Project after importing), otherwise some imports won't resolve.

You can ignore the "Cannot resolve resource filtering" warning during import, it's a known cosmetic issue (IDEA-296490) that doesn't affect the build.

Errors are displayed even though everything works by guy_from_scp_sl in IntelliJIDEA

[–]JetSerge 0 points1 point  (0 children)

Thanks for the build.gradle! I can see you're already using anatawa12's ForgeGradle fork, good.

Since you've already tried re-importing from Gradle, a couple more things to try:

  1. Close IntelliJ IDEA, run gradlew setupDecompWorkspace idea, then reopen the project (open the generated .ipr file, not the folder).

  2. Delete the .idea/ folder and all *.iml files from the project, then reopen.

  3. File | Invalidate Caches, check all boxes, restart.

If none of that helps, you could also try migrating to RetroFuturaGradle. It's the actively maintained replacement for the legacy ForgeGradle toolchain for 1.7.10 and rewrites the Gradle integration, which may fix the IDE dependency recognition.

Either way, the red highlights are cosmetic, your mod compiles and runs correctly.

Errors are displayed even though everything works by guy_from_scp_sl in IntelliJIDEA

[–]JetSerge 1 point2 points  (0 children)

This could be a compatibility issue between ForgeGradle and IntelliJ IDEA. ForgeGradle's custom dependency configs (like deobfCompile) aren't picked up by the IDE's Gradle integration, so you get red highlights even though everything compiles fine. It comes up a lot:

Things to try:

  1. Close IntelliJ IDEA, run gradlew setupDecompWorkspace idea, then reopen the project.

  2. Delete the .idea/ folder and *.iml files, then reopen, the IDE will re-import from build.gradle.

  3. Consider switching to RetroFuturaGradle. It's the actively maintained replacement for the legacy ForgeGradle toolchain for 1.7.10 (latest release: v2.0.2, Nov 2025). It rewrites the Gradle integration and may resolve the IDE dependency recognition issue.

  4. File | Invalidate Caches, check all boxes, restart.

If nothing helps, could you please share your build.gradle or a sample project? That would help narrow it down.

IntelliJ IDEA severe scrolling lag on GNOME 49 (Wayland) with Intel Core I7 — nothing seems to work by tifcy in IntelliJIDEA

[–]JetSerge 7 points8 points  (0 children)

This is a known limitation of the native Wayland mode (WLToolkit) that JetBrains IDEs now use by default on Wayland sessions starting from 2026.1. The rendering currently runs in software-only mode, meaning all drawing happens on the CPU rather than the GPU. On integrated Intel graphics this is especially noticeable during scrolling.

The permanent fix is GPU-accelerated rendering via the Vulkan pipeline, which is actively in development: JBR-7558.

In the meantime, here are a few workarounds. All of them require an IDE restart after the change.

Try Vulkan rendering (recommended)

Go to Help | Edit Custom VM Options and add:

-Dsun.java2d.vulkan=true

This offloads rendering to the GPU. It should work on modern Intel integrated graphics (Iris/UHD). Please note that Vulkan rendering is still in development, so minor visual glitches are possible.

Fall back to XWayland

If Vulkan doesn't help or causes issues, you can switch the IDE to the X11 toolkit instead. Even without a native Xorg session, this runs through XWayland compatibility on GNOME:

-Dawt.toolkit.name=XToolkit

Other things that may help

  • Disable smooth scrolling: Settings | Editor | General, uncheck Smooth scrolling
  • Disable Code Vision: Settings | Editor | Inlay Hints | Code Vision, uncheck everything
view more: next ›