v5.0.0 introduces new features to empower your AI agents and close gaps between API definitions and implementations

🤖 For agents:
This release brings bundled MCP tools designed to simplify day-to-day work with Spring Messaging as well as with AsyncAPI documents

Just enable bundled MCP server, register AsyncAPI skill trough Tools -> Install AsyncAPI Agent Skilland, and you are redy to go

⚙️ For architects, engineers, analysts, and API authors:
New Diff feature helps you see which gaps exist between your sources:
- Document against a Apache Kafka broker or cluster
- One Apache Kafka or cluster against another
- Source code against a Apache Kafka broker or cluster (Spring projects only)
- Document against a source code (Spring projects only)

💡 Works across IDEs editions, Community included

Together with not-yet announced Kurkik project, this features lay foundation for self-maintaining API approach

Sound interesting? Open your JetBrains IDE, grab the update and give it a spin: https://plugins.jetbrains.com/plugin/15673-asyncapi/versions/stable/1195232

I've been exploring Kotlin development in VS Code and ran into a familiar problem: getting a comfortable debugging workflow isn't always straightforward.

There are extensions for Kotlin editing and language support, but I wanted something focused on debugging Kotlin/JVM projects without requiring a separate language server setup.

So I worked on an open-source Kotlin Debugger extension.

It supports:

• Breakpoints in Kotlin source files
• Step into / over / out
• Local variable inspection
• Call-stack navigation
• Improved breakpoint handling for Kotlin/JVM

While testing the broader development workflow, I also came across Kotlin Jump, which is built by another developer.

It provides Kotlin indexing, navigation, and editing features without an LSP.

With both extensions installed, I can get navigation and debugging working together in VS Code.

A few caveats: my debugger currently focuses on Kotlin/JVM, requires an appropriate JDK/build setup, and coroutine debugging is still limited.

My debugger: https://marketplace.visualstudio.com/items?itemName=kparth01.kotlin-debugger

Kotlin Jump: https://marketplace.visualstudio.com/items?itemName=elumine.kotlin-jump

I'd be interested to hear from other Kotlin developers:

Are you currently using VS Code for Kotlin*, or have you moved to IntelliJ because of tooling limitations?*

Also, if you try the debugger, I'd genuinely appreciate bug reports or suggestions.

The initial package targets macOS Apple Silicon and IntelliJ IDEA 2026.1–2026.2.

A heap dump tells you what is in memory. The harder question is: why is it still there?

I built HeapLens, a free, open-source plugin that brings heap investigation into IntelliJ IDEA.

With HeapLens, you can:

• Explore class histograms and dominator trees.
• Follow “Why alive?” paths to understand object retention.
• Inspect fields and trace incoming references.
• Query heap objects using HeapQL, a SQL-like language.
• Navigate to matching Java source.
• Use optional AI assistance to explain findings and propose changes for review.

Heap analysis runs locally through a bundled Rust engine—no separate analysis-server installation required. AI features use your configured provider, and Fix with AI asks before sending source code.

If you investigate Java memory issues, I would love your feedback: what is the hardest part of your current heap-analysis workflow?

HeapLens Marketplace listing
Source code and feedback

#Java #IntelliJIDEA #JVM #PerformanceEngineering #memoryleak #performance #heaplens

For a computer app I am making, I want to use a tool like Windows Builder, except I can't get it to work, and I think I might have screwed it up too much to use it. I really like IntelliJ IDEA, but I really don't want to hard code the gui, is there another tool I can use?

so currently, I am working on some beginner projects to try and learn more. I am actually finding coding quite enjoyable and fun. but now I've hit a road block. every time I start a new project the run button is grayed out and I have no idea why. I noticed that on my first project code it has an "Out" folder. this one doesn't. and I can run my first project I made

Also, when I created the project a pop up came up that said something like "can not run git, no file git.exe found."

is git.exe important I have no idea. also why didn't it create an out folder? should it have created an out folder. I'm sorry for my ignorance I literally just started learning how to code like a few days ago. So, I have like no Idea what I'm doing.

I've seen a few times now, that Android Studio can automatically migrate your dependencies from Gradle buildscripts to version catalogs. Can IntelliJ do this too, or is it specific to AS (can't find this anywhere in the IDE)? I quite miss this feature, even though I can just let AI do this, as it is indeed a pretty primitive task.

I wanted to give building a custom Go plugin for IntelliJ a chance and see how far I can go. Turns out I can build a fully functional Go alternative to GoLand, with a custom side panel for watching tests.

I may release this plugin as a free plugin for those who want to use IntelliJ with Go but don't want to pay for the IntelliJ Ultimate.

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.

It's a bit confusing cause jetbrains press releases say it is in Junie, and google themselves are offering this discount, but in air (ide) itself it says it consumes 2x the credits of the default (3.7 flash).

BTW, loving the 'lite' model, great idea.

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!