SaiSenBox/dsh-boot-guard

Loader-independent startup recovery for DSH Web that detects likely broken plugins, temporarily skips them, and restores only Boot Guard-managed changes.

A small insurance policy for the DeepSeek Harness Web UI: normally it sits quiet; when plugin loading fails and the page is stuck on 'Failed to load plugins', Boot Guard appears and helps you find the suspect plugin, skip it temporarily, and rescue the workspace. It does not depend on the normal client plugin loading chain — the host injects a small rescue script into the failing page, so it still works when other plugins did not load. Features: auto-selects suspected plugins from load errors (user plugins by default, searchable by name or loader entry id), temporary skip (with re-try on refresh), per-plugin recovery or restore-all, clear distinction between 'Boot Guard temporary skip' and 'disabled in config', a copyable diagnosis snippet, EN/中文 UI following DSH language, and dark/light/narrow-screen read-only self-check pages. It never deletes plugins or touches plugin data — 'skip' writes a Boot Guard-marked entry into the profile's cordis.patch.yml.

Development & Runtime ★ 4 updated 2026-08-15
View on GitHub ↗

Install

dsh plugin --profile web add github:SaiSenBox/dsh-boot-guard

GitHub install per README (English edition): dsh plugin --profile web add github:SaiSenBox/dsh-boot-guard, then restart dsh web. npm path (dsh plugin --profile web add dsh-boot-guard) is documented once the package is published. Windows local dev: powershell -ExecutionPolicy Bypass -File .\install.ps1 (stages the dependency beside the DSH profile to avoid malformed cross-drive file: junctions).

Compatibility

DeepSeek Harness web profile. Host-injected rescue script — works even when the normal client plugin loading chain fails.

Details

Recent updates

boot-time plugin rescue; works when the plugin chain fails; suspect detection + temporary skip; per-plugin recovery; never deletes data.

FAQ

When does it activate?
Only when plugin loading fails and the page is stuck on 'Failed to load plugins' — normally it stays quiet.
Does it delete plugins?
No — it never deletes plugins or touches plugin data; 'skip' writes a Boot Guard-marked entry into cordis.patch.yml.
Why can it still run when others fail?
The host injects a small rescue script into the failing page directly — it does not depend on the normal client plugin loading chain.

Alternatives

SaiSenBox/dsh-prompt-manager · titanwings/dsh-better-browser · Relistencode/dsh-extension-hub

More plugins in Development & Runtime

Browse more in Development & Runtime

Guides for Development & Runtime plugins