- Rootless session operation on Podman and Docker.
- Network visibility: Traffic from all sessions goes through a gateway with an allowlist; the log allows users to review what the agent tried to reach.
- Access to tools and features straight from git repositories. A separate enclave-extensions repository provides more harnesses (like Antigravity), sandbox features, and developer tooling (like Playwright MCP). A VNC viewer provides the ability to operate UIs within the container, and extensions can add commands, such as `enclave vnc-viewer`.
- Binaries for Linux and macOS (including arm64), deb and rpm packages, and a launcher for Windows via WSL2.
- Self-updates with a stable and a rolling channel, with releases published on the Eclipse download site.
Changing how developers focus their attention
Enclave was first developed by EclipseSource, an Eclipse Foundation member that builds custom tools and integrated developer environments (IDEs), in late 2025 as an internal tool. Its developers quickly began using it daily, so it wasn’t a “purely theoretical exercise,” Mashologu noted.
The company then observed a shift in where developers focused their attention, he explained. Previously, repeated approval prompts interrupted their flow, and agents stalled whenever they couldn’t respond immediately. “Defining access rules upfront, in line with company policies, reduced the need for that constant babysitting,” Mashologu said.
Using the tool, developers could spend more time thinking through what agents should accomplish, the architecture required for those tasks, the constraints they must respect, and how they could prepare the tools, context, and checks agents needed to complete and verify their tasks.

