AI Agent Hub
Back to plugins
🧩

dsh-workspace-only-plugin

admin-security Updated 2026.08.16

Run the following command in DeepSeek Harness:

dsh plugin install CsBpRd/dsh-workspace-only-plugin

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

Run dsh plugin install CsBpRd/dsh-workspace-only-plugin in the DeepSeek Harness terminal, or manually add https://github.com/CsBpRd/dsh-workspace-only-plugin to your profile dependencies, apply the core patches, and restart the service.

About this plugin

In dsh's multi-permission model, once a session enters danger-full-access or auto mode, the agent can quietly read and write files outside the working directory with no user awareness or audit trail. dsh-workspace-only-plugin closes that gap with a global "Workspace Only" toggle: when enabled, any file operation that crosses the working-directory boundary is intercepted and surfaces a confirmation prompt on the approval/request channel, deliberately bypassing the approval-policy gate so that even a never-approve session still gets a dialog rather than a silent pass.

The interception spans every tool call—read, write, edit, read_image, glob, grep, bash, pwsh—and extends to absolute paths embedded in inline script strings (node -e, python -c) via a lexical scanner, so the boundary cannot be bypassed through script arguments. When used alongside dsh-auto-mode, the auto plugin's classifier still governs in-workspace calls while out-of-bound calls are routed through this plugin's user-confirmation step first, keeping the two concerns cleanly separated. The workspace-write preset label is permanently renamed to "Write Only" for clearer menu semantics. The toggle is persisted to settings.yaml and takes effect across all sessions immediately, with quick switches in both the settings page and the input bar.

It is well suited for developers who regularly run auto or full-access sessions in dsh and want the flexibility of broad tool access without giving up the safety net of a mandatory confirmation on every out-of-directory operation, as well as for teams that treat agent file access as a security boundary requiring explicit human sign-off.

Use Cases

  • Blocking silent out-of-directory writes in full-access sessions
  • Routing auto-mode out-of-bound calls through a user confirmation prompt
  • Lexically scanning absolute paths embedded in inline script arguments

Best For

  • dsh developers who rely on auto or full-access sessions daily
  • Teams with security or compliance requirements on agent file access
  • Users who want broad tool access with a mandatory out-of-directory confirmation