Eclipse Enclave

Eclipse Enclave defines and implements a vendor-neutral runtime for executing AI agents in isolated, policy-controlled environments. The project provides container-based sandboxes for individual agent sessions, network egress policy enforcement, persistent and auditable session lifecycle management, and dashboards for operating many agents across many projects.

In scope:

• Isolation backends for agent execution, starting with Docker containers and potentially extending toward additional mechanisms such as microVMs, rootless runtimes, and Kubernetes-based orchestration.
• Network isolation and policy enforcement, including DNS allowlisting, transparent egress filtering, and request/dependency logging.
• Per-session filesystem and workspace isolation, including integration with source control mechanisms such as Git worktrees.
• Authentication, secret, and credential handling that keeps sensitive material out of agent-visible scope where possible.
• Session lifecycle management: create, pause, resume, attach to, inspect, and clean up agent sessions.
• A desktop and/or web control center for managing multiple agents working across multiple projects in parallel.
• Telemetry, audit trails, and reporting formats that support governance obligations including the EU AI Act and the EU Cyber Resilience Act.
• Extension points for integrating third-party AI agents, IDEs, and editors, including but not limited to those at the Eclipse Foundation.

Out of scope:

• Developing AI agents or large language models. Eclipse Enclave integrates with existing agents (such as Claude Code, Codex CLI, Gemini CLI, OpenCode, Eclipse Theia AI, and others) but does not produce its own.
• Developing an IDE or editor. Eclipse Enclave integrates with editors and IDEs including potential integration with Eclipse Theia, but does not build a new one.