The Elide plugin connects Claude Code or Codex to the Elide installed on your machine. The agent discovers the project, builds one target instead of everything, reads test failures with file and line, finds untested code, reads your dependencies’ Javadoc and sources, and captures traces and logs while it runs a command. It uses structured tools instead of parsing terminal output.
- Claude Code plugin: project tools, the
elide-devskill, and build results pushed into your session. - Codex plugin: project tools, the
elide-devskill, and project context on every prompt.
What’s in the plugin
| Part | Claude Code | Codex | Does |
|---|---|---|---|
| Project MCP server | Yes | Yes | Starts elide mcp: project tools for builds, tests, coverage, dependency docs and telemetry. |
elide-dev skill | Yes | Yes | Teaches the agent the workflow: discover first, poll builds, read reports as evidence. |
| Build-result channel | Yes | No | Tells the session when a build finishes or a telemetry capture has results. |
| Context hooks | No | Yes | Adds short, project-aware guidance when a session starts and on each prompt. |
The plugin uses your installed elide. It does not install Elide, run builds on its own, or change your client’s
permissions: building, running code and downloading dependencies still ask for your approval.
Install
Install Elide and check that your agent’s shell finds it:
elide --version
Download elide-agent-plugin.zip from the latest release and
extract it to a directory you keep:
curl -fsSLO https://github.com/elide-dev/elide/releases/latest/download/elide-agent-plugin.zip
unzip -o elide-agent-plugin.zip -d ~/.local/share/elide-agent-plugin
The archive holds the plugin and a local marketplace for each client. Then install it in your client:
claude plugin marketplace add ~/.local/share/elide-agent-plugin
claude plugin install elide@elide-local
codex plugin marketplace add ~/.local/share/elide-agent-plugin
codex plugin add elide@elide-local
Start a session in your project directory and ask a question about it.
Examples
elide test fails on main. Find out why and fix it.
The agent calls project/context, picks the target with build/inspect, starts it with build/run, waits on
build/status, then reads build/diagnostics and tests/reports for the failing test, its file and line.
Which files under src/ have the least test coverage? Add tests for the worst one.
Show me the Javadoc for ImmutableList in the Guava version this project uses.
Run the checkout tests and show me every span slower than 250 ms.
The last one starts a telemetry capture with a filter such as signal == 'traces' && durationMs >= 250, runs the
tests through it, and reads back the matching spans.
Plugin or direct connection
Install the plugin, or connect elide mcp yourself as the project MCP server page shows,
not both: each registers a server named elide, and two copies duplicate every tool.
The plugin does not include the docs MCP server. Add it to search these docs and report problems from the same session:
claude mcp add --transport http elide-docs https://elide.help/mcp
codex mcp add elide-docs --url https://elide.help/mcp
Update and remove
To update, extract a newer elide-agent-plugin.zip over the same directory and reinstall:
claude plugin marketplace update elide-local
claude plugin update elide@elide-local
codex plugin add elide@elide-local
To remove it, run claude plugin uninstall elide@elide-local or codex plugin remove elide@elide-local.
The plugin’s version matches the Elide release it ships with. SHA-256 and SHA-512 checksums accompany the archive.