dsh-fold

In the DeepSeek Harness web chat, a single assistant turn can spawn dozens or even hundreds of consecutive tool calls, interleaved with Think reasoning rows, context injections, compaction notices, and other non-text surfaces. The resulting message stream is extremely hard to scan, and it is difficult to see at a glance what the agent is doing right now or to jump to a specific call and its full output. dsh-fold collapses the consecutive tool-call nodes within one turn into a single compact bar that shows the currently running tool name and the accumulated call count in real time. Think rows, compaction, context, command, model-retry, and every other non-text block fold into the same bar. When expanded, each member renders through the official tool.call.toolview dispatch, so bash, read, grep, web, and subcall cards keep their native product appearance with status, parameters, and output intact; newly arriving calls are appended live and the user's expanded state is never reset. Once a turn closes with a final summary, everything above the summary collapses behind one Turn work process folded bar while the summary stays visible. User messages longer than three lines are clamped to exactly three lines with an Expand toggle. The implementation is pure Slot / React with no DOM patching, no MutationObserver, and no display:none hacks; expanded state lives in React so live-appended calls never interrupt the reader.

dsh-fold is built for developers who run long, multi-tool orchestration turns in DSH. When a single assistant step fires dozens of terminal executions, file reads, searches, and web fetches in sequence, the collapsed one-line status bar keeps the conversation scannable, and expanding it lets you audit every call's full output and error without losing your place. Whether you are debugging a failed tool chain, re-reading intermediate reasoning, or compressing a 288-call turn into a manageable set of fold groups, dsh-fold cuts visual noise dramatically while preserving full inspectability of every individual call.

Because the plugin is written entirely in the official Slot and React layer, it leaves the product untouched at uninstall time: the slot entry, the co-declaration overlay, locale dictionaries, and stylesheet are all removed with the plugin fiber. It adapts to all three DSH release channels (latest, new, and alpha) through a snapshot normalisation seam that fails closed if internals change, so the plugin stays inert rather than breaking the host application.