How dsh-auto-collapse behaves
DeepSeek Harness loads dsh-auto-collapse in the web profile as a browser-side DOM plugin. For each turn, it rebuilds segments from the current DOM order. The last assistant-step containing text or media is treated as the final response; earlier process text remains inside the workflow. user, steering and turn-tail nodes are hard boundaries.
A completed turn becomes one row showing processed in Xs. Expanding it reveals context injection, thinking, tool calls, process text and final text. Tool-call groups and thinking blocks then receive their own chips. Adjacent tool calls merge until a正文 boundary; consecutive thinking blocks merge into one level-three block. Running chips follow streaming updates, and reduced-motion preferences disable animations.
Configuring dsh-auto-collapse
Open Settings → Plugins → Plugin configuration and edit the “status prompt”. The default is Deep sleeping.... Saving an empty value restores the official Deep diving... text. The plugin otherwise requires no configuration.
DeepSeek Harness lifecycle and commands
After installation, DeepSeek Harness requires a web-service restart or a plugin HMR trigger, followed by a browser hard refresh with Ctrl+Shift+R. During repository development, npm run check performs TypeScript checking, builds the bundle and runs regression tests. npm run deploy performs the documented local deployment flow, including backup, restart, hash verification and rollback.
dsh-auto-collapse development variables
The local deployment script accepts these environment variables:
| Variable |
Purpose |
DSH_AUTO_COLLAPSE_LIB |
Override the plugin bundle path |
DSH_DIR |
Override the DSH directory |
DSH_WEB_PORT |
Override the web port |
DSH_LOG_DIR |
Override the log directory |
The README documents no version requirement. The plugin restores fold, hide and label changes when stopped through HMR or uninstalled, including inline display values saved before modification.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub