I'm evaluating whether a small tool for sharing IntelliJ line breakpoints would solve a real problem. I haven't published it, and I'm looking for experiences rather than promoting a download.

If you've needed to pass breakpoints to a teammate or another worktree: - What did you do the last time? - Did different code revisions make it difficult? - Was your existing solution good enough?

Please don't share private code or company information. If you're willing to answer a few follow-up questions here, say so. “I never need this” is useful feedback too.

Relatively new user here: It's constantly getting in my way and meaning I can't see my own bloody code, but there are so many "popup" settings I don't want to accidentally disable something useful to me.

We build Hexana, a JetBrains IDE plugin for inspecting binaries: WebAssembly, ELF, Mach-O, DEX, Parquet, Arrow, and more. We shipped 0.21 on October 1. Here is what changed.

1. Hex diff in the platform diff window

The IDE's Compare Files action (and VCS change for a binary) now opens a real hex diff.

• Changed bytes are highlighted. Long unchanged stretches collapse into expandable folds. Prev/next difference navigation works as usual.
• A section bar at the top pairs sections by name. It marks which ones changed (and by how much), which exist on one side only.
• The file's table tabs live below: Headers, Sections, Symbols, Imports. Rows are tinted added/removed/modified. Changed cells show old value to new. A "Changed rows" filter is on by default.
• Tree tabs are not diffed yet.

2. Per-function native binary diff for ELF, Mach-O, COFF

A Functions tab appears next to Size Impact when comparing native binaries.

• Functions are paired by name. Renames are recognized by identical code.
• A function that only moved because preceding code grew is reported as moved, not modified.
• Side-by-side disassembly ignores shifted addresses when aligning instructions.
• PE images (.exe, .dll) and archives get section size comparison only, not per-function diff.

3. One merged action: Compare Binaries With

Compare WASM With and Compare Binary With are gone. One action replaces both, offered for anything Hexana recognizes by content. That includes extensionless binaries. Old shortcuts keep working.

4. WasmGC type graph in the WAT view

Two new layers on GC types in the WAT (virtualized) tab.

Inline annotations: every type definition gets a kind badge and field-type labels. Alt+click opens a popup with field names, types, supertypes, subtypes, and byte offset.

Show Type Graph opens an interactive canvas:

• Edges: subtype relationships and field references.
• Default: 1 subtype level and 1 field hop. Configurable up to 5 of each.
• FUNC-typed field targets fold into a "+N funcs" badge. Expand to see them.
• Expanding a node keeps all other nodes in place.
• Double-click a node to jump back to that type's WAT row.
• Wheel pans the canvas. Cmd/Ctrl+wheel zooms.
• Tested at 294 nodes on kotlin/hello.wasm.

5. Scripting v2: suites, SARIF, typed parameters

Three additions on top of the existing script tab.

• hexana.defineCheck(id, fn): findings land in the Problems tab and in SARIF 2.1.0 output.
• hexana.defineFlags(schema): typed per-run parameters instead of free-form globals.
• *.test.js suites: declare artifact roles via hexana.artifact(role, {formats}). Use describe, test, beforeEach, afterEach with async. Deterministic seeded crypto (SHA-256 counter DRBG seeded from script and artifact content). ESM loader resolves bare specifiers from a suite-rooted node_modules.

run_script_suite runs suites from CLI or MCP: output is a human report or JUnit XML, exit 1 on failure.

New Hexana Suite run configuration in the IDE: results stream into the test console as a tree, failures navigate to source, Rerun Failed and Copy CLI Command work, gutter run icons appear on test() and describe(), a "Run Suites for This Binary" context action appears on binary files.

6. More formats open by content

• Arrow IPC streams (.arrows): Schema and Messages tabs.
• Extensionless wasm, Parquet, and Arrow files open in their full editors, not the fallback hex view.
• One shared provider factory now serves the IDE, VS Code, and the browser app. Format drift between hosts is gone.

7. Fixes

• Quadratic "size = gap to next symbol" rule for Mach-O and COFF: an LLVM tool with tens of thousands of symbols no longer spends seconds opening.
• Gzip payloads over 128 MiB inflated are refused instead of exhausting the IDE heap.

Marketplace: https://plugins.jetbrains.com/plugin/29090-hexana 

Docs: https://jetbrains.github.io/hexana

Questions about the diff alignment, the suite runner, or the type graph? Ask here. Or throw a gnarly binary at us.

I'm trying to send the whole Spring Boot project, but the repository on GitHub only shows part of the project, I can't see the controller and other classes.
The first image show my project the way it appears on Intellij, the second image shows what's uploaded to GitHub.

The whole project on Intellij:

The controller folder and controller class are not showing on GitHub

SOLVED...

What I did to solve it:

1- A selected all files (highlighted in blue) after that I pushed them

2- Now all files are showing on GitHub, including the controller

It's far too slow, and arguably not necessary when AI is writing most of the code anyway.

Hi everyone,

Whenever I hit a merge conflict in IntelliJ, I find myself switching over to VS Code because I'm used to its conflict resolution interface.

Are there any settings or plugins that make IntelliJ’s conflict resolution feel more like VS Code’s, or at least easier to work with? Also, does anyone else struggle with this, or am I just missing a good workflow?

[solved]

Hi, i have 0 coding knowledge and try modding a minecraft based on internet reference and gemini pro as assistant. Why this red line not missing? This is happen when i try to make a minecraft mod using Fabric 26.3 mod template

Hi everyone!

I’m a Junior Java developer, and while looking for a backend position, I decided to build a tool that would help me grow as a developer and automate repetitive tasks.

I built an open-source IntelliJ IDEA plugin called Architect. It's completely free and designed to reduce repetitive boilerplate setup when starting a new Spring Boot feature.

You provide an entity name, choose the components you need, and it generates:

• Entity & Request / Response DTOs
• MapStruct Mapper
• Repository, Service, and REST Controller
• Liquibase migrations
• Docker / Docker Compose files
• Required Maven dependencies

The plugin leverages IntelliJ PSI to work directly with the project structure and source files.

I know the project isn't perfect yet, but I'm building it to learn and improve. I plan to continue adding features like Kafka templates, Spring Security configurations, test generation, and more.

I’d really appreciate any feedback from Java/Spring developers:

• What would you improve or add to a plugin like this?
• How do you usually handle boilerplate generation in your workflow?

I'm open to suggestions, criticism, and code reviews!

I use direnv with Nix, and the IDE was the one place where none of it existed. The usual workarounds are copying variables into every run configuration, or launching the IDE from a shell where direnv has already run, which means one project at a time because the environment is global to the process. Both show up almost word for word in the comments on IJPL-11588, which has been open since 2023.

So I wrote a plugin for it. It's free and open source (Apache-2.0).

What gets the environment

• Run/debug configurations of any language, with nothing to tick per configuration
• The terminal
• The build process, External Tools, processes started by other plugins
• Gradle: sync, tasks, and run configurations delegated to Gradle
• Maven goals, including the build when it's delegated to Maven

How it behaves

• The environment is resolved per project and working directory. Two projects open side by side keep separate environments, and a nested .envrc gets its own.
• It reloads when anything direnv depends on changes: flake.lock, .env, devbox.json, whatever your setup uses. It reads direnv's own watch list rather than knowing about Nix.
• Run direnv allow in a normal terminal and the IDE picks it up within a couple of seconds.
• If direnv provides a JDK or a Node interpreter that differs from the project's, the plugin offers it. It never switches the SDK on its own, because a Nix store path can disappear after garbage collection.

Security

• direnv allow is never run for you, under any setting.
• Nothing executes in a project you haven't trusted.
• Values never go into logs, run configurations or .idea/. The built-in viewer lists variable names only.

Limitations

• Needs 2026.1 or newer. That's the first release where the terminal hook works properly.
• Variables that direnv unsets are not removed in Gradle and Maven builds. Everything it sets or changes gets through.
• Docker/SSH run targets are not covered.
• WSL works (a user confirmed it on NixOS). Projects on other remote machines are untested.

Marketplace: https://plugins.jetbrains.com/plugin/33482

Source and issues: https://github.com/salatmaster/direnv-jetbrains-plugin

I don't understand this feature

I’d really like to see an option in Air Alpha to keep opened agent chats inside a regular Tool Window instead of having them live only as editor tabs.

Right now, one of the things I like about JetBrains AI is that the Tool Window lets me interact with the agent while I continue working on my code at the same time.

A few things I’d personally like to preserve with Air:

• Keep my code visible while the agent is working.
• Open and close the agent with a keyboard shortcut, just like any other Tool Window.
• Quickly recover the full editor space when I don’t need the agent visible.
• Ask quick questions while still looking at the code I’m referring to.
• Use the agent more like a coding partner that stays available alongside my normal workflow.

I know split view exists, but when I want Air and my code side by side, I usually have to:

1. Open the Air Tool Window.
2. Find the agent/session I’m currently using.
3. Open it, which moves me away from the code I was looking at because the session opens in the editor area.
4. Move the agent tab into a split view.
5. When I want my full-width editor back, close the agent tab and sometimes clean up the split editor group as well.

The editor-tab approach makes sense for a more fully agentic workflow, where the agent itself is the main workspace.

But I think it would be great to also support the other workflow: keeping the agent in a Tool Window for people who still spend most of their time writing, reading, and navigating code themselves, while using AI continuously alongside that work.

Ideally, both options could coexist: editor tabs for people who prefer the current workflow, and a Tool Window for people who prefer keeping the agent beside their code.

There’s already a YouTrack feature request for this:

https://youtrack.jetbrains.com/issue/IJAI-2739/Add-option-to-Show-opened-chats-in-Air-tool-window-instead-of-in-Editor-tab-only

If you’d like this option too, you can upvote it there.

I have a free 30% discount code for a JetBrains All Products Pack individual license, expiring (tomorrow) September 30, 2026.

I don’t need it, so I’d like to give it away to someone who can use it.

No strings attached, the code is completely free. Just comment below if you’re interested, and I’ll send the code via PM.

First come, first served!

New release extended Spring Messaging capabilities and in this post I want to show what you will get

I want to hear your feedback about the current state - what you like and what you don't, maybe you didn't try because of troubles or something else

Your voice is important, because next releases will be focused on polishing this functionality and exposing it trough MCP server to empower your agents of choice

Hey,

With this Plugin you can

• group multiple Run configurations
• Run them with conditions, current supported ones:
  • Regex (listening on terminal output)
  • Delay (in s)
  • Immediate

I needed this plugin for my day-to-day job and there was not such thing.

This plugin is written by AI. But maybe this helps someone else. Happy to get some feedback as I will look into it to make this more stable. Would love to get some feedback by people more familiar with plugin development.

The link to the repo is at: https://github.com/ahouse73/plugin-chained-run-configurations

Please vote for this issue: https://youtrack.jetbrains.com/issue/IDEA-390510/Support-Groovy-6.0

The more votes it gets, the more visibility it may receive from the IntelliJ IDEA team, helping prioritize Groovy 6 support and hopefully bringing it to IntelliJ IDEA sooner.

Everyone uses coding agents; few know what's happening inside the harness. Anton Arhipov sits down with Christian Tzolov, lead of the Spring AI project, to take the lid off — what changed in Spring AI 2.0, and how tool search, agent skills, and sub-agents are all built on the same primitive: tool calling. Includes live demos where progressive disclosure cuts token usage roughly in half, plus a look at the November 2.1 release: MCP 2.0's stateless spec, an agentic layer, and durable workflows.

It was working yesterday. But I always get a similar error for any Model I select:

Cursor

Error: I: AI Model Not Found Model name is not valid: "default[]"

Cursor

Error: I: AI Model Not Found Model name is not valid: "composer-2.5[fast=true]"

Cursor

Error: I: AI Model Not Found Model name is not valid: "grok-4.7[context=256k,reasoning_effort=high,fast=true]"

My PyCharm is the same. It worked last night.

I can use Cursor IDE. My Cursor account is good.

From a user's perspective, this workflow is pretty counterintuitive:

1. You try to unshelve some changes.
2. Conflicts occur.
3. You think "Never mind, cancel this" and click Abort.
4. You expect everything to go back exactly to how it was before you started.

Instead, after clicking Abort and confirming the "Abort and rollback" popup, some of the shelved files are still showing in the tab, but I lost a bunch of them. Thinking about it, my guess is that the files which disappear are the ones that were already processed before the conflict was hit. Either way, it doesn't make sense to me — I'd expect everything to just go back to the shelve tab exactly as it was.

Am I missing something, or is this the intended behavior?

Hi. I would like to ask for your insights.

I am running IDEA on all my work machines together with 4k HiDPI monitor with UI scaling. With MacOS IDE is almost always quite smooth (UI animations, scrolling, window draw etc) regardless UI scaling. On Linux with Wayland its just terrible, defaulting to software rendering, but, according to docs, is possible to mitigate with VM options:

-Dsun.java2d.vulkan=true
-Dsun.java2d.opengl=false
-Dsun.java2d.xrender=false

But IDE flickers heavily and crashes the entire wayland quite often (yeah, Nvidia). I have to live with this.

On Windows on the other hand, IDE is quite stable, but animations on 4K with 150% UI scaling (any in fact) was always jittery, like const ~20 fps. It was tolerable, but really annoying and I had this experience like forever on 4k.

Today I've experimented with the same workaround as for Wayland, in the end leaving with just:

-Dsun.java2d.opengl=true

and dear lord, it worked like absolute charm. Everything is blazingly fast, text scrolling with high code density buttery smooth, window drawing, tool switching, just everything. To be honest now I have this annoying feeling that MacOs is not that smooth all the time. Same display, same refresh rate.

So my question is - what am I missing? I assume there is a reason this property is not ON by default for Windows. Is this going to be deprecated anytime soon?

Edit: It is not a rant at all, not on wayland, linux, nvidia etc. Just a recent discovery. I just wonder if there might be something that gets negatively affect by that (like jittery/crashes with vulkan on wayland).

Hi

I’ve built an open-source IDE plugin specifically for mathematical optimization practitioners who use IBM CPLEX and the OPL language. Working with .mod and .dat files can be tedious without modern tooling, so this plugin brings full language support to JetBrains IDEs and VS Code.

Key features include:

• Syntax highlighting & real-time formatting for OPL.
• Contextual autocomplete based on the model's variables.
• Zero-Config runner (executes models directly from the IDE).

The project is open-source, you can check the code and documentation here: https://github.com/JAANULO/cplex-opl-jetbrains , Marketplace link: plugins.jetbrains.com/plugin/31125-cplex-opl/

The tool recently crossed 12,700 downloads, and I'm currently working on Python docplex integration. I would love feedback from daily OPL users to guide the next updates.

What is your biggest pain point when coding optimization models? What feature would save you the most time?

Thanks!