dsh-mini-remote 0.1.0 → 0.1.4

package/CHANGELOG.md

@@ -2,6 +2,84 @@
 
 本文件记录每个版本改了什么。格式参考 [Keep a Changelog](https://keepachangelog.com/zh-CN/1.1.0/)，版本号遵循 [语义化版本](https://semver.org/lang/zh-CN/)。
 
+## [0.1.4] - 2026-09-27
+
+### 新加的
+
+- **模型执行过程中的自言自语，现在由鲸鱼娘念出来。** 她在干活时会开口说一句——念的是模型写给人看的那句旁白（「我先看一下这个文件」）。**句子多长就显示多长**：气泡跟着长高，整页给它让位（只有几屏那种病态长文才会让气泡内部滚动）。**没有旁白就不说话**（气泡留着上一句），**它自己想的那些不上手机**，不分中英文。说的时长跟着句子长短走（2026-09-27 起：短句 15 秒起步、每字再加 0.15 秒、最多 30 秒；之前一律 10 秒）；这期间轮播**停住**，说完了回到被打断的那一格接着走，不是从第一张重来。同一句不会重复念。
+  - **回答区一个字都不动。** 这句话只进鲸鱼娘的说话气泡，不进「最新回复」，不进聊天记录，不冒充「正在写」。2026-09-22 你说过过程的文字别出现在手机上——那次说的是它**落进回答区**（刷屏、把真正的回复挤走）；这次它落在气泡里，不在回答区。这条界线写在 `工程说明.md` 的不变式 20 里。
+  - **配套一张新的立绘**（说话的动作，两帧），风格和配色跟已有的八张一致。
+  - **思考不上气泡**（2026-09-27 你定的口径）：模型想事情的习惯是英文、也常是长段落，念出来既看不懂也不是给你的话。气泡里出现的每一句，都是它特意写给人看的那句。所以她有时会安静一会儿——那不是坏了。
+  - **句子不被截断**（2026-09-27 你报的）：以前电脑侧掐到 80 字、手机侧又限三行，两句长话凑起来就是"话说了一半"——第四行只剩上半截。现在两处截断都撤了，话完整显示；气泡长高时整页跟着让位。
+  - **气泡里的话会渲染 markdown**（2026-09-27 你报的）：以前气泡是纯文本，`**重启把连接掐断**` 连星号一起显示。现在跟回答区共用同一套渲染——粗体、斜体、行内代码、链接都变成样式。模型原话里的尖括号仍然只是字面文字，不会变成标签。列表、标题、围栏代码块这类块级语法不认（旁白是一句话，用不到），真遇到就原样显示。
+  - **她说话的时间变长了**（2026-09-27 你问的）：以前固定 10 秒，长句子还没念完她就回去干别的了。现在短句 15 秒起步，句子越长留得越久（每分钟约 400 字的默读速度），最多 30 秒封顶——封顶是为了防"某一步她再没说话，画面却一直卡在说话那张"。
+  - **设置接上了 DSH 的标准配置通道**（2026-09-27）：插件现在把设置清单完整声明出来（`Config`），其中"默认模式"和"外部推送"标成**改了不用重载**——改这两样时 DSH 会把新值就地交给正在运行的插件，插件当场按新值办事，不会被重建。其余几样（端口、绑定地址、隧道、口令、历史条数）改完确实得重新监听或重建，就照旧重建插件，不假装能热改。顺带：访问口令和 Telegram 机器人令牌标成敏感值，不会回显在表单里。**更老的 DSH（0.1.5 那一代）上照样装得上、功能照旧**，只是没有"改完立即生效"这一条——这条声明不会让插件在旧版本上起不来。
+  - 子代理（它派出去干活的小分身）的自言自语不会推到你手机上，别的会话的也不会。
+  - **文案更正：不再拿"通知和麦克风"当加密地址的理由**（2026-09-27 你指出的）：Tailscale 加密地址那段原来写着「手机浏览器只在加密连接上才肯给用通知和麦克风」。问题是这两样我们**并没有做**——系统通知的入口从 2026-09-25 起一直藏着（锁屏会冻结后台页面，那条路走不通），麦克风图标也早已移除。拿不存在的能力当卖点，等于把你往一个没有的东西上引。现在只说成立的那一条：**这条连接是加密的**（地址栏上会出现 https 那把锁）。DSH 设置卡片、配对页那两条提示、README 中英两版都改了；相关测试也从"要提到这两样"改成"不许再出现"，并反向验证过它们真的会红。
+  - **声明了对 DSH 的版本要求**（2026-09-27）：DSH 0.1.7 起，装插件前会先拿插件声明的版本去比对运行中的 DSH。我们原来把要求写在 `engines.dsh` 里，而这道检查**只看 `peerDependencies`**——等于它对我们完全不设限。现在两处都写了（`engines.dsh` 保留给插件市场做适配展示）。效果：以后 DSH 大版本变动、我们确实不兼容时，DSH 会在加载我们之前把我们这一行禁用并打一句诊断，**整个 DSH 照常启动**（而不是默默加载失败）；要给某个具体版本开绿灯，有 `dsh plugin allow-version` 这条通道。
+
+## [0.1.3] - 2026-09-25
+
+### 新加的
+
+- **手机上也能用 `/` 指令了。** 在输入框里打一个 `/`，输入框上方就会列出这个会话能用的指令（名字 + 一句说明），继续打字按名字过滤，点一下就执行；需要参数的指令会把它填进输入框、并把「它要什么」挂在提示位置，你补完再发。指令跑出来的结果在聊天里单独一行，和 AI 说的话、你自己说的话都长得不一样。**这份名单是 DSH 自己的账本**，不是插件的——电脑上新装一个带指令的插件，手机上刷新就有了。本机这台电脑当前有 6 条：`compact`、`export`、`feedback`、`goal`、`permission`、`plan`。
+  - 打错的指令、不存在的指令：**拒绝并说明**（和电脑端同一条规则），不会退回去当成一次提问发给模型。`/model`、`/file` 会特别说一句「这是电脑网页端专有的」——它们确实只活在浏览器那半边，宿主账本里没有。
+  - 会话没在跑（睡在硬盘上）时没有指令可列：这时如实说「这个会话现在没在跑，指令要先让它跑起来」，**不显示成一个空名单**（那等于说「一条指令都没有」，是另一回事）。
+  - 指令执行会写进会话记录（`command/run` + `command/done` 两条日志事件），所以点开一个老会话时，之前执行过的指令和结果也在——手机上看到的和电脑上是同一份账。
+  - **指令这一版带不了附件**：DSH 的指令要的附件凭据和手机上传那套不通。输入框里贴着的附件会**原样留着**（不会被悄悄丢掉），跟下一条普通消息一起发出去。
+
+### 修好的
+
+- **指令跑完时手机上可能一直挂着「执行中…」（最多一分钟）。** 起因是手机一分钟会重读一次会话日志，如果读的那一刻指令还在跑，记录里那条就写着「执行中」；而它和内存里那条（已经拿到结果）时间戳相同，按原来的合成规则接不上去，于是内存里那份更准的反而没显示出来。现在指令行按 `commandId` 认人，记录里那条就地把结果换成内存这份的。配了一条反向验证（把修复去掉，那条用例确实变红）。
+
+## [0.1.2] - 2026-09-25
+
+### 新加的
+
+- **手机点开一个会话，就能看到它之前每一轮。** 在这之前，手机上只有「插件亲眼看过」的内容：内存里那份历史从 DSH 启动、或者从手机开始遥控的那一刻才开始记，所以一个早就存在的会话点进去是空的。现在点开会话（以及在手机上刷新页面、切换会话）时，插件会去读那个会话的记录，把每一轮的用户指令和最终结论列出来；单帧模式仍然只显示最后一条结论。读不出来（老格式日志、写了一半的日志）就退回手里那份并记一条日志，**不编内容**。
+  - 重放和实时走的是**同一套判断**：`lib/history.js` 调的就是 `events.js` 里那个提取器（`createTurnTracker`），两条路的「哪条才算回答」不会走散。
+  - 读完就广播一份新快照。手机上看到的顺序是「先有手里那份，再自然补全」，不会空白等待。
+  - 顺手修掉了 `tools/peek-events.mjs` 的两个真 bug：多帧 zstd 日志只解第一帧（26MB 的日志只读出 196 字节，看着像「这个会话没内容」）、文件名写死 `session.v3.jsonl.zstd`（v4 的会话根本找不到）。它现在直接用 `lib/log-tail.js` 的帧扫描和文件查找。
+
+### 修好的
+
+- **开机预热历史撞上「巨型父会话」会把 DSH 本体 OOM 打挂。** 绑定会话如果是**带大量子会话的父会话**（本机实测：310 个子会话、26MB 压缩日志），`sessionQuery.readSession()` 会触发 v3→v4 迁移并把这个父会话的**每个子会话整份解码**，默认约 4GB 堆 20 秒就没了。现在预热前先量规模（`lib/tree.js` 的 `sessionScale`：用已缓存的 `listSessions()` 记录数子会话 + 只 stat 自己的日志体积），超过 `HISTORY_MAX_CHILDREN = 20` 或 `HISTORY_MAX_BYTES = 8MB` 就**不走整份读，改走下面那条有上限的尾部读**（日志里记一条「规模上限：… 改走尾部读」，带上子会话数与日志体积）；`pending` 标记仍是**同步**打上，手机侧「正在读」的语义不变。
+  - 为什么非要挡在调用之前：`readSession` 一旦被调用，代价发生在 DSH 内核里（迁移 → 全解子会话 + 两次全量克隆），事后省不回来。
+  - 实测：绑回那个 310 子会话的父会话，堆峰 521MB（改之前 4364MB → OOM）；`npm test` 458/458。
+
+### 改了的
+
+- **手机端读会话历史有了上限（用户 2026-09-25 的要求：读历史要设上限）。** 三层都是常量、都跟会话总量无关：
+  ① **读取窗口** `lib/log-tail.js`（新）——只解日志**尾部**若干 zstd 帧：`HISTORY_TAIL_WINDOW_BYTES = 16MB`、`HISTORY_TAIL_MAX_EVENTS = 20000`；窗里一个完整帧都没有（最后一帧比窗口大）时会**放大窗口重来**（4×，上限 64MB），不是直接认输。
+  ② **展示条数** `HISTORY_MAX_ENTRIES = 200`——重放成聊天记录后只留尾部这么多。
+  ③ **诚实标注**：`store.snapshot()` 多出 `historyTruncated` / `historyNote`，手机端在聊天内容**最上面**垫一行「这个会话很大，只显示了最近 N 条（读取上限：…）」——条数被砍了却不说，用户会以为这个会话就这么点。
+  - 判定：会话「大」（子会话 > 20 或日志 > 8MB）走有上限的尾部读；「小」仍走内核的完整读（日志权威、会话活着还免读盘）。窗口把整份都盖住时**不谎报**截断。
+  - 实测（本机最坏那条 26MB / 2.2 万事件的父会话）：4MB 窗口→29 条 / 121ms；8MB→87 条 / 203ms；16MB→197 条 / 472ms；32MB（等于整份）→251 条 / 764ms / 堆峰约 540MB。同一份日志走内核 `readSession` 是 4GB 堆 OOM，所以尾部读的代价小两个数量级。
+  - 验收：把绑定会话设成那个巨型父会话，`dsh web` 起来堆峰 477MB（不再 OOM），手机 `/mini/api/state` 拿到 **197 条真实历史 + `historyTruncated: true` + 说明文案**；`npm test` **458/458**（新增 `test/log-tail.test.mjs` 8 条、`test/page.test.mjs` 2 条）。
+
+## [0.1.1] - 2026-09-25
+
+### 新加的
+
+- **手机上能回答 AI 的提问了。** 电脑那边的 AI 问你「选哪个」（比如让你挑一个方案）时，问题会推到手机上，点一下就算答了。一个一个答，答错了能回头改，选项里没有的也能自己打字。手机上要是没人（锁屏、关了页面、断了网），问题会自动还给电脑，那边照常弹窗——不会两头都答不上。
+- **权限档位能在手机上切。** 仅可查看 / 工作区内修改 / 完全权限，不用再回电脑改，档位显示中文名。
+- **每个会话的模型和思考强度能在手机上换。** 顶栏那一行就是当前用的模型，点它就能改。会话没在跑（睡在硬盘上）的时候也读得出它上次用的是什么，不用先跑一轮。
+- **手机上能新建工作区和会话。** 浏览电脑上的目录，挑一个登记成工作区，再在里面开会话。
+- **Tailscale 那条路上多了一个加密地址**（形如 `https://你的电脑名.你的网络名.ts.net/`）。它和原来那条是同一台电脑、同一条通道，区别只在连接加不加密。加密之后浏览器才肯给用系统通知和麦克风——要那两样，前提是「加密连接」。（**2026-09-27 更正**：当时这么写是错的——系统通知和麦克风这两样一直没有真正落地，界面上从来没有过可用的入口，详见本版顶部那条「文案更正」。）
+
+### 修好的
+
+- Tailscale 那条路：找不到命令时会把该装什么说清楚，检查状态不再让用户干等十五秒；加密地址那条的存在和前提也补上了说明。
+- 开启通知的引导：HarmonyOS 上不再让用户去点一个不存在的东西；权限被拒过之后，会告诉用户「清数据」这条路。
+- 「单帧」和「聊天」两种模式里，新回答落下来时的滚动位置都不再停在末尾。
+- 文案：「锁屏也能提醒」改成「页面在后台时提醒」——它做不到锁屏提醒，原来那句话承诺过头了。
+
+### 已知的取舍
+
+- 只有 Tailscale 的加密地址和公网隧道是 `https://`。明文那条路上，浏览器不给用系统通知和麦克风。（**2026-09-27 更正**：这两样如今在界面上都没有，也不需要靠加密连接去换——想要提醒请用电脑端的外部推送，详见顶部那条「文案更正」。）
+- 手机上答的是 AI 主动提给你的选择题。**系统层面的确认弹窗（比如危险命令的审批）手机上点不了**，还得回电脑。
+- 公网隧道的地址每次重启都会换。
+
 ## [0.1.0] - 2026-09-22
 
 第一个版本。
@@ -25,3 +103,7 @@
 - 不做桌面镜像。手机上看不到会话列表、文件树、工具调用详情——这是设计目标，不是还没做。
 
 [0.1.0]: https://github.com/xingzhen199186/dsh-mini-remote/releases/tag/v0.1.0
+[0.1.1]: https://github.com/xingzhen199186/dsh-mini-remote/releases/tag/v0.1.1
+[0.1.2]: https://github.com/xingzhen199186/dsh-mini-remote/releases/tag/v0.1.2
+[0.1.3]: https://github.com/xingzhen199186/dsh-mini-remote/releases/tag/v0.1.3
+[0.1.4]: https://github.com/xingzhen199186/dsh-mini-remote/releases/tag/v0.1.4

package/README.en.md

@@ -0,0 +1,160 @@
+# dsh-mini-remote
+
+> A [DeepSeek Harness](https://github.com/deepseek-ai/DeepSeek-Harness) (DSH) plugin that puts a **minimal remote control** on your mobile device — only the instruction you send, the AI's final conclusion, and the one line it mutters between steps (shown in the whale girl's speech bubble) reach it. Tool calls, file reads and writes, sub-agent dispatch, and the body of the reasoning trace all stay on the computer.
+
+![DSH plugin](https://img.shields.io/badge/DSH_plugin-dsh--plugin-blue)
+![License](https://img.shields.io/badge/license-MIT-green)
+
+[中文说明 →](README.md)
+
+---
+
+## Why I built this plugin
+
+The idea came from this: an agent task often takes a long time to finish, and if you step out, you need the phone to drive it remotely.
+
+But the phone clients that exist show the PC's execution steps in faithful detail. You send one instruction; it may think for several minutes, read dozens of files, call tools a few times, and only then give you a conclusion. If you're out, or busy away from the computer, you simply don't have the time to watch the phone that closely.
+
+I don't think that approach is bad. It's complete and controllable, and if you're going to do serious work, it's the right one.
+
+But when I'm out, what I want is something else — **a lighter way to interact that asks less of my attention**. The phone screen is small, and so is the attention I have to spare when I'm out. Most of the time I only need one thing: **this round is done, time to send the next instruction.** And even at my desk, I rarely read the AI's running commentary while it works.
+
+So the interface here is deliberately crude: it drops the PC's execution steps entirely and puts only the AI's final conclusion in front of you.
+
+**In a sense, it exists so that you look at it less.**
+
+So you can spend your time more freely — instead of being stuck in that small screen while you're playing with your daughter or out on a trip.
+
+---
+
+## Install
+
+```powershell
+dsh plugin --profile web add dsh-mini-remote
+```
+
+Or straight from GitHub, if you would rather pin the source:
+
+```powershell
+dsh plugin --profile web add github:xingzhen199186/dsh-mini-remote
+```
+
+If you already have the source on disk, you can point it at the folder:
+
+```powershell
+dsh plugin --profile web add <the folder you put the source in>
+```
+
+**You must restart DSH once after installing**, or nothing new shows up in the settings page. After the restart a "Phone Remote" entry appears in the left column, and the startup log prints the phone URL and password.
+
+**Which DSH versions it fits.** This plugin was developed on DSH **0.1.5-rc.2** and re-checked item by item on **0.1.7-rc.2** (every interface it uses was unchanged); **versions below 0.1.5 have not been tried**. `rc` is the tag the project puts on preview builds, and DSH as a whole is still a developer preview — minor versions may break things, so versions newer than 0.1.7 are not guaranteed either. If it ever does hit an incompatibility, the usual symptom is one entry point going missing (the model line at the top, say) while everything else keeps working: the plugin is written so that a missing service switches off that one feature rather than the whole thing.
+
+Settings follow the same rule: the settings are declared the standard DSH way, and on the 0.1.5-era library that ability does not exist yet — the plugin **still installs and works exactly as before**, it just loses the "applies immediately" behaviour mentioned below. On the **0.1.7 generation** that ability is fully there.
+
+---
+
+## Configuration: three routes, pick what you need
+
+All three connection methods **exist at the same time**. Pick one, or leave several on.
+
+Open DSH settings (bottom of the sidebar) → "Phone Remote" in the left column. Every route on that page has a QR code and a link, and the small text under each QR code says **when to use that route**. That's all you need to read.
+
+The plugin's own settings (default mode, external notifications, port, password and so on) also have a standard declaration, so writing them in DSH's standard configuration works too. If the same item is set in both places, **the standard configuration wins**. One difference worth knowing: **"default mode" and "external notifications" apply immediately, with no plugin restart**; port, bind address, tunnel, password and history length make the plugin restart and the phone reconnect once — those genuinely need to re-bind or rebuild, and the plugin says so instead of pretending they can be changed live.
+
+### 1. LAN: at home only
+
+When the phone and the computer are on the same Wi-Fi, scan the "LAN" code and you're in. **Nothing extra to install** — the least fuss of the three.
+
+The cost is that it stops working the moment you leave: the phone switches to mobile data and this route is gone.
+
+### 2. Tailscale: works outside, and the address stays fixed
+
+Install [Tailscale](https://tailscale.com) on both the computer and the phone, sign in to the same account, and this route appears on the pairing page by itself. The address is fixed — set it up once and forget it.
+
+The cost is an app on each side. If you don't mind installing it, **this is the steadiest route when you're out**.
+
+You can take this route one step further and get an encrypted address as well (shaped like `https://your-machine.your-tailnet.ts.net/`). It is **the same computer over the same tunnel** as the entry above; the only difference is that the connection is encrypted. It is not a fourth route — the plain `http://` entry keeps working and keeps showing.
+
+What encryption buys is a private connection: the address bar shows the https padlock, and what travels the wire is encrypted. **That does not depend on which route you pick** — the public tunnel in route 3 below also gives you an `https://` address, equally encrypted.
+
+The two encrypted routes have different prerequisites, so it's worth being precise. This one uses a name shaped like `your-machine.your-tailnet.ts.net`, and **that name only resolves inside your Tailscale network**, via MagicDNS on the phone's client. **But some clients don't have that capability** — MeshArc, the third-party client for HarmonyOS, states in its own README that MagicDNS is not enabled and you should use Tailscale IP addresses; on such a phone this encrypted route simply won't work, and it isn't a matter of a setting being switched off. The tunnel route uses a Cloudflare name that resolves for anyone and doesn't care about the phone; its cost is that the address changes on every restart.
+
+There's a switch on the pairing page — just turn it on. The first time, you have to confirm it in Tailscale's admin console: it is a tailnet-wide switch, and the plugin cannot click it for you. So the pairing page puts the exact link Tailscale hands out right in front of you — one click and you're there. If this computer isn't signed in to Tailscale yet, it says so and gives you a sign-in link instead.
+
+### 3. Public access: nothing to install
+
+There's a switch at the bottom of the pairing page. Turn it on and Cloudflare hands you a public URL (shaped like `https://random-words.trycloudflare.com/`). The phone can reach it on any network, **with nothing installed**. It is an **encrypted connection**, just like the encrypted Tailscale route above — if your phone can't resolve your tailnet's name, this is how you still get encryption.
+
+Two costs, worth knowing before you decide:
+
+- **The address changes every time you restart DSH.** When it does, come back and scan the new code.
+- **The first time is slow** — it's downloading a component of about 50 MB, and only that once. While it does, the status line reads "opening…", which is normal, not a hang. Registration occasionally fails; the plugin retries three times on its own.
+
+Once it's on, **wait half a minute before scanning.** Cloudflare needs a moment to publish the address. Scanning too early reports that it can't be opened — that's not breakage, it's just too soon.
+
+---
+
+<img width="1314" height="2186" alt="screenshot_20260922_233535_com huawei hmos brows" src="https://github.com/user-attachments/assets/8befa186-3e20-4c0e-8efc-8ea523f77648" />
+
+
+## What the mobile side does
+
+Open the link and that's the whole interface: one input box, and the latest reply.
+
+**Send instructions.** Type and send; the AI starts working on the computer.
+
+**Wait for the conclusion.** While it runs, the page shows "running…". You can keep sending during that time — instructions queue up. When the task ends, the conclusion appears on the page, and the phone chimes and buzzes.
+
+**She speaks up while she works.** On the computer, the model often mutters a line between steps ("let me look at this file first"). That line is now spoken by the whale girl through her speech bubble — the talking pose is a newly drawn sprite, the rotation pauses for it, and afterwards picks up from where it stopped. It stays **in the bubble** and never bleeds into the answer area below. Only the line it deliberately writes *for a human reader* is spoken; its own working thoughts — often English, often a whole paragraph — never reach the phone at all. Should that one narration line itself be in English, it is shown as-is, untranslated (translating would mean putting words in its mouth).
+
+**Two display modes.** Tap the ⚙ in the top right to switch. "Single frame" (the default) keeps only the newest reply on screen — good for "I just want to see how this one turned out". "Chat" is a back-and-forth bubble list — good for several rounds of follow-up questions. Use it for a while and you'll know which you prefer.
+
+**Open a session and you see what was said in it before.** Switch to a session that has existed for a while and Chat mode lists every earlier round (the instructions you sent, the conclusion of each round); Single frame shows only the last conclusion. **Very large sessions show only the most recent stretch**: reading one of those in full — tens of thousands of events — would drag the DSH process on your computer down, so the plugin reads just the tail and says so at the top ("this is not everything, only the most recent stretch"). That line is not boilerplate; it is the truth.
+
+**Slash commands work from the phone too.** Type a `/` in the input box and the commands available in this session appear above it; keep typing to filter by name, tap one to run it, and commands that take arguments get filled in for you along with a note on what they expect. The list is DSH's own on your computer (whatever plugins are installed), and a command's result gets its own row in the chat, visually distinct from what the AI said. A mistyped or unknown command is refused with an explanation — it is **not** sent as a message. When the session is not running there are no commands to list, and the page says so. **Commands cannot carry attachments** in this version: files you have attached stay put and go out with your next ordinary message.
+
+**Answer questions from the phone.** When the AI asks you to pick something (choose one of several plans, say), the question is pushed to the phone and a tap answers it — **one at a time, revisable if you change your mind, and you can type your own answer** when none of the options fit. If nobody is at the phone (locked, page closed, network gone), the question goes straight back to the computer and the dialog pops up there as usual.
+
+**Three things you can change in passing.** Tap the line at the top to switch the current session's model and reasoning effort; switch the permission preset (View Only / Workspace Write / Full Access); browse the computer's folders to register a new workspace and start a session in it.
+
+**You're reading conclusions, not the process.** There's no tool-call chain and no file diff on the page. The one exception is the line the whale girl says out loud — it goes into her bubble, never into the answer area (see above). **System-level confirmation dialogs cannot be answered from the phone** (approving a dangerous command, for instance) — those still need the computer. What the phone can answer is the multiple-choice question the AI puts to you; the two are not the same thing. It's a remote control: the TV still has to be on for the remote to be any use.
+
+---
+
+## FAQ
+
+**The QR code scans but the page won't open.**
+First check that the phone and the computer are on the same Wi-Fi.
+
+**Scanning the "public" route from outside won't open.**
+Wait half a minute and try again. If it still won't, the pairing page shows the reason directly. The most common one is **a proxy or VPN running on the computer** — the "TUN mode" in tools like Clash cuts the tunnel's connections; the process looks fine while not a single connection has actually been established. Turn it off and try again. Another possibility: that network simply can't reach Cloudflare (it's intermittent in mainland China, and not something you misconfigured). If so, don't burn time on the public route — **switch to the Tailscale route**.
+
+**It says "disconnected".**
+This happens often after the phone has been in the background. The page reconnects by itself; give it a few seconds. If that doesn't work, open settings and tap "Reconnect".
+
+**The reply arrives but there's no sound.**
+Audio only plays after you've touched the page once. Tap it.
+
+**The phone keeps asking for a password.**
+That means the link you opened didn't carry one — for example, you typed the address by hand. Go back to the computer and scan the QR code again.
+
+**I want a password I can remember.**
+Change it in the password section of "Settings → Phone Remote". **At least 12 characters.** A DSH restart is required afterwards, and the phone has to scan a new code.
+
+---
+
+## Security
+
+**The pairing page carries the password — don't screenshot it and send it around.** The password is encoded straight into the QR code so you never have to type it. That's convenient, and the price is that whoever holds that image can get in.
+
+Beyond that: every endpoint requires the password; password comparison is constant-time; five wrong attempts from one source blocks that source for a minute; pairing information is **readable only from the local machine**, so other devices on the same Wi-Fi can't get it; the public tunnel is off by default and you have to turn it on yourself in the settings page; the phone sees no file contents — when you pick a workspace it lists folder names only, and never lists or reads files. **One thing worth stating plainly: the phone can switch the agent's permission preset.** On Full Access, the agent can then modify any file on this computer. That path is open.
+
+---
+
+## Credits
+
+This plugin's design draws on [dsh-pocket](https://www.npmjs.com/package/dsh-pocket) by shaobeichen — in particular the shape of the configuration page, where each connection route gets its own link, its own QR code, and its own password.
+
+## License
+
+MIT

package/README.md

@@ -1,138 +1,160 @@
 # dsh-mini-remote
 
-> A [DeepSeek Harness](https://github.com/deepseek-ai/DeepSeek-Harness) (DSH) plugin that puts a **minimal remote control** on your phone — only the instruction you send and the AI's final conclusion reach it. Tool calls, file reads and writes, sub-agent dispatch, and reasoning traces all stay on the computer.
+> 一个 [DeepSeek Harness](https://github.com/deepseek-ai/DeepSeek-Harness)（DSH）插件，把一部手机变成**极简遥控器**——移动端只收到你发出去的指令、AI 最后的结论，以及执行中它自言自语的那一句（只进鲸鱼娘的气泡）；工具调用、文件读写、子 Agent 调度、思考过程的正文全部留在电脑上。
 
 ![DSH plugin](https://img.shields.io/badge/DSH_plugin-dsh--plugin-blue)
 ![License](https://img.shields.io/badge/license-MIT-green)
 
-[中文说明 →](README.zh.md)
-
-**To use this plugin from your phone, switch the DSH session page on your PC to Full Access（完全权限）** — approvals cannot be granted from the phone, so a session waiting on one will simply stall.
+[English →](README.en.md)
 
 ---
 
-## Why this exists
+## 为什么做这个插件
 
-I built this because an agent task often takes a long time to finish. If you step out, you need the phone to drive it remotely.
+初衷是因为现在AGENT任务执行一轮往往需要很久，而如果出门，则需要手机端来远程操作。
 
-But the phone clients that exist show the PC's execution steps in faithful detail. You send one instruction; it may think for several minutes, read dozens of files, call tools a few times, and only then give you a conclusion.
+但现有的手机端，会把PC的执行步骤非常还原地展现出来。你发一条指令，它可能要想上几分钟、读几十个文件、调好几次工具，最后才给你一个结论。如果出门或有事不在电脑前，实在没时间盯着手机看那么细致。
 
-I don't think that approach is bad. It's complete and controllable, and if you're going to do serious work, it's the right one.
+我并不认为那种方式不好。信息完整、过程可控，如果你要认真处理任务，它是对的。
 
-But when I'm out, what I want is something else — **a lighter way to interact that asks less of my attention**. The phone screen is small, and so is the attention I have to spare when I'm out. Most of the time I only need one thing: **this round is done, time to send the next instruction.** And even at my desk, I rarely read the AI's running commentary while it works.
+但出门在外的时候，就我个人而言，我需要的是另一种东西——**更轻便、更少占用注意力的交互方式**。手机屏幕就那么大，出门时的精力也就那么多。而大部分时候我真正需要的只有一件事：**这一轮跑完了，该发下一条指令了**。而且大部分时间，即使在电脑上，我也很少会去仔细阅读AI做执行过程中的“自言自语”。
 
-So the interface here is deliberately crude: it drops the PC's execution steps entirely and puts only the AI's final conclusion in front of you.
+所以这个插件的界面做得相当「原始」：它完全省略了电脑网页端的执行步骤，只把 AI 最后的结论送到你面前。
 
-**In a sense, it exists so that you look at it less.**
+**某种意义上，它的存在，是为了让你更少地去看它。**
 
-So you can spend your time more freely — instead of being stuck in that small screen while you're playing with your daughter or out on a trip.
+你可以更加自由地支配自己的时间，而不是当你和女儿玩耍时，抑或出游时，被困在那个小小的屏幕里。
 
 ---
 
-## Install
+## 安装
 
 ```powershell
-dsh plugin --profile web add github:xingzhen199186/dsh-mini-remote
+dsh plugin --profile web add dsh-mini-remote
 ```
 
-Once the package is on npm, the package name alone works too:
+也可以直接从 GitHub 装，这样锁的是源码：
 
 ```powershell
-dsh plugin --profile web add dsh-mini-remote
+dsh plugin --profile web add github:xingzhen199186/dsh-mini-remote
 ```
 
-If you already have the source on disk, you can point it at the folder:
+手上有源码目录的话，把目录指给它也一样：
 
 ```powershell
-dsh plugin --profile web add <the folder you put the source in>
+dsh plugin --profile web add <你放源码的目录>
 ```
 
-**You must restart DSH once after installing**, or nothing new shows up in the settings page. After the restart a "Phone Remote" entry appears in the left column, and the startup log prints the phone URL and password.
+装完**必须重启一次 DSH**，设置页里才会出现新东西。重启后左栏会多出「手机遥控」，启动日志里也会打印手机访问地址和密码。
+
+**它适配哪些 DSH 版本。** 这个插件在 DSH **0.1.5-rc.2** 上开发，在 **0.1.7-rc.2** 上重新逐项核对过（插件用到的那些接口，一个都没变），**低于 0.1.5 的版本没试过**。`rc` 是官方给预览版编的号，DSH 目前整体还是开发者预览版，跨小版本可能有破坏性改动，所以比 0.1.7 更新的版本同样不保证。真遇上不兼容，症状一般是某一块入口不见了（比如顶栏那行模型），其余部分照常——插件是按「少了哪个服务就关掉哪块功能」写的，不会整个起不来。
+
+设置也是这样处理的：设置清单按 DSH 的标准方式声明，而在 0.1.5 那一代的库还没有相应能力，插件**照样装得上、功能照旧**，只是少了下面提到的「改完立即生效」。**0.1.7 这一代**上这条能力是齐的。
 
 ---
 
-## Configuration: three routes, pick what you need
+## 配置：三条路，按需要选
+
+三条连接方式**同时存在**，选一条就行，也可以都开着。
+
+打开 DSH 设置（侧边栏最下面）→ 左栏「手机遥控」。这一页上每条路都有一个二维码和一条链接，二维码底下那行小字写着**什么时候用这条**，看它就够了。
 
-All three connection methods **exist at the same time**. Pick one, or leave several on.
+插件的设置（默认模式、外部推送、端口、口令这些）也有一份标准声明，写在 DSH 的标准配置里同样认得。两处都写了同一项时，**以标准配置为准**。另有一条区别：**「默认模式」和「外部推送」改完立即生效、插件不重启**；端口、绑定地址、隧道、口令、历史条数这几样改完会让你重连一次——它们本来就得重新监听或重建，插件如实声明，不假装能热改。
 
-Open DSH settings (bottom of the sidebar) → "Phone Remote" in the left column. Every route on that page has a QR code and a link, and the small text under each QR code says **when to use that route**. That's all you need to read.
+### 一、内网：只在家里用
 
-### 1. LAN: at home only
+手机和电脑连同一个 Wi-Fi 时，扫「内网」那个码就能用。**不需要任何额外安装**，最省事的一条。
 
-When the phone and the computer are on the same Wi-Fi, scan the "LAN" code and you're in. **Nothing extra to install** — the least fuss of the three.
+代价是出了门就连不上——手机一切到流量，这条就断了。
 
-The cost is that it stops working the moment you leave: the phone switches to mobile data and this route is gone.
+### 二、Tailscale：出门也能连，地址还固定
 
-### 2. Tailscale: works outside, and the address stays fixed
+电脑和手机都装上 [Tailscale](https://tailscale.com)、登录同一个账号，配对页上就会自动多出这一条。地址固定，配一次以后不用再管。
 
-Install [Tailscale](https://tailscale.com) on both the computer and the phone, sign in to the same account, and this route appears on the pairing page by itself. The address is fixed — set it up once and forget it.
+代价是两边都要装一个 App。如果你不介意装，**出门在外这条最稳**。
 
-The cost is an app on each side. If you don't mind installing it, **this is the steadiest route when you're out**.
+这条路上还能再开一步，多拿一个加密地址（形如 `https://你的电脑名.你的网络名.ts.net/`）。它和上面那条是**同一台电脑、同一条通道**，区别只在连接加不加密——不是第四条路，那条明文的照旧能用、也照旧显示。
 
-### 3. Public access: nothing to install
+加密的好处是这条连接本身是密的：地址栏上会出现 https 那把锁，路上传的东西是加密的。**这一点不挑路**——下面第三条的公网隧道给的也是 `https://` 地址，一样加密。
 
-There's a switch at the bottom of the pairing page. Turn it on and Cloudflare hands you a public URL. The phone can reach it on any network, **with nothing installed**.
+两条加密路各有各的前提，说清楚免得你走错：这一条用的是形如 `你的电脑名.你的网络名.ts.net` 的域名，**它只在你的 Tailscale 网络内部解析得出**，靠的是手机客户端上的 MagicDNS。**但有些客户端没有这个能力**——HarmonyOS 上那个第三方客户端 MeshArc，它自己的说明里就写着「请用 Tailscale IP 地址」，那类手机上这条加密路走不通，不是设置没开的问题。隧道那条用的是 Cloudflare 的域名，谁都能解析，不挑手机，代价是地址每次重启都会换。
 
-Two costs, worth knowing before you decide:
+配对页上有一个开关，打开就行。第一次开需要你在 Tailscale 的后台确认一次——那是整个网络级别的开关，插件代不了你点，所以配对页会把 Tailscale 给出的那条链接直接摆在你面前，点一下就过去。要是这台电脑还没登录 Tailscale，它会说清楚，并给你登录链接。
 
-- **The address changes every time you restart DSH.** When it does, come back and scan the new code.
-- **The first time is slow** — it's downloading a component of about 50 MB, and only that once. While it does, the status line reads "opening…", which is normal, not a hang. Registration occasionally fails; the plugin retries three times on its own.
+### 三、公网访问：什么都不用装
 
-Once it's on, **wait half a minute before scanning.** Cloudflare needs a moment to publish the address. Scanning too early reports that it can't be opened — that's not breakage, it's just too soon.
+配对页最底下有个开关，打开它，Cloudflare 会给你一个公网网址（形如 `https://随机词.trycloudflare.com/`）。手机在任何网络下都能连，**不用装任何东西**。它和上面那条加密路一样是**加密连接**——手机上的 Tailscale 解析不了你那个网络的域名的话，想要加密就走这条。
+
+两个代价，先知道再决定：
+
+- **地址每次重启 DSH 都会换**，换了得回来重新扫一次码。
+- **第一次打开会慢**——它在下载一个五十兆左右的组件，只下这一次。这期间状态那行会显示「正在打开…」，那是正常的，不是卡死。注册偶尔会失败，插件会自动重试 3 次。
+
+打开之后**等半分钟再扫**。Cloudflare 需要一点时间把这个地址公布出去，太早扫会提示打不开——那不是坏了，是还没到时候。
 
 ---
 
 <img width="1314" height="2186" alt="screenshot_20260922_233535_com huawei hmos brows" src="https://github.com/user-attachments/assets/8befa186-3e20-4c0e-8efc-8ea523f77648" />
 
 
-## What the phone side does
+## 移动端能做什么
+
+打开链接就是全部界面：一个输入框，和最新的一条回复。
+
+**发指令。** 打字发出去，AI 就在电脑上开始干活。
+
+**等结论。** 跑的时候上面显示「运行中…」。这期间你可以接着发，指令会排队。任务结束，结论直接出现在页面上，同时响一声、震一下。
+
+**她干活的时候会开口。** 电脑上的模型在步骤之间常会自言自语一句（「我先看一下这个文件」这类），这一句现在由鲸鱼娘念出来——说话的动作是新画的一张立绘，轮播会为它停一下，说完接着从停下的地方往下走。它**只在那只气泡里**，不会混进下面的回答区。气泡里只念**它特意写给人看的那一句**；它自己心里想的那些（常是英文、也常成段）一个字都不上手机。万一那句旁白本身就是英文，就照原样显示、不翻译——翻译等于替它编一句它没说过的话。
+
+**两种显示模式。** 点右上角的 ⚙ 切换。「单帧」（默认）整屏只留最新一条回复，适合「我就想看这次的结果」；「聊天」是一来一回的气泡列表，适合连着追问好几轮。用一阵子你会知道自己偏哪个。
 
-Open the link and that's the whole interface: one input box, and the latest reply.
+**点开一个会话，能看到它之前聊过什么。** 在左边切到一个早就存在的会话，聊天模式会把之前的每一轮都列出来（你发过的指令、每一轮的结论），单帧模式只显示最后一条结论。**特别大的会话只给最近一段**：那种几万个事件的会话，整份读下来会把电脑上的 DSH 拖垮，所以只读末尾那一小段，并在最上面写明「这不是全部，只显示了最近一段」——你看到的那句话不是客套话，是实情。
 
-**Send instructions.** Type and send; the AI starts working on the computer.
+**斜杠指令也能在手机上用。** 在输入框里打一个 `/`，上面就会列出这个会话能用的指令，接着打字按名字过滤，点一下就执行；要参数的会帮你填好、并告诉你它要什么。名单是电脑上 DSH 自己的那份（装了什么插件就有什么），执行结果在聊天里单独占一行，和 AI 说的话区分得开。打错的、不存在的指令会被明确拒绝并说明原因，**不会当成一句话发出去**。会话没在跑的时候没有指令可列，页面会直说。**指令这一版带不了附件**：你贴着的文件会留着，跟下一条普通消息一起发。
 
-**Wait for the conclusion.** While it runs, the page shows "running…". You can keep sending during that time — instructions queue up. When the task ends, the conclusion appears on the page, and the phone chimes and buzzes.
+**在手机上答题。** AI 问你「选哪个」（比如让你挑一个方案）时，问题会推到手机上，点一下就算答了——**一个一个答，答错了能回头改，选项里没有的也能自己打字**。手机不在跟前（锁屏、关了页面、断了网）就自动把问题还给电脑，那边照常弹窗。
 
-**Two display modes.** Tap the ⚙ in the top right to switch. "Single frame" (the default) keeps only the newest reply on screen — good for "I just want to see how this one turned out". "Chat" is a back-and-forth bubble list — good for several rounds of follow-up questions. Use it for a while and you'll know which you prefer.
+**顺手能改的三样。** 点顶栏那一行，换当前会话的模型和思考强度；切权限档位（仅可查看 / 工作区内修改 / 完全权限）；浏览电脑上的目录，登记新的工作区和会话。
 
-**You're reading conclusions, not the process.** There's no tool-call chain, no file diff, no approval dialog on the page — **anything that needs your confirmation cannot be confirmed from the phone**; you have to go back to the computer. Nor will it start new sessions, switch models, or change configuration for you. It's a remote control: the TV still has to be on for the remote to be any use.
+**看的是结论，不是过程。** 页面上没有工具调用链、没有文件 diff。唯一的例外是鲸鱼娘嘴里那一句自言自语——它只进气泡，不进回答区（见上面那一段）。**系统层面的确认弹窗手机上点不了**（比如危险命令的审批），那类还得回电脑处理——手机上能答的是 AI 主动提给你的选择题，这两件事不一样。它的定位是一根遥控器：电视还得在那儿开着，遥控器才有用。
 
 ---
 
-## FAQ
+## 常见问题
 
-**The QR code scans but the page won't open.**
-First check that the phone and the computer are on the same Wi-Fi.
+**扫码之后打不开。**
+先看手机和电脑是不是同一个 Wi-Fi。
 
-**Scanning the "public" route from outside won't open.**
-Wait half a minute and try again. If it still won't, the pairing page shows the reason directly. The most common one is **a proxy or VPN running on the computer** — the "TUN mode" in tools like Clash cuts the tunnel's connections; the process looks fine while not a single connection has actually been established. Turn it off and try again. Another possibility: that network simply can't reach Cloudflare (it's intermittent in mainland China, and not something you misconfigured). If so, don't burn time on the public route — **switch to the Tailscale route**.
+**出门扫「公网」那条打不开。**
+等半分钟再试。还不行的话，配对页上会直接显示原因。最常见的一种是**电脑上开着代理或 VPN**——Clash 这类软件的「TUN 模式」会把隧道的连接掐断，进程看着好好的，其实一条连接都没建立起来，先把它关掉再试。还有一种：这条网络就是走不通 Cloudflare（国内时好时坏，不是你哪里配错了），那就别在公网上耗着，**改用 Tailscale 那条**。
 
-**It says "disconnected".**
-This happens often after the phone has been in the background. The page reconnects by itself; give it a few seconds. If that doesn't work, open settings and tap "Reconnect".
+**显示「未连接」。**
+手机切后台再回来经常会这样，页面会自己重连，等几秒；还不行就进设置点「重连」。
 
-**The reply arrives but there's no sound.**
-Audio only plays after you've touched the page once. Tap it.
+**回复到了，但没声音。**
+声音要你先碰过页面才会响，点一下就行。
 
-**The phone keeps asking for a password.**
-That means the link you opened didn't carry one — for example, you typed the address by hand. Go back to the computer and scan the QR code again.
+**手机上一直让我输密码。**
+说明你打开的链接里没带密码（比如自己手打的地址）。回电脑上重新扫一次二维码就好。
 
-**I want a password I can remember.**
-Change it in the password section of "Settings → Phone Remote". **At least 12 characters.** A DSH restart is required afterwards, and the phone has to scan a new code.
+**想换一个自己记得住的密码。**
+在「设置 → 手机遥控」的密码那一块直接改，**至少 12 位**。改完要重启一次 DSH，重启之后手机上要重新扫一次码。
 
 ---
 
-## Security
+## 安全
 
-**The pairing page carries the password — don't screenshot it and send it around.** The password is encoded straight into the QR code so you never have to type it. That's convenient, and the price is that whoever holds that image can get in.
+**配对页上带着密码，别截图发出去。** 密码直接编在二维码里，扫完不用手敲——方便是方便，代价是谁拿到这张图谁就能进。
 
-Beyond that: every endpoint requires the password; password comparison is constant-time; five wrong attempts from one source blocks that source for a minute; pairing information is **readable only from the local machine**, so other devices on the same Wi-Fi can't get it; the public tunnel is off by default and you have to turn it on yourself in the settings page; and the phone has no access to your filesystem.
+除此之外：所有接口都要密码，密码比对用定长比较；同一来源一分钟错 5 次就挡一分钟；配对信息**只允许本机读取**，同一个 Wi-Fi 下的其他设备拿不到；公网隧道默认关着，要你自己在设置页里打开；手机看不到任何文件内容——挑工作区的时候只列文件夹名字，文件一个都不列、也不读。**但有一件事要说清楚：手机上能切换 Agent 的权限档位。**切到「完全权限」，Agent 就能改这台电脑上的任何文件。这条路径是开着的。
 
 ---
 
-## Credits
+## 致谢
 
-This plugin's design draws on [dsh-pocket](https://www.npmjs.com/package/dsh-pocket) by shaobeichen — in particular the shape of the configuration page, where each connection route gets its own link, its own QR code, and its own password.
+这个插件在设计思路上参考过 [dsh-pocket](https://www.npmjs.com/package/dsh-pocket)（作者 shaobeichen）——尤其是「每条连接路径各配一条链接、一个二维码、一个密码」这种配置形态。
 
-## License
+## 许可
 
 MIT