dsh-gzip

Anyone who has used the DeepSeek Harness Web GUI has likely hit this wall: open a large session, the history list stalls for ten-plus seconds, and then the browser throws a cold "The user aborted a request." The root cause is that each page of history ships every raw event—for the most recent 50 messages, including all streaming chunks—in one shot, easily ballooning to 4 or even 13 MB, while the server applies no compression whatsoever. On remote links (Tailscale, ZeroTier, easytier) or mobile data, the browser's hard 30-second timeout is almost guaranteed to fire.

dsh-gzip does one focused thing: it layers gzip compression onto /api responses right before they are written out. Under the hood it wraps the /api route handler so that when a request negotiates gzip and the response type is compressible, the payload is compressed on the fly. SSE streams, zip exports, already-encoded responses, and requests without Accept-Encoding are all passed through untouched, and no official internals are modified. In real measurements a 13.4 MB history response shrank to 1.16 MB (a 91.4 % reduction), bringing load time on a 3 Mbps line from roughly 36 seconds down to about 3 seconds—well under the timeout.

If you primarily access the DSH Web interface over a remote network, mobile data, or an uplink-constrained home connection, this plugin delivers an immediate improvement: install it, restart the service, and the history loads. It is positioned as a stopgap—once upstream ships response slimming or native compression, the plugin simply fades into a compatibility role; and if it ever becomes irrelevant, uninstalling it is completely clean with zero side effects.