All plugins

DSH / BUNDLE / CLIENT-UI

dsh-mobile-upgrade

v0.8.1langyo / dsh-mobile-upgrade1c232e5b61

InstallableBundlesUI & client pluginsCommunity · Topic auto-analysisWeb UI

Overview

dsh-mobile-upgrade

Mobile UI fixes for the DeepSeek Harness web profile: a restart row, input-modality switches, a narrow-screen drawer and settings tabs, a full-width model menu, a stuck-request network chip, a scrollable question region, a throttled reaction to streaming message storms, a guarded subagent-catalog refresh, click-to-open lineage chips, a narrow-header collector sheet, and a throttled session-list render under background streaming load.

README / EN

Package documentation

Registry summary

Mobile UI fixes for the DeepSeek Harness web profile: a restart row, input-modality switches, a narrow-screen drawer and settings tabs, a full-width model menu, a stuck-request network chip, a scrollable question region, a throttled reaction to streaming message storms, a guarded subagent-catalog refresh, click-to-open lineage chips, a narrow-header collector sheet, and a throttled session-list render under background streaming load.

dsh.pub verifies the pinned bundle contract, runtime facts, and distribution semantics. The complete README remains in the source repository.

Read the full README on GitHub

LIMITATIONS

Known limitations

- The client hooks specific host UI elements by their hashed CSS class names (menu, drawer toggle, provider editor, session-header chips). A host build that renames them degrades individual features until this plugin catches up; everything else keeps working. The question card's question region is found through the card's own `data-question-key` hook instead, so a host rebuild that merely rehashes its CSS modules keeps it working. - The header collector and the lineage click shim ride the host's own data (the live session list and its subagent catalogs); they add no requests beyond the guarded branch fetches, and a tap on a row whose mode is still loading completes on its own once that catalog lands. - Input-modality switches can only patch provider routes you have customised yourself; catalog-only routes are read-only by design, because fabricating a catalog section collapses the model directory.