DeepSeek Harness plugin

dsh-web-chat

Codex-ChatGPT-mode style web chat for DeepSeek Harness: chat through chat.deepseek.com (deepseek-chat) using your DeepSeek web session instead of API billing, then transfer the conversation into a

Jump to install

Source facts

Repository
xmuwenxiang/dsh-web-chat
Latest update
Aug 20, 2026
Category
Memory
GitHub stars
0
Format
plugin
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/xmuwenxiang/dsh-web-chat
Plugin: dsh-web-chat
Author: xmuwenxiang

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer3 files
README.mdSource · read only

dsh-webchat

A "Codex ChatGPT mode" plugin for DeepSeek Harness: drive chat.deepseek.com with a real browser, chat with deepseek-chat (and deepseek-reasoner) using your DeepSeek web session — no API billing. Transfer a conversation into a harness session as development context (distilled into an executable task brief), import stored web conversations as markdown context, or let the harness agent keep chatting through the same web session.

Features

  • Web chat over your DeepSeek web login, with streaming replies and "Deep Think (R1)" / "Web Search" toggles.
  • Transfer to Harness: distill the current conversation into a task brief and open it as a new harness session to continue development.
  • Import as context: export a stored web conversation to markdown.
  • Agent tools: webchat_status, webchat_send, webchat_import, webchat_transfer.
  • Hands-free login: first use opens a visible browser window for login, which auto-closes afterward; chat then runs headless.

Install

From npm (once published)

dsh plugin --profile web add dsh-webchat

From GitHub

dsh plugin --profile web add github:xmuwenxiang/dsh-web-chat

> lib/ is committed, so git installs need no build step.

First use

<img width="1920" height="958" alt="image" src="https://github.com/user-attachments/assets/2df5acdb-b0b5-404a-a381-3dba98650baa" />

<img width="1920" height="958" alt="image" src="https://github.com/user-attachments/assets/7516776d-0b58-452c-bd58-e35ea39dc4ac" />

1. Open the "网页聊天" (Web Chat) sidebar entry in the Web GUI. 2. Click "打开登录窗口" and sign in to DeepSeek in the browser window that appears. 3. The window auto-closes after login; you can then chat and transfer normally.

Config

Settings expose: browserChannel (default auto), browserExecutablePath, browserProxy, browserHeadless (chat headless; default true — the login window is always visible and auto-closes), replyTimeoutMs, and transferDistill / transferProvider / transferModel (distillation model for transfer).

Requirements

  • Node.js >= 22
  • Google Chrome or Microsoft Edge installed
  • A graphical session for the one-time login window

Limitations

  • The web app is subject to DeepSeek's own risk controls; failures or page changes return errors rather than crashing.
  • Session credentials live in a local private profile directory.

License

[Apache-2.0](./LICENSE)