YEYEYEYESHIFU/dsh-result-only-view ↗★ 0
dsh-result-only-view
Results-only toggle for the DeepSeek Harness Web GUI: hides thinking and tool-call process nodes so a conversation shows only final answers, while keeping a single live status line (the latest running step) during agent activity. Whitelisted interactive cards (ask_user_question, cordis_run) stay visible; approval prompts always render in the composer. zh-CN / en localized.
安装
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:YEYEYEYESHIFU/dsh-result-only-view说明文档
阅读完整 README ↗dsh-result-only-view
A "Results only" toggle for the DeepSeek Harness Web GUI. When enabled, the conversation hides thinking rows and tool-call nodes, so only user messages and final assistant replies remain visible. Clicking the toggle restores the built-in collapsed-row view; the trajectory view is never affected and stays the full-detail option.
- Default on; the preference is remembered in
localStorage. - One live status line while the agent works: during an active run, only the latest step of the current turn (running tool row, else the last tool row, else the streaming thinking row) is shown with native real-time updates; it disappears when the run settles.
- Restores activity animations on the turn-status line and the running row, even under
prefers-reduced-motion: reduce. - Interactive cards are never hidden:
ask_user_questionandcordis_runrows stay visible, and privileged-execution approval prompts render in the composer itself. - Localized through the client locale service: English (
Results only) and Simplified Chinese (只看结果).
Install
From npm:
dsh plugin --profile web add dsh-result-only-view
Or from a local checkout:
dsh plugin --profile web add file:
Then restart the web profile (dsh web). Uninstall with dsh plugin --profile web remove dsh-result-only-view and restart.
How it works
The plugin registers a small control in the conversation.input.left slot and injects a stylesheet targeting stable product DOM attributes (data-variant="think", data-tool, data-chat-flow-kind, data-subcalls), plus a MutationObserver that keeps exactly one live status line visible while a session runs. No product DOM is modified and no network requests are made; only presentation is affected.