pi-web-ui 0.10.0 → 0.10.2

package/README.md

@@ -72,6 +72,37 @@ npm i -g .
 > install scripts, approve node-pty's native build once after installing:
 > `npm approve-scripts node-pty@1.1.0` (standard npm does this automatically).
 
+### As a pi package (web UI inside pi)
+
+`pi-web-ui` is also published as a **pi package** (`pi-package` on npm) so it
+can be installed and used from within a pi session:
+
+```bash
+pi install npm:pi-web-ui
+```
+
+Once installed, a `/webui` command becomes available inside pi, launching the
+local web UI against your current working directory:
+
+```
+/webui                      # start + open browser (current dir)
+/webui --port 9000          # start on a specific port
+/webui --no-browser         # start without opening the browser
+/webui stop                 # stop the running instance
+/webui status               # show URL / status
+```
+
+> **Note — `pi install` is NOT a global CLI install.**
+>
+> `pi install npm:pi-web-ui` only loads the package into pi's extension tree
+> (`~/.pi/agent/npm/node_modules/`) and registers its extension for pi sessions.
+> It does **not** put a `pi-web-ui` executable on your shell `PATH`, so you
+> cannot run the `pi-web-ui` terminal command from that install. For the CLI you
+> still need the global npm install above (`npm i -g pi-web-ui`), which is what
+> `which pi-web-ui` resolves to. `pi install` ≠ `npm i -g`: one is for pi
+> extensions, the other for a system-wide command. Both can coexist (the global
+> 0.x CLI for terminal use, the pi package for the `/webui` in-pi entry).
+
 ### Start
 
 ```bash

package/dist/server/agent-service.js

@@ -777,6 +777,7 @@ export class ClientSession {
             lastActiveAt: Date.now(),
             msgIds: new Map(),
             nextMsgId: 1,
+            userSeqByTs: new Map(),
             uiMessageCache: new Map(),
             lastMessagesSig: "",
             lastMessagesArray: [],
@@ -910,7 +911,18 @@ export class ClientSession {
         const cached = conv.uiMessageCache.get(cacheKey);
         if (cached)
             return cached;
-        const msg = serializeMessage(m, n);
+        // User-message id suffix is a 1-based count of user messages sharing
+        // this timestamp (that's what resolveUserMessageEntryId() expects). n is
+        // a global per-conversation counter across ALL roles, so it can't be
+        // reused as the seq — otherwise editing anything but the first question
+        // fails to resolve ("找不到要编辑的消息").
+        let seq = n;
+        if (m.role === "user") {
+            const ts = m.timestamp ?? 0;
+            seq = (conv.userSeqByTs.get(ts) ?? 0) + 1;
+            conv.userSeqByTs.set(ts, seq);
+        }
+        const msg = serializeMessage(m, seq);
         if (msg)
             conv.uiMessageCache.set(cacheKey, msg);
         return msg;
@@ -2110,7 +2122,10 @@ export class ClientSession {
         const ts = Number(m[1]);
         const seq = m[2] ? Number(m[2]) : 1;
         let count = 0;
-        for (const entry of this.session.sessionManager.getEntries()) {
+        // Resolve against the compaction-aware current leaf path — the same list
+        // the UI renders (state.messages). Scanning the whole file (getEntries)
+        // could match a summarized entry or one on a different branch.
+        for (const entry of this.session.sessionManager.buildContextEntries()) {
             if (entry.type !== "message")
                 continue;
             const msg = entry.message;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-web-ui",
-  "version": "0.10.0",
+  "version": "0.10.2",
   "description": "Web chat interface for the pi coding agent, powered by the pi SDK (@earendil-works/pi-coding-agent) — one-command run, Docker/systemd/launchd deployable",
   "license": "MIT",
   "type": "module",