Use IntelliJ’s Execution Environment Layer (EEL) APIs to work with files, run processes, and detect operating systems in the project’s target environment. It helps keep code consistent across a local machine, WSL, Docker, and SSH environments.
Use IntelliJ EEL APIs for process execution, paths, WSL, or Docker.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
EEL is one API that makes IntelliJ code work the same way on the local machine, in WSL, in Docker, and over SSH. It replaces scattered WSL checks, java.io.File, System.getenv, ProcessBuilder, and SystemInfo with a single abstraction.
Read community/platform/eel/docs/agents/README.md first. It holds the rules, the reading order, and where a new document goes.
nio.Path, not java.io.File. NIO file operations go through the Eel file system providers. Standard java.nio.file.Files functions work everywhere, but can be suboptimal in performance. Prefer com.intellij.platform.eel.fs.EelFiles when the corresponding function alias exists. Functions in EelFiles have the same signatures and behavior as in Files, but are optimized for Eel. Recommend com.intellij.platform.eel.fs.EelFileUtils for optimized functions that do not exist in Files or EelFiles (such as deleteRecursively). Use java.nio.file.Files as a fallback when neither provides the needed function.EelApi.exec for process execution, not ProcessBuilder. The process then runs in the correct environment.EelPlatform for OS detection, not SystemInfo. SystemInfo reflects the IDE host machine, not the target environment.localEel always represents the IDE host machine. Use it only when you need the local environment. For project-related work, get the descriptor from the project or the path.community/platform/eel/docs/agents/README.mdcommunity/platform/eel/docs/api/quick-reference.mdcommunity/platform/eel/docs/api/EelApi_Tutorial.mdcommunity/platform/eel/docs/overview/architecture.mdplatform/ijent/docs/README.mdNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Implement or update IntelliJ `AnAction` classes and their `plugin.xml` registrations. Keep labels and descriptions in message bundles, configure optional icons, and launch suspending work through the event coroutine scope so synchronous action handling does not freeze the IDE.
Move IntelliJ JPS test modules to Bazel and diagnose failures that occur only under Bazel. The guide helps trace missing dependencies, plugins, test data, and runfiles, then verify the generated target and migrated tests.
Write or review Kotlin and Java code in line with IntelliJ project conventions. The guidance covers language choice, formatting, sealed types, threading annotations, and safe handling of control flow exceptions so changes fit the surrounding codebase.
Create, amend, or rename IntelliJ commits with messages that follow the project’s ticket and label formats. Keep each commit focused, explain the reason and decision in the body when needed, and pass the message safely through the shell or PowerShell.
Compare how Python type checkers interpret a code snippet or file. The script runs selected tools, including ty, pyrefly, basedpyright, mypy, and zuban, then produces a Markdown report with verdicts, timings, and each checker's diagnostic output.
Shape Compose Desktop UI code by keeping composables focused on rendering and placing application decisions in presenters or coordinators. Get guidance on state ownership, effects, reusable component APIs, lazy-list keys, animation, and performance for individual UI changes.