# IDE integration

> Work on Elide projects in VS Code, IntelliJ IDEA, Zed or any LSP or DAP editor: project sync, code intelligence, run, test and debug from the editor, and coding agents over MCP.

Elide projects open in VS Code and IntelliJ IDEA with their dependencies, source sets, run targets, tests and
debugger wired to the `elide` CLI. The Zed extension and other editors use `elide lsp` for Java and the Debug Adapter
Protocol to debug JavaScript, TypeScript and Python.

## Choose your editor

| Editor | Install | Guide |
| --- | --- | --- |
| VS Code 1.105+ | `code --install-extension elide-*.vsix` | [VS Code extension](https://elide.help/docs/vscode) |
| IntelliJ IDEA 2025.3+ | Plugin repository `https://plugins.elide.dev/intellij` | [IntelliJ IDEA plugin](https://elide.help/docs/intellij) |
| Zed | [Elide extension](https://github.com/elide-dev/zed) | [Zed extension](https://elide.help/docs/zed) |
| Neovim, Helix, any LSP or DAP client | `elide lsp`, `--debugger=dap` | [Other editors](https://elide.help/docs/connect-ide) |

## What each editor gets

| Feature | VS Code | IntelliJ IDEA | Zed | LSP or DAP client |
| --- | --- | --- | --- | --- |
| Project sync from `elide.pkl` | Yes | Yes | Classpath | Classpath |
| Kotlin code intelligence | Yes | Yes | No | No |
| Java code intelligence | Yes | Yes | Yes | Yes |
| JavaScript, TypeScript, Python debugging | No | No | Elide adapter | DAP |
| Run entrypoints and tasks | Yes | Yes | No | No |
| Tests in the IDE's runner | Yes | Yes | No | No |
| JVM debugging | Yes | Yes | No | No |
| Native Image debugging | GDB | GDB, LLDB | No | No |
| Coverage view | Yes | Yes | No | No |
| New project from a template | Yes | Yes | No | No |
| `elide.pkl` completion | No | Pkl plugin | No | No |

## In the editor

1. Open a folder with `elide.pkl`. The editor syncs its dependencies and source sets.
2. Code intelligence resolves project and library symbols, with library sources attached.
3. Run and debug entrypoints from code lenses or gutter icons; runs go through `elide run`.
4. Tests run through `elide test` and report per test in the IDE's test view.

## Related

- [Debugging](https://elide.help/docs/debugging): CDP, DAP and JDWP debuggers for every language.
- [Agentic engineering](https://elide.help/docs/agentic-engineering): `elide mcp` and the docs MCP server for coding agents in your editor.
- [Project setup](https://elide.help/docs/projects): the `elide.pkl` manifest the editors read.