Enclave Extensions

Community tool and feature extensions for Eclipse Enclave, the Docker sandbox for agentic coding tools.

Enclave has a small set of built-in tools and features. This repo is for everything that lives outside core: experimental agents or features, or extensions that are too niche to be built in.

Install

Enclave installs extensions straight from a git repository.

enclave tools add eclipse-enclave/enclave-extensions

With more than one tool in the repo, add lists what it found and asks which one you meant. Skip the question by naming it:

enclave tools add eclipse-enclave/enclave-extensions --name <extension-name>
enclave --tool <extension-name>

Features install the same way with enclave features add, and are enabled per session with enclave --features +<extension-name>.

Before writing anything, add prints what the extension can do: root install steps, install and startup scripts, network changes, declared credentials, files seeded into your project, host commands. Read that summary. An extension is code that runs at container build and start time, and a host command runs outside the sandbox with your own privileges. Proceed at your own risk, extensions here are not signed or are not reviewed or tested in depth by Eclipse Enclave core team.

Afterwards:

enclave tools list                     # built-in and installed, with provenance
enclave tools update <extension-name>  # refresh from the recorded source
enclave tools remove <extension-name>

If enclave tools --help has no add subcommand, your Enclave predates the installer. Update from the rolling release.

Alternatively, you can skip the installer entirely: download or clone this repository yourself and copy the individual tools/<name>/ or features/<name>/ directories you want (not necessarily all of them) into the matching tools/ or features/ subdirectory of ~/.config/enclave/extensions/. This gets you the same extensions without provenance tracking or update checks. See Enclave's extension docs for more information.

What is in here

Tool	Status	What it is
openclaw	Experimental	OpenClaw personal assistant: gateway, terminal UI, and browser dashboard
dsh	Experimental	DeepSeek Harness with its browser UI
antigravity	Experimental	Google's Antigravity CLI (agy), installed from the upstream GitHub release, with its telemetry opted out and its self-updater cut off. Requires the Enclave rolling release from 2026-09-21 or newer
amp	Experimental	Sourcegraph's Amp coding agent CLI, installed checksum-verified from upstream storage, with its self-updater blocked and remote-control paths disabled by default
mistral-vibe	Experimental	Mistral's Vibe coding assistant CLI, installed with Mistral's installer. A built-in tool of core Enclave until it moved here

Feature	Status	What it is
vnc	Experimental	Contained GUI: a virtual X display with a fullscreened Chromium, served over VNC, plus an enclave vnc-viewer host command
enclave-dev	Experimental	Go linters at the versions Enclave's CI pins, for developing Enclave itself. Use with core's golang-dev
deb-dev	Experimental	Debian packaging tools: debhelper, fakeroot, lintian
rpm-dev	Experimental	RPM packaging tools: rpmbuild
playwright-mcp	Experimental	Playwright MCP server with Chromium, registered with Claude Code. Replaces core's playwright feature and --playwright-mcp
shell-extras	Experimental	zsh with oh-my-zsh, and bash-completion
debug-tools	Experimental	Debugging and tracing tools: gdb, strace, ltrace, valgrind, tcpdump, sysstat

Experimental means what it says: each one gets thinner testing than a built-in tool, and has rough edges written down in its own README. Read that README before the first session, the security notes above all.

Contribute

Bring your favorite agent or enclave feature. A tool extension is a directory with a spec.yaml and usually an install.sh. A feature extension can be as small as a spec and a package list.

• Tools live in tools/<name>/ and declare kind: sandbox.
• Features live in features/<name>/ and declare kind: mixin.
• The directory name must match the spec's name.
• Every extension needs a README.md that covers credentials, egress, persistence, and whatever does not work.

Start from Enclave's guide to adding a tool and the extension reference, try it locally with enclave tools add ./path/to/clone --name <name>, then open a pull request. Also rough extensions marked experimental are welcome. But please make sure to properly document the state of your extension and its edges.

Questions & Support

Got a question, an idea, or ran into trouble with one of these extensions? Head over to Enclave's discussions and start a thread. It's the best place for support, feature requests, and just chatting about what you're building.

License

MIT. See LICENSE.