Plugin directory / Developer / dsh-tool-approval
dsh-tool-approval
Verified · install-tested on dsh ilharp
What it does
Manual approval for DeepSeek Harness (aka Manual Mode / Ask Mode).
Works — verified, early-stage project
Manual approval for DeepSeek Harness (aka Manual Mode / Ask Mode). 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-tool-approval
English | 锟斤拷锟斤拷
Add pre-approval to any Tool Calling, aka "Manual Mode"/"Ask Mode".

Install
dsh plugin --profile web add dsh-tool-approval
Config
Default config
- id: tool-approval
name: dsh-tool-approval
With the default config, every Tool Calling goes through pre-approval.
Custom config
- id: tool-approval
name: dsh-tool-approval
config:
include: [fs_*, web_*]
exclude: [task_output]
reason: tool execution requires your approval
Only tools specified in include get pre-approval; tools in exclude pass through. Wildcards are supported.
LICENSE
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-tool-approval for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
Web profile:
dsh plugin --profile web add dsh-tool-approval Headless (CLI) profile:
dsh plugin --profile headless add dsh-tool-approval Package
npm: dsh-tool-approval · version 0.1.0 · tested on dsh 0.1.0-rc.6
Test report
Verified end-to-end: L1 install + L2 load + L3 runtime Q&A 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.