docs: MXC execution-container integration design (Phase 1 plan)#15
Merged
Conversation
DESIGN-mxc-sandbox.md — Phase-1 plan to add MXC OS-level sandboxing to entrabot via a new entrabot/sandbox/ module + an operator-opt-in run_code MCP tool (off by default). Hardened against an independent review: - run_code disabled unless ENTRABOT_ENABLE_RUN_CODE=1 - positive-allowlist-only, backend-aware, fail-closed policy ceiling (LLM may only narrow — Learning #54); deniedPaths unsupported on Windows - no token in the sandbox; keychainAccess hard-banned in P1 - binary verified by pinned commit + SHA256 before exec; build-from-source opt-in; structured argv, no shell; config via stdin/0700 file - audit redaction schema + error taxonomy; adversarial integration tests - Phase-2 (Entra-bound session isolation) stubbed + documented; not GA Supersedes the AppContainer TODO (sandbox co-equal with identity). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
brandwe
force-pushed
the
docs/mxc-sandbox-design
branch
from
fef180d to
720112b
Compare
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
1 participant
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
Engineer-review output: the design to add MXC (Microsoft Execution Containers) OS-level sandboxing to entrabot. Pairs entrabot's identity/attribution with MXC's containment — the full Build-2026 secure-agent story.
docs/architecture/DESIGN-mxc-sandbox.md. Research input:docs/platform-learnings/mxc-windows-sandbox.md(already on main).Scope
entrabot/sandbox/module (mirrorsplatform/) + an operator-opt-inrun_codeMCP tool.Supersedes the
AppContainer sandbox production implementationTODO (prior CEO-review premise "sandbox co-equal with identity").Hardened against an independent review (3/10 → resolved)
A fresh-context review flagged real gaps; all incorporated:
run_codeoff by default (ENTRABOT_ENABLE_RUN_CODE=1to enable) — it's a new model-invocable surface inside a sandbox MS says "isn't a security boundary yet."deniedPathsis unsupported on Windows, so the ceiling never relies on allow-broad+deny.keychainAccesshard-banned in Phase 1.What's not buildable yet (cited for stakeholders)
The Entra-bound, Intune-governed session-isolation story is announced, not GA — Windows blog future-tense ("will be used"), Insider-build-only, "not a security boundary yet." Internal verification (eng.ms / ES Chat) was inconclusive; an inquiry to the MXC owners is recommended. Full citations in the doc.
Docs-only. No code yet — implementation is the task list in the doc.
🤖 Generated with GitHub Copilot CLI
Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com