Eclipse Enclave 1.0 Ships as Sandbox for Coding Agents
A vendor-neutral sandbox for coding agents
The Eclipse Foundation announced Eclipse Enclave 1.0 on November 19, 2026, describing it as a vendor-neutral runtime and sandbox for running AI coding agents autonomously in isolated, policy-controlled environments (Eclipse Foundation). The project supports Claude Code, Codex, and OpenCode out of the box, with an architecture designed to permit additional agent integrations (Eclipse Foundation). It is released under the MIT License.
Why it matters to builders of agent systems
For teams running coding agents against real repositories, Enclave offers a neutral alternative to vendor-specific sandboxing, giving operators rootless sessions on Podman and Docker, allowlisted network access with traffic logging, and self-updates through stable or rolling channels (InfoWorld). That combination matters for organizations that want agents to execute code autonomously without granting them unrestricted access to a host machine or network.
The version 1.0 that wasn't quite 1.0
The GitHub release page for the project tells a more precise story than the announcement alone. Version 1.0.0 was tagged but never published, because its Windows archives lacked required license files; version 1.0.1, released October 31, is described on the release page as "the first official release of Eclipse Enclave" and as "1.0.0 with that fixed" (GitHub). In effect, developers pulling the project's first real build have been running 1.0.1 since late October, three weeks before the Foundation's public announcement.
Platform support and known limits
Official release artifacts cover Linux packages for Ubuntu 24.04 and Fedora on x86-64, plus single-file builds for Linux and macOS on x86-64 and arm64 (GitHub). Windows users run Enclave through WSL2. The release page also flags that the QEMU backend remains experimental and lacks network filtering, and that Debian and RPM packages are x86-64 only and do not self-update (GitHub). No breaking changes are documented in the official release material.
What's not yet known
Neither the Foundation's announcement nor the release notes disclose adoption numbers, so it is not yet possible to say how many teams have put Enclave into production use.


