sujingkpo/dsh-auto-pass
Adds an Auto Approve permission preset to DeepSeek Harness that runs each approval request through a single-shot model review plus project/global allow and deny lists.
dsh-auto-pass adds an '自动审批' (Auto Approve) permission preset to the DeepSeek Harness Web UI. Every action needing approval goes through a single-shot model review — one plain model call with no child agent, no tools and no transcript, fed only the normalized action plus your last direct message — and the plugin auto-approves only requests that pass. A model denial, a host safety downgrade, and a failed review all fall back to DSH's normal approval chain so the user decides; the one exception is the off-by-default 'Reject on denylist' switch, where a denylist hit fails the tool call outright. On top of that sit two layers of permission memory — an allowlist (allowed directly, no model call) and a denylist (handed to you directly) — at project and global scope, with rules coming from your own promote/demote action, the Reviewer's suggested rule, or a threshold that writes a rule automatically after the same permission is approved (default 3 times) in a row.
Install
dsh plugin --profile web add github:sujingkpo/dsh-auto-passCopied verbatim from the README's install block (the web profile github: form). The README also documents a local-path form (dsh plugin --profile web add link:/path/to/dsh-auto-pass). Its headline caveat: the project only auto-approves requests that pass review — it does not solve unattended operation — and it is forked from / based on simon300000/dsh-auto.
Compatibility
Installs into the web profile. The README's screenshots reference DSH 0.1.5-rc.1 for the Auto Approve permission preset.
Details
- Repo: sujingkpo/dsh-auto-pass
- Category: Coding & Development
- Stars: 0
- Version: GitHub repo sujingkpo/dsh-auto-pass; installed from the github: source in the README's install block (no npm package claimed).
FAQ
- Does it make approval decisions without me?
- The README says it auto-approves only requests that pass a single-shot model review; a model denial, a host safety downgrade or a failed review is handed back to DSH's normal approval chain so the user decides.
- What is the one exception to the fall-back behaviour?
- The 'Reject on denylist' switch (off by default) — the README says once you turn it on, a denylist hit fails the tool call outright instead of opening an approval card.
Alternatives
timeance/dsh-approve-for-me · nexu-io/open-design · liustack/modsearch