AI coding agents need a safe place to work; Eclipse is building the sandbox to give it to them
InfoWorld ·

AI coding tools are moving beyond copilots that make suggestions to independent, autonomous agents that execute terminal commands, write and modify software, run tests, and install dependencies. This means they need the freedom to move around on their own, but that is inherently dangerous; agents with little oversight or unrestricted access can make changes they aren’t supposed to, expose credentials and other sensitive information, or take other unintended actions, as vendors have discovered the hard way . To help move the bar on these security and governance challenges , the Eclipse Foundation has launched Eclipse Enclave 1.0, an AI sandbox and runtime. Developers can use the vendor-neutral platform to test various autonomous AI coding tools in isolated environments, with explicitly defined access to files, credentials, and networks. The alternative has been to keep the agent on a “very short leash,” which requires developers to approve every action, said Thabang Mashologu , CMO and head of products at the Eclipse Foundation. And at that point, you’re losing a lot of the productivity benefits of having an autonomous agent in the first place. “Ultimately, developers shouldn’t have to choose between agent productivity and security,” he said. More independent work, less supervision The Eclipse Foundation is a non-profit chartered in the EU that supports and governs more than 450 open source software projects. That now includes Eclipse Enclave 1.0, which currently supports Claude Code, Codex, OpenCode, GitHub Copilot CLI, Pi, and Eclipse Theia. Its extensible architecture allows for additional tool integration. Developers can run agent sessions in isolated containers, allowing them to work independently but with limited access to sensitive files and resources. Built-in mechanisms help protect API keys and OAuth tokens for third-party services. Users can give the agent access to exactly what it needs for a particular task, such as project source files, selected documentation, or web resources, plus a curated list of development tools, Mashologu explained. “Everything else on your development machine, such as SSH keys, tokens, and other source files, remains out of reach of the agent,” he said. One example use case would be that of an agent given the task of refactoring a fairly substantial piece of code. It should be able to explore the codebase, make changes, install whatever dependencies it needs, run tests, execute ad-hoc scripts to obtain and analyze runtime logs, and keep iterating until it’s done, Mashologu said. “That’s exactly the kind of work where agents can save developers a lot of time ,” he noted. “But it’s also the kind of long-running task where you might be uncomfortable giving an agent unrestricted access to your machine without supervision.” Multiple agents can also be run in parallel on separate tasks in Enclave, but their work is isolated, making it simpler to review. Developers have model choice and persistent sessions, so they can resume work without losing progress or configuration. The platform integrates a preview of HomeShell , a UI that manages multiple parallel sessions in project workstreams. For instance, one agent may be delegated to perform a bug fix, another may write tests, and a third may handle a refactoring task. “Each can work in its own worktree and isolated environment without interfering with the others,” Mashologu explained. Developers still review the work before merging it, but the difference is that they’re able to spend more time defining needed changes and evaluating results, and “less time supervising every step along the way,” he said. Eclipse Enclave 1.0 also gives developers: 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. “They found that this also made it more practical to delegate several tasks to multiple agents in parallel, with developers focusing on shaping the work and steering the results,” Mashologu said. EclipseSource, which has been actively involved in the open-source ecosystem for more than 15 years, contributed the platform to the Eclipse Foundation in July 2026, and its team has continued developing it, incrementally porting more and more features from its internal tooling. “Making Enclave open source creates an opportunity for others to contribute, scrutinize the technology, and help shape its direction,” Mashologu observed. Better tools to manage the risk Still, it’s relatively early in the evolution of agentic development, he acknowledged, and it’s important not to overstate what sandboxing can do. It helps define clear borders outside of the AI harness and contain risk, but doesn’t eliminate it. Developers still have to think carefully about permissions, network access, dependencies, and the quality and security of the code agents produce. “We’re not suggesting that Enclave makes autonomous agents completely safe,” Mashologu said. “It’s about giving developers better tools to manage the risks.” The bigger issue Ultimately, the project highlights what the Eclipse Foundation considers a much bigger issue: Who controls the infrastructure that AI agents rely on. It shouldn’t be controlled by any one vendor or tied to any particular AI model or development tool, Mashologu said. As agents become more autonomous, the systems that determine what they can access, what they’re allowed to execute, and how they interact with the outside world become incredibly important, he pointed out. “It’s not enough for the AI models themselves to be powerful. We also need open, trusted infrastructure around them.”