omdsh-dev/sandbox-mxc
微软跨平台沙盒支持
Listed
2
Security
Bundle verified
Preview
What it does
Microsoft cross-platform sandbox support.
Best for
- DSH deployments that need the extracted Microsoft cross-platform MXC sandbox provider for bash or PTY consumers.
- Teams that require fail-closed executor qualification, complete file-effect policy, and versioned result-envelope settlement.
Not ideal for
- Linux hosts without usable Bubblewrap or user namespaces, and platforms that cannot satisfy MXC-specific acceptance requirements.
- Installations without GitHub Packages access for the patched MXC SDK on main, unless they deliberately use the vendor SDK branch; older DSH hosts also need the legacy integration patch.
README
@deepseek-ai/dsh-sandbox-mxc
| English | 中文 |
The MXC sandbox provider extracted from the DSH feat-mxc implementation as one standalone external bundle. The repository keeps two delivery faces in one Git repository:
-
maincontains the registry-backed provider from DSHfeat-mxc. -
feat-mxc-vendor-sdkcarries the same provider with the pinned SDK and native executors invendor-sdk/for offline packed-install rehearsal.
Repository shape
package.json # standalone provider package and dsh.bundle manifest
cordis.patch.yml # explicit sandbox-mxc profile row
src/ # provider, invariant, and Windows environment helpers
tests/ # unit, parity, and publish-path tests
lib/ # generated install artifacts
vendor-sdk/ # vendor branch only: SDK runtime and native executors
docs/ # detailed provider documentation
legacy/ # DSH host integration patch for older snapshots
The package exports @deepseek-ai/dsh-sandbox-mxc and its invariant companion. Its runtime peers are the DSH sandbox seam, subprocess environment helper, invariants package, and Cordis. The patched @dsh-external/mxc-sdk remains a runtime dependency: main resolves the dsh release tag from GitHub Packages, while the vendor branch replaces it with file:./vendor-sdk.
Bundle behavior
The bundle contributes an explicit, disabled opt-in row:
- id: sandbox-mxc
name: '@deepseek-ai/dsh-sandbox-mxc'
disabled: true
config:
enabled: true
useResultEnvelope: true
Enable the row in a profile only after the target DSH host supplies the prepare/settlement sandbox seam and the patched MXC SDK is available. The bundle does not silently replace an existing sandbox row; legacy/mxc-host-integration.patch contains the host cutover for DSH snapshots that need it.
The provider remains fail-closed. prepare() refuses to run unless enabled: true, and functional qualification must prove the exact bundled executor before a launch is returned. The provider compiles complete file-effect policy, preserves the exact payload argv/cwd/environment, settles versioned result envelopes, and releases per-run capture artifacts.
Development
A full source-plane check uses a sibling DSH checkout. For the latest extracted implementation, point external-plugins/deepseek-harness at the compatible feat-mxc checkout, install the SDK or use the vendor branch, then run:
pnpm install
pnpm run typecheck
pnpm test
pnpm run prepare
pnpm pack --dry-run
The prepare script builds directly from src/, so a Git installation does not require DSH project references at runtime. pnpm test:e2e runs the packed-install and real-executor rehearsals when the platform, SDK, and native executor are available.
Model Experience
This provider adds no model-visible prompt, tool, or result text. It supplies the sandbox capability consumed by DSH bash and PTY plugins; the sandbox seam owns the SANDBOX_UNAVAILABLE error and any user-facing denial semantics.
Known Limitations and Deferred Work
- Linux MXC qualification requires usable Bubblewrap/user namespaces.
- macOS and Windows acceptance remains platform-dependent; Windows Tier 3 requires explicit host DACL permission.
- The registry-backed
mainbranch requires GitHub Packages access to resolve@dsh-external/mxc-sdk@dsh; usefeat-mxc-vendor-sdkfor the tracked offline carrier. - Older DSH snapshots require
legacy/mxc-host-integration.patchbecause a bundle cannot add missing sandbox prepare/settlement APIs by itself.
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:omdsh-dev/sandbox-mxc in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.