npm / sandboxOfficial
DSH Bash Sandbox
by DeepSeek
Sandbox-consuming implementation of the DeepSeek Harness bash executor seam (confines every command via ctx.sandbox, reports denial/enforcement result facts)
CAPABILITY INDEX
Sandbox
09Compare sandbox DSH plugins for isolated execution, permission policies, filesystem boundaries, and safer code runs.
npm / sandboxOfficial
DSH Credentials Local
by DeepSeek
File-backed credentials provider ($DSH_HOME/.env under the live process environment) for the DeepSeek Harness
npm / sandboxOfficial
DSH FS Sandbox
by DeepSeek
Sandbox-enforcing implementation of the DeepSeek Harness filesystem seam: fences write/edit by the per-call sandbox mode (read-only denies mutation, workspace-write contains it to the workspace + temp roots) while reads pass through
npm / sandboxOfficial
DSH Permission Presets
by DeepSeek
User-facing permission presets (ctx.permissionPresets) for the DeepSeek Harness: one product-level Permissions select bundling the sandbox-mode and approval-policy knobs, written through to their own session events
npm / sandboxOfficial
DSH PowerShell Sandbox
by DeepSeek
Sandbox-consuming implementation of the DeepSeek Harness PowerShell executor seam (confines every command via ctx.sandbox, reports denial/enforcement result facts)
npm / sandboxOfficial
DSH Sandbox Local
by DeepSeek
Local process-sandbox backends for the DeepSeek Harness sandbox seam: bwrap, the npm-distributed landlock-run launcher, macOS Seatbelt, or the Windows ACL restricted-token runner — functionally probed, fail-closed
npm / sandboxOfficial
DSH Sandbox Policy
by DeepSeek
Per-call sandbox policy resolver and current model context: deployment fallbacks plus each session's mode and workspace root, shared by every enforcing capability family
npm / sandboxOfficial
DSH User Approval
by DeepSeek
User-approval seam (ctx.approval) for the DeepSeek Harness: one-shot permission decisions dispatched to composed answerers over the approval/request waterfall, fail-closed by default
npm / sandbox
DSH Credential Guard
by lee-scott
Blocks DSH file tools from reading common credential stores, SSH keys and secret files.
DSH CATEGORY GUIDE
How to choose Sandbox DSH plugins
Sandbox DSH plugins isolate command execution, files, processes, or policy decisions from the host environment. They are useful for running generated code and risky tools, but isolation strength varies widely between a local shell wrapper, an operating-system boundary, and a remote execution service.
Where these plugins help
- Isolated shell and code execution
- Permission and approval policies
- Filesystem and network containment
How to compare
Compare the actual isolation boundary, supported shells and operating systems, filesystem mounts, network access, environment variables, approval policy, timeouts, resource limits, and cleanup. A sandbox label alone does not explain what the plugin can still reach.
Before you install
Begin with no secrets, minimal mounts, and network access disabled where possible. Test termination, timeout, and cleanup behavior before allowing longer jobs. Keep host credentials and personal directories outside the sandbox boundary.
FAQ / 02
Frequently asked questions
Does a sandbox make generated code safe?
It reduces risk only within its documented boundary. Review mounts, network access, credentials, host integration, and escape assumptions; no sandbox should replace source review and least-privilege configuration.
Local or remote DSH sandbox?
Local sandboxes can be faster and keep data nearby; remote services may offer a stronger host boundary. Choose based on data sensitivity, isolation requirements, latency, cost, and provider trust.