You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@magpie.apache.org by Jarek Potiuk <ja...@potiuk.com> on 2026/08/01 16:46:46 UTC

[DISCUSS] Eclipse Enclave support

Hello here,

I am catching up on things from the past few weeks and just created
https://github.com/apache/magpie/issues/1059 after our discussion with
Bartosz during EuroPython.

I did some research. Enclave seems to aim to wrap the whole agentic CLI in
a container. This differs from our current solution based on
Bubblewrap/Seatbelt, where only the CLI commands are container-wrapped (in
addition to the CLI's native sandboxing solution), and the CLI itself is
wrapped only with a script that strips sensitive environment variables.

The promise is this - https://projects.eclipse.org/proposals/eclipse-enclave

 * Go-based CLI for launching AI coding agents inside isolated Docker
 containers.
* gateway sidecar enforcing DNS- and SNI-based network egress policy with
 per-request logging.
* Git worktree integration for safe parallel agent sessions.
A desktop control UI (Wails v2 + React) for managing projects, sessions,
and worktrees.
* Pluggable tool and feature extensions, with built-in support for Claude
Code, Codex CLI, Gemini CLI, OpenCode, Theia AI, and others.
* Per-session authentication, secret, and credential handling, with
optional shared- or project-scoped persistence.

This architecture - if working - should prevent from even a compromised
CLI  or from agents escaping the sandboxing of CLI - and provide more
complete isolation.

I asked the Eclipse team to get us in contact with Enclave team so that
they can explain us where they are (they are still incubating in Eclipse).
If someone is interested, as soon as I get information from them I might
try to setup a more technical call/demo and discuss options

J.