@jaychang1989/dsh-webchat 0.3.0 → 0.4.1

package/NOTICE

@@ -1,11 +1,11 @@
 dsh-webchat
 Copyright 2026 jaychang1989
 
-This product is a maintained fork of dsh-web-chat
+This product is a fork of dsh-web-chat
 (https://github.com/xmuwenxiang/dsh-web-chat), Copyright the dsh-web-chat
 authors, licensed under the Apache License, Version 2.0.
 
-The fork retargets the plugin at the DeepSeek Harness 0.2.x plugin APIs:
+0.3.0 retargeted the plugin at the DeepSeek Harness 0.2.x plugin APIs:
 
   * the settings section is no longer registered by the plugin
     (`installSettingsSection` / `settingsNamespace` were removed from
@@ -15,4 +15,11 @@ The fork retargets the plugin at the DeepSeek Harness 0.2.x plugin APIs:
     (`sessionPersistence.open` / `create` + handle `read` / `append` / `flush`)
     instead of the retired service-level `load` / `append` pair.
 
-See MAINTAINING.md for the exact files and the shipped-build policy.
+0.4.0 reduced the package to a launcher: it opens the official
+chat.deepseek.com web app in a window instead of driving the page and
+re-rendering the conversation. The custom chat panel, the local transcript
+store, the five `webchat_*` agent tools, the transfer/distillation code and
+thirteen of the fifteen HTTP routes were removed, along with the
+`playwright-core` runtime dependency and the React-based client build.
+
+See MAINTAINING.md for the current structure and the constraints behind it.

package/README.md

@@ -1,78 +1,83 @@
 # dsh-webchat
 
-Codex-ChatGPT-mode style web chat for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness): a real browser drives [chat.deepseek.com](https://chat.deepseek.com), so you chat with the DeepSeek web model through your own web login — **no API billing**. A conversation can be transferred into Harness: it is distilled into an executable task brief and opened as a new harness session, imported as markdown context, or continued by the harness agent through the same web session.
+Opens the official [chat.deepseek.com](https://chat.deepseek.com) web app from inside [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness): one sidebar entry, and **clicking it opens the official page directly**.
 
-> **This is a maintained fork of [xmuwenxiang/dsh-web-chat](https://github.com/xmuwenxiang/dsh-web-chat).** The unmaintained upstream release **cannot start** on dsh 0.2.x. This fork retargets the plugin at the dsh 0.2.x plugin APIs. License stays Apache-2.0.
-> See [MAINTAINING.md](./MAINTAINING.md) and [NOTICE](./NOTICE) for the exact difference.
+**It no longer reimplements the chat UI.** The official web app is the client — model picker, deep think, smart search, history and attachments all live there. This plugin opens it and nothing else.
 
-## Difference from upstream
+## Why a window, and not a pane
 
-| Area | Upstream on dsh 0.2.x | This fork |
-| --- | --- | --- |
-| Startup | `installSettingsSection` and `settingsNamespace` were removed from `@deepseek-ai/dsh-settings` in dsh 0.1.7, so the host half fails at ESM link time and the whole `webchat` entry reports `failed to import` — the plugin never loads | Uses the Loader-owned settings form (namespace = profile entry id, schema = this package's exported `Config`); the plugin no longer registers a settings section |
-| Transfer to Harness | `sessionPersistence.load(id)` and `persistence.append(id, events)` became a **handle-based** API in dsh 0.2.x, so the call throws | Migrated to the `SessionHandle` returned by `open(id, 'write')` / `create(header)`, using `handle.read` / `append` / `flush` / `close` |
-| Dependency declarations | `devDependencies` pinned at `@deepseek-ai/*: ^0.1.0-rc.7` | Updated to 0.2.x, plus runtime `peerDependencies` and `engines.dsh` |
+Both embedding routes are closed, and that is a measurement rather than a choice:
 
-## Install
+- `chat.deepseek.com` answers with **`Content-Security-Policy: frame-ancestors 'none'`**, so no iframe can host it;
+- the desktop build runs both windows with **`webviewTag: false`** and blocks `will-attach-webview`, so `<webview>` is unavailable too.
+
+A real window is therefore the only faithful way to show the official page.
+
+## What opens, in order
 
-From npm (prebuilt — no build step, no `allowBuilds` approval):
+Clicking the entry tries these in order and reports which one worked in a short toast:
+
+1. **`app-window`** — a window created by the DSH desktop process itself (the desktop app is Electron). An already-open one is focused instead of duplicated.
+2. **`app-window-shell`** — a chromeless Edge/Chrome window (`--app=`) with its own `--user-data-dir` (`~/.dsh/dsh-webchat/app-window`), so its login stays separate from your everyday browser. Used when the host refuses (1).
+3. **`system-browser`** — handed to the OS default browser, so the button always does something.
+
+Sign in once; the window's own profile keeps the session.
+
+## Install
 
 ```bash
 dsh plugin --profile desktop add @jaychang1989/dsh-webchat
 ```
 
-Or straight from this repository (also prebuilt, `lib/` is committed):
+Or straight from this repository:
 
 ```bash
 dsh plugin --profile desktop add github:jaychang1989/dsh-webchat
 ```
 
-> The npm package is scoped because the unscoped `dsh-webchat` name belongs to the unmaintained upstream project. The plugin's own identity is unchanged by the scope: the entry id stays `webchat`, and so do the `/api/dsh-webchat` routes, the data directory and the locale namespace.
-
-**Switching from upstream:** both packages insert the same `id: webchat` row, and one profile cannot hold the same entry id twice — boot fails on the duplicate. Remove the upstream package first (the Plugin Manager UI, or `dsh plugin --profile desktop remove dsh-webchat`), then add this one.
-
-**Restart the DSH desktop app afterwards** — an entry that failed during startup is not hot-reloaded.
+> The npm package is scoped because the unscoped `dsh-webchat` name belongs to the unmaintained upstream project. The scope does not change the plugin's identity: the entry id stays `webchat`.
 
-## First use
+**Switching from upstream, or from this plugin's 0.3.x:** all of them insert the same `id: webchat` row, and one profile cannot hold the same entry id twice — boot fails on the duplicate. Remove the old package first, then add this one, then restart the desktop app.
 
-1. Open the "网页聊天 / Web chat" entry in the Web GUI sidebar.
-2. Click "打开登录窗口" and complete the DeepSeek web login in the window that opens.
-3. The window closes itself once you are logged in; chatting then runs headless.
+## Use
 
-## Features
+1. Click the "DeepSeek 网页 / DeepSeek Web" entry in the sidebar — the page opens directly, there is no second click.
+2. Sign in once in the window it opens; afterwards just use the official web app.
 
-- **Web chat** — reuses your DeepSeek web login, streams replies, with "deep think (R1)" and "smart search" toggles.
-- **Transfer to Harness** — distill the current web conversation into a task brief and open it as a new harness session (first message is the brief), or continue an existing session by appending the brief to it; the transfer can target a registered workspace.
-- **Recover from the web** — pull web-side conversations that are not in the local store yet (panel button / `webchat_recover`).
-- **Import as context** — export a stored web conversation as markdown context.
-- **Agent tools** — `webchat_status`, `webchat_send`, `webchat_recover`, `webchat_import`, `webchat_transfer`, callable by the harness agent directly.
-- **Effortless login** — the login window is visible once, then closes itself; chatting afterwards is headless.
+A toast in the corner reports the outcome: `已打开 DeepSeek 网页` / `已交给系统默认浏览器打开` / a failure reason (an `HTTP 404` usually means the host half is still an older version — restart the desktop app).
 
-## Configuration
+## Difference from 0.3.x — this release deletes most of the plugin
 
-The settings form follows the profile entry (`webchat`) and is generated from this package's `Config`: `browserChannel` (default `auto`), `browserExecutablePath`, `browserProxy`, `browserHeadless` (default `true` — the login window is always visible and closes itself), `replyTimeoutMs`, `transferDistill` / `transferProvider` / `transferModel` (distillation model for transfers), `transferMaxTokens` (final brief cap, default 4096), `transferChunkTokens` (per-chunk cap for long conversations, default 1024).
+| 0.3.x | 0.4.0 |
+| --- | --- |
+| Drove the page with Playwright and re-rendered messages in a custom panel | Does not drive the page; opens it. Custom panel removed |
+| Five agent tools (`webchat_status/send/recover/import/transfer`) | All removed |
+| "Transfer to Harness", "recover from web", "import", "export" | All removed |
+| Local transcript store at `~/.dsh/dsh-webchat/transcripts.json` | Removed (only the window profile directory remains) |
+| Fifteen `/api/dsh-webchat/*` routes | Two: `state` and `open` |
+| Depended on `playwright-core`; the client half needed React and a bundler | **No runtime dependencies**; plain-DOM client, no build step |
+| ~3800 lines of build output | ~700 lines of hand-written JS |
 
 ## Requirements
 
 - DeepSeek Harness **0.2.0-rc.1 or a newer 0.2.x**
 - Node.js >= 22
-- Google Chrome or Microsoft Edge installed
-- An interactive desktop for the one-time login window
+- Strategy 2 needs Edge or Chrome installed; strategy 1 does not
 
 ## Limitations
 
-- The DeepSeek web front end is rate-limited and can change; failures return errors instead of crashing.
-- Credentials and session data live in a local private directory (the profile) — do not share it.
-- "Continue an existing session" on dsh 0.2.x needs that session to be free of another writer (for example it must not be open in the GUI holding the write lease). A taken session returns an explicit error rather than failing silently.
+- The DeepSeek web front end applies its own rate limiting; the plugin hands the page over and does not mediate its login or requests.
+- A strategy-1 window is owned by the DSH process: if you close the DSH main window while it is still open, DSH will not quit (Electron's `window-all-closed`). Close that window too.
+- Reloading the plugin does not close a window that is already open, so a settings change cannot close the conversation you are reading.
 
-## Development
-
-`lib/` is committed as the shipped build and is what a git install runs. Host-half changes must be mirrored in `src/` and `lib/` until the build pipeline is restored — see [MAINTAINING.md](./MAINTAINING.md).
+## Development and tests
 
 ```bash
-node --test        # unit tests (Node's built-in test runner)
+node --test        # 11 cases: host routes, window-strategy selection, and the browser half mounted into a DOM stand-in
 ```
 
+There is no build step: `lib/index.js` and `lib/client.js` are the hand-written runtime. See [MAINTAINING.md](./MAINTAINING.md).
+
 ## License
 
 [Apache-2.0](./LICENSE). Original copyright belongs to the authors of [xmuwenxiang/dsh-web-chat](https://github.com/xmuwenxiang/dsh-web-chat); see [NOTICE](./NOTICE).

package/README.zh.md

@@ -1,83 +1,83 @@
 # dsh-webchat
 
-为 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) 提供的「Codex ChatGPT 模式」插件：通过真实浏览器驱动 [chat.deepseek.com](https://chat.deepseek.com)，用你的 DeepSeek 网页登录会话与网页模型对话，**无需 API 额度**。对话可「转移到 Harness」——蒸馏成可执行任务简报并新建 harness 会话作为开发上下文，也可把网页对话导入为 markdown 上下文，或让 harness agent 直接通过同一个网页会话提问。
+在 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) 里打开 [chat.deepseek.com](https://chat.deepseek.com) 官方网页版：侧边栏一个入口，**点一下就直接打开官方页面**。
 
-> **这是 [xmuwenxiang/dsh-web-chat](https://github.com/xmuwenxiang/dsh-web-chat) 的维护分支（fork）**，已停止维护的上游版本在 dsh 0.2.x 上**无法启动**。本分支把插件重新对准 dsh 0.2.x 的插件 API，许可证沿用 Apache-2.0。
-> 差异与原因见 [MAINTAINING.md](./MAINTAINING.md) 与 [NOTICE](./NOTICE)。
+**不再重新实现聊天界面。** 官方网页版本身就是完整的客户端——模型选择、深度思考、智能搜索、历史记录、附件上传都在里面。本插件只负责把它打开，别的一概不管。
 
-## 与上游的差异
+## 为什么是「开一个窗口」，而不是「嵌在面板里」
 
-| 问题 | 上游（dsh 0.2.x 上） | 本分支 |
-| --- | --- | --- |
-| 启动 | `installSettingsSection` / `settingsNamespace` 在 dsh 0.1.7 起已从 `@deepseek-ai/dsh-settings` 移除，宿主半区在 ESM 链接期报错，整条 `webchat` entry `failed to import`，插件**完全不加载** | 改为使用 Loader 自带的设置表单（命名空间 = profile entry id，schema = 本包导出的 `Config`），插件不再自行注册设置段 |
-| 转移到 harness | `sessionPersistence.load(id)` / `persistence.append(id, events)` 在 dsh 0.2.x 已改为**句柄式** API，调用即抛错 | 迁到 `open(id, 'write')` / `create(header)` 返回的 `SessionHandle`，用 `handle.read` / `append` / `flush` / `close` |
-| 依赖声明 | `devDependencies` 停留在 `@deepseek-ai/*: ^0.1.0-rc.7` | 更新到 0.2.x，并补上运行时 `peerDependencies` 与 `engines.dsh` |
+两条路都被封死了，这是实测结论而非选择：
 
-## 安装
+- `chat.deepseek.com` 返回 **`Content-Security-Policy: frame-ancestors 'none'`** —— 任何 iframe 嵌入都会被浏览器拒绝；
+- DSH 桌面端两个窗口都是 **`webviewTag: false`**，且 `will-attach-webview` 被显式拦截 —— `<webview>` 也不可用。
 
-从 npm 安装（预构建产物，免构建、免 `allowBuilds` 授权）：
+所以忠实呈现官方页面的唯一方式就是开一个真实窗口。
 
-```bash
-dsh plugin --profile desktop add @jaychang1989/dsh-webchat
-```
+## 打开顺序
 
-或直接从本仓库安装（同样是预构建，`lib/` 已提交）：
+点击入口后会按顺序尝试，第一个成功的生效，结果用一条短提示告诉你实际用了哪种：
+
+1. **`app-window`** —— 由 DSH 桌面端进程直接创建的窗口（桌面端就是 Electron）。已经开着就聚焦，不会重复开第二个。
+2. **`app-window-shell`** —— 无边框的 Edge/Chrome 窗口（`--app=`），使用独立 `--user-data-dir`（`~/.dsh/dsh-webchat/app-window`），因此登录态与你的日常浏览器互不干扰。用于第 1 种被宿主拒绝的场景。
+3. **`system-browser`** —— 交给操作系统默认浏览器，保证按钮任何时候都有反应。
+
+登录一次即可：窗口自己的 profile 会保留登录态。
+
+## 安装
 
 ```bash
-dsh plugin --profile desktop add github:jaychang1989/dsh-webchat
+dsh plugin --profile desktop add @jaychang1989/dsh-webchat
 ```
 
-> npm 包名带 scope，是因为不带 scope 的 `dsh-webchat` 属于已停止维护的上游项目。scope 不影响插件自身身份：entry id 仍是 `webchat`，`/api/dsh-webchat` 路由、数据目录与 locale 命名空间也都不变。
-
-**从上游切换过来时**：上游包与本包都插入 `id: webchat` 这一行，同一个 profile 里同时存在会因 entry id 重复而在启动时报错。请先移除上游包：
+或直接从仓库安装：
 
 ```bash
-dsh plugin --profile desktop remove dsh-webchat
 dsh plugin --profile desktop add github:jaychang1989/dsh-webchat
 ```
 
-改完请**重启 DSH 桌面端**（启动期已判定失败的 entry 不会热重载）。
+> npm 包名带 scope，因为不带 scope 的 `dsh-webchat` 属于已停止维护的上游项目。scope 不影响插件身份：entry id 仍是 `webchat`。
 
-## 首次使用
+**从上游或本插件 0.3.x 切换过来时**：它们都插入 `id: webchat` 这一行，同一个 profile 里不能并存（entry id 重复会在启动时报错）。先移除旧的再加新的，然后重启桌面端。
 
-1. 打开 Web GUI 侧边栏「网页聊天」入口。
-2. 点击「打开登录窗口」，在弹出的浏览器中完成 DeepSeek 网页登录。
-3. 登录成功后窗口会自动关闭，之后即可正常聊天 / 转移。
+## 使用
 
-## 特性
+1. 点侧边栏的「DeepSeek 网页」入口 —— 页面直接打开，不需要再点第二次；
+2. 在弹出的窗口里登录一次，之后正常使用官方网页版。
 
-- **网页聊天**：复用 DeepSeek 网页端登录，流式获取回复，支持「深度思考（R1）」与「智能搜索」开关。
-- **转移到 Harness**：一键把当前网页对话蒸馏成任务简报（首条消息即简报）并创建新 harness 会话继续开发，或「延续到已有会话」——把简报作为新消息追加进指定会话；转移时可选择目标工作区（未选则归入「未分组」）。
-- **从网页恢复会话**：把网页端已存在但本地未收录的会话拉回本地存储（面板「从网页恢复」按钮 / `webchat_recover`）。
-- **导入为上下文**：把存储的网页对话导出为 markdown 上下文。
-- **Agent 工具**：`webchat_status` / `webchat_send` / `webchat_recover` / `webchat_import` / `webchat_transfer`，harness agent 可直接调用。
-- **无感登录**：首次使用弹出可见浏览器窗口完成登录，登录后窗口自动关闭，后续聊天在无头浏览器中进行。
+点击后右下角会有一条短提示说明结果：`已打开 DeepSeek 网页` / `已交给系统默认浏览器打开` / 失败原因（例如 `HTTP 404`，通常意味着宿主半区还是旧版本，重启桌面端即可）。
 
-## 配置
+## 与 0.3.x 的差异（这是一次大幅删减）
 
-插件设置跟随 profile entry（`webchat`）自动生成，可调整：`browserChannel`（浏览器渠道，默认 auto）、`browserExecutablePath`（显式浏览器路径）、`browserProxy`（代理）、`browserHeadless`（聊天是否无头，默认 true——登录窗口始终可见且登录后自动关闭）、`replyTimeoutMs`（回复等待上限）、`transferDistill` / `transferProvider` / `transferModel`（转移时的蒸馏模型）、`transferMaxTokens`（最终简报输出上限，默认 4096）、`transferChunkTokens`（长对话分块摘要每段上限，默认 1024）。
+| 0.3.x | 0.4.0 |
+| --- | --- |
+| 用 Playwright 驱动网页，自研聊天面板重新渲染消息 | 不再驱动网页，直接开官方页面；自研面板删除 |
+| 5 个 agent 工具（`webchat_status/send/recover/import/transfer`） | 全部删除 |
+| 「转移到 harness」「从网页恢复」「导入」「导出」 | 全部删除 |
+| 本地会话存储 `~/.dsh/dsh-webchat/transcripts.json` | 删除（只留窗口 profile 目录） |
+| 15 条 `/api/dsh-webchat/*` 路由 | 只剩 2 条：`state` / `open` |
+| 依赖 `playwright-core`，客户端产物需 React + 构建器 | **零运行时依赖**，客户端为纯 DOM，无构建步骤 |
+| 约 3800 行（构建产物） | 约 700 行（手写 JS） |
 
 ## 环境要求
 
 - DeepSeek Harness **0.2.0-rc.1 或更新的 0.2.x**
 - Node.js >= 22
-- 已安装 Google Chrome 或 Microsoft Edge
-- 首次登录需要可交互的图形环境（弹出登录窗口）
+- 第 2 种策略（无边框窗口）需要本机装有 Edge 或 Chrome；第 1 种策略不需要
 
 ## 限制
 
-- 网页端受 DeepSeek 官方风控；页面改版或操作失败时返回错误而非崩溃。
-- 密码/会话凭据保存在本地私有目录（profile），请勿外泄。
-- 「延续到已有会话」在 dsh 0.2.x 上需要该会话未被其它写入方占用（例如未在界面上打开并持有写租约）；被占用时会返回明确错误而不是静默失败。
-
-## 开发
+- 官方网页端受 DeepSeek 官方风控；页面打不开时插件只负责把页面交出去，不介入其登录或请求。
+- 第 1 种策略创建的窗口由 DSH 进程拥有：若你先关掉 DSH 主窗口、而它仍开着，DSH 不会退出（Electron 的 `window-all-closed` 语义）。关掉该窗口即可。
+- 插件被重载时不会主动关闭已经打开的窗口（避免一次设置变更就关掉你正在看的会话）。
 
-`lib/` 是随仓库提交的编译产物，从 git 安装直接使用它。宿主半区改动需要同步 `src/` 与 `lib/`（构建流水线尚未恢复，见 [MAINTAINING.md](./MAINTAINING.md)）。
+## 开发与测试
 
 ```bash
-node --test        # 运行单元测试（Node 内置测试运行器）
+node --test        # 11 个用例：宿主路由、窗口策略选择、浏览器半区在 DOM 桩里的挂载与按钮行为
 ```
 
+没有构建步骤：`lib/index.js` 与 `lib/client.js` 就是手写的运行时代码。详见 [MAINTAINING.md](./MAINTAINING.md)。
+
 ## License
 
 [Apache-2.0](./LICENSE) — 原始版权归 [xmuwenxiang/dsh-web-chat](https://github.com/xmuwenxiang/dsh-web-chat) 作者所有，详见 [NOTICE](./NOTICE)。

package/cordis.patch.yml

@@ -6,13 +6,14 @@
 #   dsh plugin --profile <name> add github:jaychang1989/dsh-webchat
 #
 # The row is a bare plugin by package name: the node half (exports ".") runs in
-# the host process (DeepSeek web browser engine, /api/dsh-webchat routes, agent
-# tools), and the `dsh.client` declaration in package.json makes the browser
-# half (exports "./client", served at /plugins/<id>/client.js) load in the web
-# GUI. `name` must be this package's manifest name verbatim (scoped names
-# included) — dsh-client-modules keys every browser row by it, and lib/client.js
-# registers its factory under the same id. `id` is the profile entry id; dsh >=
-# 0.1.7 also uses it as the settings form namespace, so keep it stable.
+# the host process — it registers the two /api/dsh-webchat routes and opens the
+# page in a window — and the `dsh.client` declaration in package.json makes the
+# browser half (exports "./client", served at /plugins/<id>/client.js) load in
+# the web GUI as the sidebar entry and its panel. `name` must be this package's
+# manifest name verbatim (scoped names included) — dsh-client-modules keys every
+# browser row by it, and lib/client.js registers its factory under the same id.
+# `id` is the profile entry id; dsh >= 0.1.7 also uses it as the settings form
+# namespace, so keep it stable.
 #
 # Note: the upstream package xmuwenxiang/dsh-web-chat inserts the same
 # `id: webchat`. Do not keep both installed in one profile — a duplicate entry