JBang for IntelliJ IDEA

The JBang plugin brings JBang scripts into IntelliJ IDEA while keeping JBang itself as the source of truth. It reads script metadata with jbang info tools and exposes dependencies and declared sources as project overlays. It exposes dependencies as project overlays and does not rewrite Gradle builds or Maven projects. Externally managed IntelliJ modules are left intact; the one narrow exception is a transient Kotlin support library for standalone K2 scripts, described in Architecture.

Highlights

  • Automatic synchronization after opening or saving a JBang root script

  • Explicit Sync JBang Project action with visible progress and detailed errors

  • Multiple root scripts with isolated classpaths and active-root switching

  • Resolution and navigation for //SOURCES and //FILES

  • Local and remote Maven coordinate completion for //DEPS

  • Directive, path, and catalog script-ref completion

  • Exact diagnostics for invalid directives, unresolved dependencies, and missing resources

  • Per-root //JAVA JDK registration and selection in standalone projects

  • Run and Debug configurations, gutter icons, and editor/project context actions

  • CLI-backed New > JBang Script templates

  • Java, Kotlin, Groovy, JShell (.jsh), and .jbang script recognition

  • JSON Schema support for jbang-catalog.json

JBang multi-root project in IntelliJ IDEA

How project integration works

Each JBang root has its own resolved metadata, dependency roots, declared source files, and requested Java version. The active root controls the classpath and JDK used for its included sources. Dependencies appear under External Libraries as synthetic JBang libraries; existing Gradle and Maven models remain untouched.

See Features for a visual tour, Usage for the complete workflow, and Installation for executable discovery and configuration.