timeance/dsh-approve-for-me
90Last commit Aug 15, 2026
dsh-approve-for-me DSH plugin
dsh-approve-for-me is a plugin for DeepSeek Harness that applies fixed high-risk checks, an optional tool-free LLM reviewer, and native human fallback to sandbox approval requests. Every successful decision grants one-time allowed-once approval, never permanent access. It is validated against DeepSeek Harness 0.1.0-rc.6.
How to install the dsh-approve-for-me DSH plugin
dsh plugin --profile web add dsh-approve-for-me@latestCopying does not run this command. Review the repository and version before installing the dsh-approve-for-me DSH plugin.
dsh-approve-for-me DSH plugin data source
dsh-approve-for-me DSH plugin snapshot date: Aug 16, 2026
discovered
What the dsh-approve-for-me DSH plugin can do
- Literal prefix allowlist for Shell and PowerShell commands
- Fixed high-risk checks before any approval
- Optional tool-free LLM reviewer with human fallback
Where the dsh-approve-for-me DSH plugin fits
- Automating approval of read-only commands like git status or Get-Location in repeated workflows
- Using rules-only mode for deterministic command approval without LLM
- Handling sandbox escalation in headless environments with YAML configuration
Who the dsh-approve-for-me DSH plugin is for
- Developers using DeepSeek Harness who want to reduce manual approval for safe commands
- Teams running automated workflows with clear command boundaries
dsh-approve-for-me DSH plugin limitations
- Only supports Shell and PowerShell sandbox escalations; other tools are not covered
- commandPrefixes is empty by default; no automatic approval without explicit configuration
dsh-approve-for-me DSH plugin: from the repository README
Quoted from the timeance/dsh-approve-for-me README, the upstream source of the dsh-approve-for-me DSH plugin. Copyright remains with the original authors.
English | [中文](README.zh.md) [](https://www.npmjs.com/package/dsh-approve-for-me) [](LICENSE) **Rules set the boundary. The current session model reviews candidates. Anything uncertain goes back to you.** `dsh-approve-for-me` is a DeepSeek Harness plugin for rule-gated automatic approval of narrowly allowlisted Shell and PowerShell sandbox escalations. It applies fixed high-risk checks, an optional tool-free LLM reviewer, and native human fallback. Every successful decision grants one `allowed-once` approval, never permanent access. It is validated against DeepSeek Harness `0.1.0-rc.6`; newer Harness releases will be tracked after validation. Literal prefix allowlist | fixed high-risk checks | tool-free LLM reviewer | native human fallback > [!WARNING] > This is an unofficial beta plugin. It 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. ## Why use it | Access
Read the full READMERepository license: MIT
dsh-approve-for-me DSH plugin questions
How do I install dsh-approve-for-me?
First install DeepSeek Harness globally with `npm install -g @deepseek-ai/dsh`. Then add the plugin to your web profile: `dsh plugin --profile web add dsh-approve-for-me@latest`. Restart the Host after installation.
How do I configure command prefixes for auto-approval?
Open the Web settings page at Settings -> Plugins -> Plugin configuration -> Approve for me. Add prefix entries like `Shell: git status` or `PowerShell: Get-Location`. You can also edit the YAML configuration under `$DSH_HOME\settings.yaml` in the `approve-for-me` section.
Why is my command not being auto-approved?
Check that the command matches a configured prefix exactly, that the sandbox escalation is for Shell or PowerShell, and that the active Access preset is set to 'Approve for me'. Also verify the command passes the built-in high-risk checks; if it fails, it falls back to human approval.
Can I use the plugin without an LLM reviewer?
Yes. Set the mode to `rules-only` in the YAML configuration. This disables the LLM reviewer and relies solely on the prefix rules and fixed high-risk checks. The `rules-only` mode still requires all command segments to match a prefix.
Is dsh-approve-for-me safe for production use?
The plugin is in beta and has not received an independent security audit. It applies fixed high-risk checks and only grants one-time allowed-once approval. However, built-in checks cannot cover every command or environment. Keep your prefix rules narrow and retain Harness's native human approval as a fallback for important operations.