Requirements for dsh-tts-bridge
DeepSeek Harness must be running with its Web interface. The browser side requires Chrome, Edge, Brave, or another Chromium-based browser; Firefox is not supported. The “朗读桥” extension must be loaded from the plugin’s extension/ directory, and https://chat.deepseek.com must remain open in a browser session signed in to the user’s own DeepSeek account. Before automated speech works, the user must click DeepSeek’s own read-aloud button once. The README does not specify a separate environment variable or command added by the plugin.
Configuring dsh-tts-bridge
The plugin stores its persistent state at:
<DSH_HOME>/.dsh/tts-bridge.json
This file contains the conversations selected under “听谁” and the saved replies under “收藏”. The README does not document editable configuration keys. A newly installed instance does not automatically monitor every conversation: the user selects the conversations to hear in the plugin card.
How dsh-tts-bridge behaves
DeepSeek Harness loads the plugin in the Web profile and displays a “朗读桥” card after the plugin starts. The card can:
- enable automatic read-aloud by holding the status row for 0.6 seconds;
- stop playback;
- select multiple currently loaded conversations;
- organise, replay, delete, and export saved replies as Markdown.
With automatic read-aloud enabled, a completed turn in a selected conversation is queued. The extension sends the queued text to the open DeepSeek page and activates its read-aloud control. Individual replies can also be played from their own ▶ 朗读 control. Archived or unloaded conversations are removed from the selectable list.
Known limits of dsh-tts-bridge
The extension relies on the DeepSeek web page rather than an API. If the page becomes unavailable or speech remains pending, the README recommends refreshing it; when queued text exists and the page is absent, the extension may reopen a DeepSeek window. The plugin identifies the final reply currently shown on the page, so unrelated page changes can result in the wrong text being read. Read-aloud usage is subject to a daily limit.
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