Configuring dsh-smooth-stream
DeepSeek Harness reads the pacing preset from the web profile's cordis.patch.yml. The combined package uses balanced by default.
preset |
Behaviour |
realtime |
Follows model arrival more closely |
balanced |
Default pacing |
silky |
Uses more buffering and catches up more slowly |
Older profile fields, including mode, revealCharsPerSec, scrollSpeedPxPerSec and maxScrollSpeedPxPerSec, can still be loaded for compatibility. The current adaptive engine uses only preset to change pacing.
dsh-smooth-stream user settings
DeepSeek Harness exposes a Smooth stream card under Settings → Plugins → Plugin configuration. Enable smooth stream rendering is on by default. When enabled, dsh-smooth-stream controls reply and tool-row rendering and follow behaviour; when disabled, DeepSeek Harness uses its built-in rendering again.
Automatically expand thinking controls whether thinking blocks open during streaming. When enabled, blocks expand while output is streaming and collapse after thinking ends. When disabled, they stay collapsed unless opened manually. These are user-level persistent preferences, take effect immediately and are written to DeepSeek Harness's user settings document rather than the plugin's profile configuration.
Commands for dsh-smooth-stream
DeepSeek Harness starts the Web UI with pnpm dsh web. The plugin can be removed with dsh plugin --profile web remove dsh-smooth-stream or updated with dsh plugin --profile web update dsh-smooth-stream. dsh plugin --profile web outdated checks for newer versions. The update command applies to npm installations declared by the profile and prompts for a DeepSeek Harness restart.
dsh-smooth-stream behaviour and limits
DeepSeek Harness should show [dsh-smooth-stream] plugin loaded! in the Host log after loading the plugin. With reduced-motion preferences enabled, dsh-smooth-stream displays complete text and does not take over follow scrolling. If frame rate falls below 30 fps while a reply is off-screen, revealing pauses and resumes when conditions allow.
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