AI Agent Hub
Back to plugins
🧩

dsh-sandbox-permissions-not-strictly-wider-justification-empty-fix

admin-security Updated 2026.08.31

Run the following command in DeepSeek Harness:

dsh plugin install yajiangandchenchen/dsh-sandbox-permissions-not-strictly-wider-justification-empty-fix

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install yajiangandchenchen/dsh-sandbox-permissions-not-strictly-wider-justification-empty-fix in DeepSeek Harness to install it; the source repository is available at https://github.com/yajiangandchenchen/dsh-sandbox-permissions-not-strictly-wider-justification-empty-fix .

About this plugin

When DSH runs with non-default models and a session is already in danger-full-access mode, two recurring bugs surface across four tools (pwsh, bash, fs, and dsh-sandbox): an empty justification string triggers an 'invalid justification' error, or a same-level permission request is rejected as 'not strictly wider,' throwing an exception. These issues have been independently reported multiple times and reliably break session flow. This plugin introduces a two-layer defense. First, schema descriptions are updated to explicitly tell the model that same-mode retries are accepted as no-ops, reducing the tendency to emit empty fields. Second, runtime normalization logic is injected at each tool's execute or resolvePolicy entry point, silently clearing escalation parameters whenever the requested mode is not strictly wider than the current effective mode, so no exception is ever thrown. The plugin also self-heals: on every client start it verifies that patches are still intact and automatically re-applies them if a desktop update has broken the hard link. Uninstalling restores all original files from a persistent backup directory. If you frequently operate DSH in danger-full-access mode with non-default models, this plugin removes these recurring interruptions and keeps sandbox permission transitions smooth.

Use Cases

  • Hitting a 'not strictly wider' exception when requesting the same sandbox level in danger-full-access mode
  • Non-default models emitting an empty justification string and triggering validation errors
  • Patches silently lost after a desktop update, requiring automatic detection and re-application

Best For

  • Users who run DSH with non-default models in danger-full-access mode on a daily basis
  • Developers who frequently switch sandbox permission levels across pwsh, bash, and fs tools
  • Operators managing both desktop and web installs who care about patch persistence