Skip to content

dsh-always-require-tools-approval

Verified

@j0ss077/dsh-always-require-tools-approval Β· v1.1.0 Β· MIT

Require a one-shot user approval before configured tools execute

Install

dsh plugin add @j0ss077/dsh-always-require-tools-approval

Confirm the layer applied with dsh --profile default --dump-config β€” see the install guide.

Source

Creators

Readme

@j0ss077/dsh-always-require-tools-approval

Stop. Confirm. Run. A DeepSeek Harness plugin that pauses the tools on your watchlist and waits for your explicit approval before every execution.

npm version license: MIT node: >=22.19

What it does

DSH runs your agent in a sandbox that blocks file writes β€” but not commands. bash can still read files, launch programs, and reach the network.

This plugin puts an approval gate between a tool and its execution. When the agent calls a tool on the watchlist, the harness pauses and asks before anything runs.

  • Default watchlist: bash and pwsh.
  • One approval = one execution. The next call asks again.
  • Reject, cancel, or no approval channel β†’ the tool is blocked.
  • Every other tool is left untouched.

Requirements

  • A DSH profile with an approval service β€” the standard web (GUI) profile ships one.
  • Node.js >= 22.19.

Install

One command installs and activates the plugin (it ships as a bundle layer):

dsh plugin --profile web add @j0ss077/dsh-always-require-tools-approval

Then restart the GUI. Use a different --profile if you run under another one.

Configure

One option: tools β€” the watchlist.

Key Type Default Meaning
tools string[] ["bash", "pwsh"] Tool names that require approval before they run.

Override it at runtime without reinstalling. Edit ~/.dsh/settings.yaml ($DSH_HOME/settings.yaml when set):

always-require-tools-approval:
    tools: ["bash", "pwsh", "node"]

This file takes precedence over the value baked into the bundle.

What you'll see

  1. The agent calls a watched tool, e.g. bash.
  2. Execution pauses: "Approve this tool execution?"
  3. Approve β†’ that single call runs. Reject β†’ denied, and the agent is told you rejected it.

Every call prompts again β€” approving once never grants a blank check. The prompt text is fixed by design.

Safety model

  • One-shot. One approval authorizes exactly one execution.
  • Fail closed. No approval channel (headless run, unmounted service) β†’ the tool is denied, never silently allowed.
  • No auto-approve. For a watched tool the plugin only asks; it never approves on its own.
  • No interference. Unwatched tools delegate to the next plugin.

Update & remove

dsh plugin --profile web update @j0ss077/dsh-always-require-tools-approval
dsh plugin --profile web remove @j0ss077/dsh-always-require-tools-approval

Restart the GUI after updating.

Development

pnpm install
pnpm build      # compile and normalize .d.ts
pnpm typecheck  # type-check source + tests
pnpm test       # node --test

The plugin is three modules β€” src/contracts.ts (harness types), src/gate.ts (the gate policy), src/index.ts (wiring). See ADR 0001 for why the harness types are self-declared.

License

MIT