AuraxM/dsh-plugin-confirm-check

Confirm Mode swaps per-command permission prompts for task-level confirmation: instead of approving every mutating command, you grant a task and the plugin adds step reminders and model-facing reminders so the agent stays inside the granted scope. The README documents what needs an application (mutating commands such as git commit/push, npm install and deletions), the tools and /confirm-mode command it adds, the composer toggle, and card presentation. The README's own comparison table in the sibling doc-present plugin frames the pair as task-level permission rather than per-command gating; mounts can be global (host plane, all sessions) or per session (agent preset), with the same row in either place.

Other ★ 0 updated 2026-08-17 ✅ runtime-tested
View on GitHub ↗

Install

⚠️ Install command not yet confirmed — check the README on GitHub for the exact command.

Compatibility

DeepSeek Harness web profile for the host-plane mount; the row consumes the host registries tools, systemPrompt, commands, userQuestions and agents and publishes no service, so it needs no isolate realm. Toggle and grant state are process-wide: switching the mode off in one session switches it off for every session.

Details

Recent updates

The README documents the permission model and mount contract rather than a versioned changelog: mutating commands require an application, the toggle and grant state are process-wide, and the session-mode picker reflects preset directories. It also warns to validate a custom composition with the harness preset tools (standingKeyFor) before relying on it.

FAQ

How do I install dsh-plugin-confirm-check?
Manually: copy the repository to $HOME/.dsh/profiles/node_modules/dsh-confirm-mode, then add an insert row (id: confirm-mode, name: dsh-confirm-mode) to the web profile's cordis.patch.yml (all sessions) or to an agent preset (per session). There is no npm package or install script.
Does the toggle apply per session?
No — the README states the toggle and grant state are process-wide: switching the mode off in one session switches it off for every session.
Why does a new preset show up in the session-mode picker?
The picker is the preset roster; the README notes that every preset directory appears there as a session mode, so installing the package never adds a mode by itself — only a preset directory does.

Alternatives

deepseek-ai/deepseek-harness · awesome-dsh-plugin/awesome-dsh-plugin · yjh051108/dsh-routing-suite

More plugins in Other

Browse more in Other

Guides for Other plugins