@jamolpe88/dsh-desktop-chat
在 DeepSeek Harness Desktop 中打开官方 DeepSeek Chat Web 应用：侧边栏中的一个入口通过桌面 Shell 的原生浏览器 guest 在中央栏中呈现 chat.deepseek.com，并在重启后保持登录状态。不包含聊天 UI、代理工具或运行时依赖。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @jamolpe88/dsh-desktop-chat@0.1.2Desktop Chat 以 @jamolpe88/dsh-desktop-chat 发布，当前版本为 0.1.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Opens the official DeepSeek Chat web app (chat.deepseek.com) inside DeepSeek Harness Desktop, in the
center panel, through the desktop's native browser guest. One sidebar entry, the real page, and the session
survives closing the app.
Español → README.es.md
The Chat DeepSeek entry in the DSH sidebar, above the workspace list
The entry registers as one more DSH panel. Icon, label and selected state belong to the shell; the plugin only provides the destination.
The official page inside the center panel: not a clone, not an iframe. The native guest keeps the session and the page state while you switch panels.
https://chat.deepseek.com/ in the center panel, with the official interface untouched.GET /api/dsh-desktop-chat/state) and a route to forget the saved session.HttpOnly cookies: DSH does not expose a guest partition's cookie store to plugins.>= 0.2.1-rc.3, profile desktop (a plain web profile provides no native browser guest).From npm:
dsh plugin --profile desktop add @jamolpe88/dsh-desktop-chat
From the repository:
dsh plugin --profile desktop add github:JaMoLpE88/dsh-desktop-chat
From a local checkout, while developing:
dsh plugin --profile desktop add C:\path\to\dsh-desktop-chat
Restart DSH Desktop after installing. The entry appears in the sidebar as Chat DeepSeek.
If the sign-in screen appears after a restart, check the diagnostics below before signing in again: it will tell you whether the snapshot is being written, and why not.
DSH Desktop gives every browser view a process-lifetime session partition (a new random name on each start). A plugin cannot change that, and there is no public API to read the partition's cookies. The session is therefore preserved at the page level:
| Data | Kept? | Where |
|---|---|---|
chat.deepseek.com localStorage (includes userToken) | Yes | %USERPROFILE%\.dsh\dsh-desktop-chat\session.json (or $DSH_HOME) |
Cookies the page can see (document.cookie) | Yes | same file |
HttpOnly cookies (WAF/Cloudflare: cf_clearance, aws-waf-token…) | No | unreachable from a plugin in this DSH |
| Passwords | Never | — |
Honest consequence: DeepSeek authenticates with the token in localStorage, so the session should survive.
Losing the WAF cookies may trigger an anti-bot check after a restart; that is up to the site, not the plugin.
With DSH running, on the same URL as the interface (for example http://127.0.0.1:59863):
curl -H "x-dsh-desktop-chat: 1" http://127.0.0.1:59863/api/dsh-desktop-chat/state
It returns counts and booleans only, never credentials:
{
"ok": true,
"panelId": "deepseek-chat",
"url": "https://chat.deepseek.com/",
"session": {
"file": "C:\\Users\\<user>\\.dsh\\dsh-desktop-chat\\session.json",
"exists": true,
"savedAt": "2026-10-25T09:12:44.120Z",
"hasUserToken": true,
"storageKeys": 24,
"cookieBytes": 275
},
"last": { "restore": { "...": "..." }, "save": { "...": "..." } }
}
hasUserToken is the signal that matters: if it is false after signing in, saving is not reaching the Host
and the session cannot survive. last.save.diag reports why a save was skipped (not-ready, off-origin,
read-failed…). The port changes on every DSH start; take it from the interface URL.
Close the panel, and with DSH running:
curl -X POST -H "x-dsh-desktop-chat: 1" http://127.0.0.1:59863/api/dsh-desktop-chat/session/forget
That deletes the snapshot; the next start will ask for access again. Signing out on the website is also
detected and clears the snapshot. You can also delete ~/.dsh/dsh-desktop-chat/session.json by hand with
DSH closed.
lib/index.js, DSH Host process): registers four routes on ctx.webServer, writes the
snapshot atomically with user-only permissions, and never imports electron. Details and evidence in
docs/architecture.md.lib/client.js): registers the sidebar row (sidebar.panellist) and the panel (main)
under one id, reserves a native guest, and keeps the <webview> outside the React tree so hiding the panel
does not destroy it.localStorage and document.cookie, reloads once, and from
then on saves every 10 s and whenever the panel is hidden.| DSH | >= 0.2.1-rc.3 (the only version tested by the author) |
| Node | >= 22 |
| OS | Windows 11 (tested); macOS and Linux untested |
| Profile | desktop (the web profile has no native guest) |
| Catalog | listed on dsh-plugin.org |
@jaychang1989/dsh-webchat | not required; do not run both at once |
Validation status: tested on Windows 11 with DSH Desktop 0.2.1-rc.3 (2026-10-25). Manual sign-in in the panel, full DSH exit, restart, and the session was still active: on the new start the plugin restored 27 keys — token included — before loading the page, which opened without asking for credentials. Hiding and reshowing the panel keeps the same page (the guest is not remounted).
Not validated: macOS, Linux, other DSH versions, and the behaviour if DeepSeek starts requiring HttpOnly
cookies.
node --test
The tests cover the Host half (routes, snapshot, guards, diagnostics without secrets) and the browser half (slot registration, guest reservation, restore, hide without unmount) against a simulated DOM.
An independent implementation, inspired by jaychang1989/dsh-webchat and its predecessor xmuwenxiang/dsh-web-chat, both Apache-2.0. What was reused (concepts, not code) is listed in NOTICE.