dsh-ballute

DeepSeek Harness has a quiet blind spot that drives plugin operators crazy: when a plugin crashes at runtime, the framework silently strips the failing slot, the panel goes blank, the tab vanishes, and the only trace of what happened is a console error you may never scroll to back to. Which plugin broke, on which line, and why? No clue. Can you disable it without rebooting the whole instance? Not really. dsh-ballute exists to turn that silent abdication into something you can see, attribute, and recover from.

It lays down five lines of defense. Before anything loads, a static contract inspection checks structural integrity and flags faults early. When a crash does happen at runtime, an official error hook fires a crash card in the bottom-right corner showing the plugin name, slot key, and the exact error. Every crash is appended to a local JSONL black-box log that survives restarts, and a boot-graph hash pinpoints which code version was running. One click on the crash card disables the offender by writing a patch layer and unloading it via HMR — no full restart needed. And when the main profile's UI is so broken that nothing opens, a safe-mode profile (official bundle plus ballute only) boots a minimal instance from which you can inspect and disable plugins cross-profile, rescuing a dead profile without guessing.

It is for anyone running two or more third-party DSH plugins who is tired of staring at a blank panel and shrugging, for teams that need traceable crash records and fast stop-the-bleeding without rolling back or restarting, and for tinkerers who want the peace of mind that a single bad plugin will not take down their entire workspace. If your profile only ships the built-in plugins, you will never need it. The moment you start adding community plugins to the mix, this parachute may well be the thing that saves your session.