DeepSeek Harness Plugin

kennethfan/dsh-sandbox-tune

Category Development & Runtime Added 2026-10-30

Lets build commands run inside the DSH sandbox instead of asking for elevation on every invocation: redirects pure caches (GOCACHE, NPM_CONFIG_CACHE, BUN_INSTALL_CACHE_DIR, PIP_CACHE_DIR) to a temp root, or grants the real cache directories write access in place so they stay shared with the terminal. Dependency stores (GOMODCACHE, CARGO_HOME) are never redirected, only granted. Adds optional user-directory grants (~/.config and friends, all off by default) and a command allowlist that matches exact strings or per-segment after splitting on &&, ||, ; and |, while rejecting redirects that write files (fd duplication like 2>&1 and /dev/null are allowed), command substitution and backgrounding outright. Settings are per-profile or per-session; file edits apply without a restart.

Install

# from a prebuilt release tarball

dsh plugin --profile web add "https://github.com/kennethfan/dsh-sandbox-tune/releases/latest/download/dsh-sandbox-tune.tgz"

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:kennethfan/dsh-sandbox-tune

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.