Bugs, questions and feature requests: the repository's issue tracker. Email: hello@corsen.ai. Please never paste a pairing code, a page's content, or anything from a signed-in site into a report.
| Panel says | What it means | What to do |
|---|---|---|
| Welcome | This Chrome has never been paired | Follow the setup card: it says whether the companion is reachable and shows the commands; then type the pairing code (dsh plugin --profile web exec dsh-connector-broker --pairing-code, or the installer's output) |
| Connecting… / Not connected | The companion on 127.0.0.1 is not reachable | Start DeepSeek Harness (the connector starts the broker itself), or dsh plugin --profile web exec dsh-connector-broker, or re-run the installer; check the port in Settings |
| No sessions | No DeepSeek Harness process with the connector installed is running | Start dsh in a profile where the connector was added |
| No tabs attached | The session is selected but controls nothing | Open the tab you want it to work in and press Attach |
| Update required | The extension and the companion speak different protocol versions | Update whichever is older; the two are released together at the same version |
DeepSeek Harness (dsh) 0.1.2-rc.1 or newer, Node.js 22.19 or newer, and pnpm on PATH — dsh plugin forwards to pnpm and DeepSeek Harness does not install it (npm install -g pnpm). The installers check for all three before creating anything.
chrome://, the Web Store) cannot be attached; the panel marks them as restricted.dsh plugin add splits a path containing a space (an upstream limitation); the installer works around it with the file's short name.