dsh-approve-for-me: A Rule-Gated Sandbox Auto-Approval Plugin for DeepSeek Harness

timeance/dsh-approve-for-me

Workflow & AutomationVerified
Listed on 2026-08-20
Page last updated 2026-08-20

Rule-gated automatic sandbox approval for DeepSeek Harness with optional LLM review and human fallback.

Let DeepSeek Harness auto-approve allowlisted sandbox escalations, and fall back to human approval for uncertain cases.

install
dsh plugin --profile web add github:timeance/dsh-approve-for-me
Category
Workflow & Automation
Platform
DSH-Plugin
Author
timeance
Distribution
Plugin

dsh-approve-for-me Key Features

Prefix allowlist rulesFixed high-risk checksOptional LLM reviewNative human fallbackOne-time grants only

dsh-approve-for-me Repository

timeance
Publisher
timeance
Repository
timeance/dsh-approve-for-me
12
Stars
1
Forks
0
Watchers
0
Open issues
LanguageTypeScript
LicenseMIT License
Website
Repo last push2026-08-19 22:45:51
Repo created2026-08-15 00:30:21
Topics
cordisdeepseek-harnessdshdsh-plugin
Default branchmain

dsh-approve-for-me Repo Summary

dsh-approve-for-me is a sandbox approval automation plugin (DSH plugin) for DeepSeek Harness, maintained by timeance under the MIT license, written in TypeScript. It solves the inefficiency of asking the user for every sandbox escalation request by applying rule-gated automatic approval: narrowly allowlisted Shell and PowerShell commands get one-time (allowed-once) approval, while uncertain cases fall back to the user. Core capabilities include a literal prefix allowlist, fixed high-risk checks, an optional tool-free LLM reviewer, and native human fallback. The plugin is validated against DeepSeek Harness 0.1.0-rc.6; newer Harness releases will be tracked after validation.

What core features does the dsh-approve-for-me DSH plugin support?

The plugin follows the design: "Rules set the boundary. The current session model reviews candidates. Anything uncertain goes back to you." It only auto-approves narrowly allowlisted Shell and PowerShell sandbox escalations, granting a single allowed-once approval per successful decision, never permanent access. Fixed high-risk checks intercept package-manager lifecycle scripts (e.g., npm test, pnpm test), path-qualified executables, direct scripts, wrappers, known mutating PowerShell aliases, and unknown package-manager actions, returning them to native human approval even when a prefix matches. The optional LLM reviewer can narrow the auto-approval set but cannot bypass rules or fixed checks.

How do I install dsh-approve-for-me?

Installation requires installing DeepSeek Harness, then adding the plugin to the Web Profile and starting the Host. Note that @latest is an npm dist-tag, not a fixed version; use @beta to follow the beta channel explicitly, or a concrete published version for reproducible installs or rollback. Do not use the bare package name as an upgrade command, as the Profile manifest may already contain an exact version, and pnpm may report "Already up to date" without changing it.

bash
npm install -g @deepseek-ai/dsh
dsh plugin --profile web add github:timeance/dsh-approve-for-me
dsh web --host 127.0.0.1 --port 3080

How do I configure dsh-approve-for-me in the Web UI?

In Settings -> Plugins -> Plugin configuration -> Approve for me, add only command prefixes you are willing to review automatically, for example Shell: git status, git diff; PowerShell: Get-Location, Get-Content -LiteralPath README.md. Then select the "Approve for me" Access preset for the target agent or session. Note that commandPrefixes is empty by default; installing the plugin alone does not automatically approve any command. Define positive rules first. A rule is a token prefix, not an exact-command equality check, so additional arguments can follow, but keep subcommands and paths explicit.

Which DeepSeek Harness versions and platforms does dsh-approve-for-me support?

The plugin is validated against DeepSeek Harness 0.1.0-rc.6; newer releases will be tracked after validation. The Web card is an optional editor; the Host approval core also works in a headless Profile and can be configured through YAML only. On rc.6, the client registers a settings.plugin.item card under the real plugin id approve-for-me, appearing only over loopback and using the plugin's loopback-only RPC. The Host delegates persistence, schema validation, conflict handling, redaction, and hot reload to the official Settings service. The card makes no approval decisions and does not depend on or impact the approval core.

What is the license and project status of dsh-approve-for-me?

The project is maintained by timeance, licensed under MIT, and written in TypeScript. The repository was created on 2026-08-14 and last updated on 2026-08-17, with 11 stars, 1 fork, and no open issues. This is an unofficial beta plugin that has not received an independent security audit and comes without warranty. Built-in checks cannot cover every command, argument, or environment. Keep rules narrow and retain Harness's native human approval as the final decision for important operations.

View more DSH plugins at dsh-plugin.org

DSH-Plugin FAQ