pi-sdk-web 0.5.13 → 0.5.14

package/dist/server.js

@@ -882,22 +882,37 @@ export class PiWebServer {
             }
         };
         const unsubscribe = this.session.subscribe(listener);
-        // hasUI by extension: most extensions degrade gracefully to notify()
-        // (our notify -> browser dialog/toast), but a few (magic-context) use
-        // ctx.ui.custom() - an extension-drawn TUI panel we can't render. For
-        // those, hasUI:false routes them to their own text fallback
-        // (appendEntry -> modal), same as before.
+        // hasUI per extension: extensions whose command handler draws a TUI
+        // panel via ctx.ui.custom() when hasUI=true need hasUI:false so they
+        // use their text fallback instead (pi-web can't render custom()).
+        // magic-context /ctx-status -> appendEntry (custom entry -> modal);
+        // aft-pi /aft-status (its only command) -> ui.notify(text).
+        // Everything else gets hasUI:true so notify-based output works.
         const cmdPath = (cmd.sourceInfo && cmd.sourceInfo.path) || "";
-        const customOnly = /pi-magic-context|magic-context/.test(cmdPath);
+        const customOnly = /pi-magic-context|magic-context|aft-pi/.test(cmdPath);
+        // While a command runs, tag extension notify() broadcasts with the
+        // command name as title so the browser renders them as a titled,
+        // Markdown modal (e.g. /ctx-status, /aft-status) - the command's status
+        // report is a dialog, not a transient stream line. Restores the design
+        // in 68b56f1 (recorded in pi-web-design.md §14.9); 41112f5 had dropped
+        // the wrapping, so command notifies fell back to persistent status
+        // lines while custom-entry commands (/ctx-status) kept the modal.
+        const ui = this.uiContext;
+        const originalSink = ui.sink;
         try {
-            // No sink wrapping: notify() broadcasts go through as-is (no title),
-            // so the frontend renders them as persistent status lines - the same
-            // as TUI's notify -> showStatus (a dim line appended to the chat),
-            // whether or not they come from a command. Command *results* (custom
-            // entries) still become titled modals via the captured entries below.
+            ui.sink = (obj) => {
+                const req = obj;
+                if (req && req.method === "notify") {
+                    originalSink({ ...obj, title: `/${name}` });
+                }
+                else {
+                    originalSink(obj);
+                }
+            };
             await cmd.handler(args, this.buildCommandContext(customOnly ? false : true));
         }
         finally {
+            ui.sink = originalSink;
             unsubscribe();
         }
         // Show command output as a modal (TUI-like). The session entry remains

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-sdk-web",
-  "version": "0.5.13",
+  "version": "0.5.14",
   "description": "Browser Web access for Pi (AI coding agent) via the Pi SDK - standalone module, zero modification to Pi itself",
   "type": "module",
   "bin": {