JetBrains IDE integration for the Elide runtime and build tooling.
Elide projects (elide.pkl) can be imported just like Gradle or Maven projects, and provide dependency info, structured
build and test output, CLI completion for custom run targets, and more.
- IntelliJ IDEA 2025.3 or newer (builds
253–262.*) - Elide CLI installed, or a distribution directory selected in project settings
- Optional: the Pkl plugin (
org.pkl) for manifest editor features
Add the Elide plugin repository under Settings → Plugins → ⚙ → Manage Plugin Repositories:
https://plugins.elide.dev/intellij
then install Elide from the marketplace tab. Plugin ZIPs are also attached to every GitHub release.
Project import. Directories containing elide.pkl are linked and synced automatically; manifest or lockfile changes
prompt a reload. The Elide tool window shows linked projects, their modules, and the build targets reported by the
CLI, runnable from the tree view.
Multi-project workspaces. A manifest declaring workspace.members is imported as one project: every member gets
its own modules, source roots, classpath and JDK, and a member consuming a sibling's artifact with project("name")
gets a module dependency on it — along with the siblings that artifact brings with it, the way Elide resolves the
classpath — so the IDE compiles and navigates across the workspace. The tool window nests every project's build
targets and source-set modules under that project, and only the root is linked — editing a member's manifest reloads
the workspace. Opening a member directory on its own still works, and points at the workspace above it.
Run configurations. Add Elide run configurations with command-line completion for entrypoints, CLI commands, arguments, build tasks and flags. Ad-hoc commands can also be run through Run Anything.
Gutter actions. Run and Debug icons on Kotlin/Java main functions and JUnit tests. When the Pkl plugin is also
installed, build icons also appear on artifacts entries in the project manifest, and declared entrypoints and scripts
will also gain Run and Debug actions. An artifacts entry declaring a binary Native Image offers Run and Debug of the
image itself alongside its build.
Build output. Runs report as a step tree with timings, skip reasons, and compiler diagnostics rendered with source
excerpts and navigable file locations. elide build reports to the Build tool window, other commands to the Run
window.
Test results. elide test configurations show a test tree with pass/fail/skip states, timings, output and
jump-to-source.
Coverage. Run with Coverage adds --coverage and loads the resulting JaCoCo and LCOV reports into the IDE's
coverage view, including runs started outside the IDE.
Debugging. Entrypoint and test configurations support Debug via Elide's JDWP support; the IDE attaches
automatically. Debugging elide test requires Elide 1.5.3 or newer and is available for JVM code only, for guest
languages use DevTools or DAP instead. Native Image binaries are also supported via GDB/LLDB through the JetBrains
Native Debugging Support plugin (IntelliJ IDEA Ultimate)
Manifest editing (requires the Pkl plugin). Completion and navigation for jvm.main and entrypoint paths, for
workspace.members directories, and for the project and artifact names a project("name").artifact("name") reference
or an artifact's dependsOn/from list carries. Renaming or moving a member directory rewrites the entry that names
it. Inspections report unresolved or invalid JVM entrypoints, members without a manifest, and references to projects
and artifacts the workspace does not declare.
Settings → Build, Execution, Deployment → Build Tools → Elide selects the Elide distribution per project:
Auto-detect (default) or a custom path. Auto-detection uses $ELIDE_HOME, then the standard install locations for the
platform. Run targets carry their own Elide Home field.
./gradlew buildPlugin # plugin ZIP -> build/distributions/
./gradlew runIde # sandboxed IDE with the plugin installed
make verify # descriptor checks + IntelliJ Plugin Verifier
tools/codegen.sh # regenerate the manifest model from Elide's Pkl schemaSee CONTRIBUTING.md for development setup and repository layout.
Releases are driven by release-please: run the Release workflow to open a release pull request, then merge it to tag, publish to the JetBrains Marketplace and the Elide plugin repository. Commits follow Conventional Commits, enforced by commitlint.
- CHANGELOG.md — release notes
- CONTRIBUTING.md — development setup and contribution workflow
- SECURITY.md — vulnerability reporting
- CODE_OF_CONDUCT.md — community expectations
- docs/PLATFORM_APIS.md — platform APIs the plugin uses
MIT (see LICENSE).