pi-sdk-web 0.4.3 → 0.4.5

package/dist/server.js

@@ -411,6 +411,11 @@ export class PiWebServer {
             case "abort":
                 await this.session.abort();
                 break;
+            case "abort_bash":
+                // Kill only the running bash (TUI Ctrl+C equivalent), leaving any
+                // agent activity untouched.
+                this.session.abortBash();
+                break;
             case "get_stats":
                 this.broadcastStats();
                 break;

package/dist/static/app.js

@@ -1331,6 +1331,30 @@ class PiWebClient {
     if (!div) {
       div = this.createToolBlock('bash', { command: this.pendingBashCommand || '' }, key);
       div.className = 'tool-block pending';
+      // Stop button in the title row (TUI Ctrl+C equivalent): abort_bash
+      // kills only this running bash. Removed when the block finalizes.
+      const stopBtn = document.createElement('button');
+      stopBtn.className = 'bash-stop-btn';
+      stopBtn.textContent = '⏹ stop';
+      stopBtn.title = 'Stop this bash command (Ctrl+C in TUI)';
+      stopBtn.addEventListener('click', (e) => {
+        e.stopPropagation(); // don't toggle expand
+        this.send({ type: 'abort_bash' });
+        stopBtn.disabled = true;
+        stopBtn.textContent = 'stopping...';
+      });
+      div.querySelector('.tool-title')?.appendChild(stopBtn);
+      // The running bash block lives in the #bash-pending area (between the
+      // message flow and the input box) so later messages don't push it
+      // out of view - same as TUI's pendingMessagesContainer. bash_result
+      // moves it into the normal message flow when done.
+      const bashPending = document.getElementById('bash-pending');
+      if (bashPending) {
+        bashPending.appendChild(div);
+        bashPending.style.display = 'block';
+      } else {
+        this.contentEl.appendChild(div);
+      }
       this.bashEls.set(key, div);
     }
     // Append the delta to the full text and re-apply the preview (respects
@@ -1355,6 +1379,18 @@ class PiWebClient {
     if (!(div.dataset.fullOutput && div.dataset.fullOutput.length > 0)) {
       this.setToolOutput(div, output);
     }
+    // Move the finished block from the bash-pending (fixed) area into the
+    // normal message flow, keeping its accumulated output.
+    const bashPending = document.getElementById('bash-pending');
+    if (bashPending && bashPending.contains(div)) {
+      this.contentEl.appendChild(div);
+      if (bashPending.children.length === 0) {
+        bashPending.style.display = 'none';
+      }
+      this.scrollToBottom();
+    }
+    // Bash done: the stop button is no longer relevant.
+    div.querySelector('.bash-stop-btn')?.remove();
 
     const isError = result.exitCode !== undefined && result.exitCode !== 0;
     div.className = isError ? 'tool-block error' : 'tool-block success';

package/dist/static/index.html

@@ -31,6 +31,7 @@
       </div>
     </div>
     <div id="pending"></div>
+    <div id="bash-pending" style="display:none"></div>
     <div id="widgets"></div>
     <div id="status"></div>
     <div id="footer">

package/dist/static/style.css

@@ -544,6 +544,40 @@ body {
   font-size: 12px;
 }
 
+/* Running !/!! bash output (streaming) - fixed area between messages and
+   input, so later messages don't push it out of view (TUI analog:
+   pendingMessagesContainer). Moved into the message flow on completion. */
+#bash-pending {
+  display: none;
+  padding: 4px 12px;
+  border-top: 1px solid var(--border);
+  font-size: 13px;
+  /* ~10 lines of output visible; scrolling inside the block for more */
+  max-height: calc(10 * 1.5em);
+  overflow-y: auto;
+}
+
+.bash-stop-btn {
+  margin-left: 8px;
+  padding: 1px 8px;
+  font-size: 11px;
+  color: var(--error);
+  border: 1px solid var(--error);
+  border-radius: 4px;
+  background: transparent;
+  cursor: pointer;
+  vertical-align: middle;
+}
+
+.bash-stop-btn:hover {
+  background: color-mix(in srgb, var(--error) 15%, transparent);
+}
+
+.bash-stop-btn:disabled {
+  opacity: 0.6;
+  cursor: default;
+}
+
 .widget-block {
   margin: 2px 0;
 }

package/dist/ui-context.js

@@ -68,6 +68,30 @@ export class WebUIContext {
     statusMap = new Map();
     constructor(sink) {
         this.sink = sink;
+        // Pi's ExtensionRunner wraps the ui context with `{...ui}` (a shallow
+        // spread) when building the extension ctx - class prototype members
+        // (methods AND the theme getter) would be LOST by that spread (only own
+        // enumerable properties survive). Copy prototype methods onto the
+        // instance as own bound properties, and expose theme as an own
+        // property, so extensions see the same shape as TUI's object-literal
+        // UIContext (all methods + theme as own props).
+        const proto = Object.getPrototypeOf(this);
+        for (const name of Object.getOwnPropertyNames(proto)) {
+            if (name === "constructor")
+                continue;
+            const desc = Object.getOwnPropertyDescriptor(proto, name);
+            if (desc && typeof desc.value === "function") {
+                this[name] = desc.value.bind(this);
+            }
+        }
+        // Theme: the prototype getter is not picked up by `{...}` and the own
+        // property cannot shadow a getter-only prototype via assignment. Define
+        // an own enumerable getter returning webTheme (fresh after setWebTheme).
+        Object.defineProperty(this, "theme", {
+            configurable: true,
+            enumerable: true,
+            get: () => this.webTheme,
+        });
     }
     /** Current extension status snapshot (key -> text) for new connections. */
     getStatusSnapshot() {

package/package.json

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