DeltaBox Lite vs Microsoft Execution Containers

DeltaBox Lite

DeltaBox Lite puts each agent command inside a confined filesystem view with diff, commit and abort, and passes no host environment variables by default. It is version 0.1.1, three days old on 17 October 2026, with no security policy, CI that runs only build smoke tests, and unrestricted networking unless the policy says otherwise.

Microsoft Execution Containers

MXC puts nine operating-system sandbox backends behind one typed request, with network access denied by default and a JSON Schema for the stable 1.0.0 contract. Version 1.0.0 shipped on 6 October 2026 and 1.0.1 on 17 October. Enforcement varies by backend, and isolation_session cannot restrict networking at all.

DeltaBox Lite

1. Skip step 5 of install-prompt.txt. Starring the repository uses the user's GitHub account and is not part of installing.
2. Pass --commit or --abort to deltabox run explicitly. The child's exit status is preserved after that decision.
3. Wrap redirection and pipes in sh -c '...'. An unquoted > is handled by the host shell and writes outside the sandbox.
4. Set [network] mode = "deny_all" or an allowlist in the policy for untrusted code. The default allows every destination.
5. Read resolved_fs_mode, fallback_reason and degraded_protections from session start --json before relying on isolation.

Microsoft Execution Containers

1. Import from @microsoft/mxc-sdk/v1. The package root exports nothing.
2. Call getPlatformSupport() first and stop if isSupported is false. getAvailableBackends() is advisory and launch-time validation still applies.
3. Set network.egress.default to allow only when the task needs it. Omitted network policy resolves to deny in every direction.
4. Never pass --audit to an executor for untrusted code. It turns off all sandbox security for the workload.
5. Read ExecutionResult.warnings after each run. Security warnings arrive there and are not written to stdout or stderr.