docs(sandbox): document Eclipse Enclave as an optional container-level backend - #1064
Closed
onlyarnav wants to merge 1 commit into
Closed
docs(sandbox): document Eclipse Enclave as an optional container-level backend#1064onlyarnav wants to merge 1 commit into
onlyarnav wants to merge 1 commit into
Conversation
…l backend bubblewrap (Linux) and Seatbelt (macOS) sandbox each Bash subprocess on the host. Eclipse Enclave — an incubating Eclipse Foundation project, MIT-licensed — takes the container route instead: the whole agent session runs isolated, so the host is never in scope. Adds it as a documented Layer 1 option alongside the two OS backends, with the trade-offs stated (needs a container runtime; coarser than per-subprocess carve-outs like sandbox.excludedCommands; covers the agent's own Read/Edit/Write tools, which the OS backends do not). States the contract Magpie requires of any container-level backend rather than wiring to Enclave's CLI, which is not stable yet. Enclave is deliberately absent from pinned-versions.toml: a pin needs a version and a release date to age through the cooldown, and there is no released artefact to pin. Documentation of an option, not a shipped integration — the backend selector, pin entry, and verify check are left for a stable release. Generated-by: Claude Code (Opus 5)
Member
|
I do not want to document it yet. This is question of discussion whether and how and why |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Supports Eclipse Enclave as an optional container-level backend for Layer 1 sandbox isolation, alongside existing per-subprocess OS sandboxes (
bubblewrapon Linux andSeatbelton macOS).Where
bubblewrapandSeatbeltsandbox each Bash subprocess on the host, Eclipse Enclave runs the entire agent session inside an isolated container with its own filesystem, process tree, and network stack so the host is never in scope.Key Highlights & Benefits
dangerouslyDisableSandboxor local.claude/settings.jsonoverrides — Threat Model Residual Risk 4). Even under an override, execution is bounded by the container.Required Contract for Container Backends
This PR defines the 5 contract requirements Magpie expects of any container-level backend:
$GH_TOKEN,$AWS_*, or host credential paths mounted).tools/egress-gateway/).Why Wiring / Pins Are Deferred
Eclipse Enclave is currently incubating at the Eclipse Foundation without a published release or stable CLI. Wiring (backend selector in
agent-iso.sh, pin entry inpinned-versions.toml, and verification probes) is intentionally deferred until Enclave publishes its initial release.Files Modified
Verification
prek run --all-files).uv run pytest— 389 passing tests).closes: #1059
Generated using: Claude Code (Opus 5)