omdsh-dev/sandbox-mxc
Microsoft cross-platform sandbox support
Routes DeepSeek Harness shell and terminal payloads through MXC as an explicit opt-in, without patching the harness. The bundle declares descriptors under config.stent.patches; stent-dsh reads them, installs the transformations before the target modules load, and enables the row only for the Stent composition. That keeps DSH in charge of the sandbox seam and lifecycle while letting MXC supply the actual execution path, and the README documents a legacy host patch that this bundle never applies.
Install
⚠️ Install command not yet confirmed — check the README on GitHub for the exact command.
Compatibility
README: a Stent sidecar that runs the DSH bash, PowerShell and persistent-terminal payloads through MXC without modifying DeepSeek Harness source files. DSH keeps ownership of ctx.sandbox, subprocess I/O, deadlines, signals, terminal sessions and teardown, while Stent supplies controlled load-time hooks that replace only the consumer call paths. The package root is the Stent function plugin and deliberately has no default export; the compatibility provider and policy compiler are also available from a /provider subpath, and new profiles are told to load the package root through the bundle row. The README notes the workspace uses pnpm's nodeLinker: hoisted because bundled dependencies cannot be materialized from an isolated linker.
Details
- Repo: omdsh-dev/sandbox-mxc
- Category: uncategorized
- Stars: 2
- Version: Bundle package @deepseek-ai/dsh-sandbox-mxc (name did not resolve on the registry when checked 2026-09-17; MXC runtime release v0.7.0 asset verified 2026-09-17; repo 1★, last push 2026-08-30)
- Last push: 2026-08-09
- First seen: 2026-08-04
Recent updates
The README documents the package surface, the descriptor model and the KV-cache effect rather than a release-by-release table; the MXC runtime it consumes was at release v0.7.0 when checked on 2026-09-17.
FAQ
- Does it patch the harness?
- No — the README says it is a Stent sidecar that never modifies DeepSeek Harness source files: DSH keeps ownership of ctx.sandbox, subprocess I/O, deadlines, signals, terminal sessions and teardown, while Stent hooks only the consumer call paths at load time.
- Where does the MXC runtime come from?
- Per the README it is the public @omdsh-dev/mxc-sdk 0.7.0 GitHub Release asset (omdsh-dev-mxc-sdk-0.7.0.tgz), pinned with its sha256; the release asset was verified on 2026-09-17.
- Is the row active by default?
- No — the README says the row is disabled in ordinary profiles and enabled only for the Stent composition.