Plugin directory / Developer / dsh-same-mode-sandbox-noop
dsh-same-mode-sandbox-noop
Verified · install-tested on dsh zhangzujian
What it does
DSH compatibility plugin for redundant same-mode sandbox escalation requests
Works — verified, early-stage project
DSH compatibility plugin for redundant same-mode sandbox escalation requests It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
dsh-same-mode-sandbox-noop
A removable compatibility plugin for DeepSeek Harness / DSH 0.1.0-rc.6.
That release rejects a tool call when sandbox_permissions names a mode that
is already covered by the call's effective sandbox mode:
Error: sandbox escalation to "danger-full-access" is not strictly wider than
this call's current "danger-full-access" mode
The plugin wraps both ctx.tools.execute() and the rc.6 Agent Loop scheduler's
preparation entry point before DSH snapshots and freezes tool arguments. Forbash, pwsh, write, and edit, it removes the pairedsandbox_permissions and justification fields when the requested mode is
equal to or narrower than the calling session's effective mode. The original
runtime then executes the call under its standing policy. For example, aworkspace-write request in a danger-full-access session is not an
escalation, so the redundant pair is removed.
Genuinely wider requests, unknown modes, malformed argument pairs, unrelated
tools, and calls without escalation fields pass to DSH unchanged. For a known
non-escalating request, an empty justification is removed with the redundant
permission fields before DSH validates it; for a genuinely wider request, the
same empty justification remains subject to DSH's original validation.
Disposal restores the original runtime methods.
This is an out-of-tree compatibility workaround. Prefer a DSH release that
handles non-escalating requests in the shared sandbox escalation layer when one
is available.
Install into a DSH profile
Until this package is published to npm, clone it and add the local directory:
git clone https://github.com/zhangzujian/dsh-same-mode-sandbox-noop.git
cd dsh-same-mode-sandbox-noop
npx @deepseek-ai/[email protected] plugin --profile web add "$PWD"
The package declares a DSH bundle, so dsh plugin adds its patch layer to the
profile automatically. Restart dsh web after installation.
To remove it:
npx @deepseek-ai/[email protected] plugin --profile web remove @zhangzujian/dsh-same-mode-sandbox-noop
For a one-off local overlay without profile installation, insert the plugin by
file URL in a patch loaded after the base bundle:
- insert:
- id: same-mode-sandbox-noop
name: file:///absolute/path/to/dsh-same-mode-sandbox-noop/index.mjs
Test
Unit tests require only Node.js:
npm test
Integration tests run against an installed DSH tree:
DSH_INSTALL_DIR=/path/to/npx/cache/package npm run test:integration
DSH_INSTALL_DIR is the directory containing node_modules/@deepseek-ai.
License
MIT
Install
Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:
dsh plugin add dshbase-catalog Then say "install dsh-same-mode-sandbox-noop for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
This plugin is GitHub source (not published to npm) — install it straight from the repo:
Web profile:
dsh plugin --profile web add github:zhangzujian/dsh-same-mode-sandbox-noop Headless (CLI) profile:
dsh plugin --profile headless add github:zhangzujian/dsh-same-mode-sandbox-noop Test report
Verified: L1 install + L2 load + L3 runtime from GitHub source on dsh 0.1.0-rc.6.
When to use it
Extend the agent's coding surface — give it a new tool, workflow, or integration so it handles a dev task it couldn't before.
Who it's for
Developers who want dsh to behave like a teammate on real codebases — editing, running, and verifying changes rather than just answering.
For developers — extending it
The tool/command surface is the seam: expose more of the SDK, add smarter context wiring, or tighten the loop between code changes and verification.