@esso0428/pi-subagents 0.17.22 → 0.17.23

package/CHANGELOG.md

@@ -7,6 +7,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.17.23] - 2026-10-02
+
+### Fixed
+- **Stopped the agents roster from stealing keys from open modals**: the widget's focus detection used `focused instanceof Editor`, which is always false when the extension resolves its own copy of `@earendil-works/pi-tui` at a different version than pi's host (for example a hoisted peer pinned to an older release). The check silently degraded to "focused is null", so the widget's global `onTerminalInput` listener claimed the keyboard during teardown and transient render states and consumed `↑`/`↓`/`enter`/`escape` from modals such as the `/agents` menus. Focus detection now identifies the prompt editor structurally and fails closed, so the listener only claims input while the editor provably owns it.
+
 ## [0.17.22] - 2026-10-01
 
 ### Changed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@esso0428/pi-subagents",
-  "version": "0.17.22",
+  "version": "0.17.23",
   "description": "A pi extension that brings smart Claude Code-style autonomous sub-agents to pi, with npm:pi-subagents-style JSON agent overrides.",
   "author": "ESSO0428",
   "repository": {

package/src/ui/agent-widget.ts

@@ -5,7 +5,7 @@
  * Uses the callback form of setWidget for themed rendering.
  */
 
-import { Editor, isKeyRelease, Key, matchesKey, truncateToWidth, visibleWidth } from "@earendil-works/pi-tui";
+import { isKeyRelease, Key, matchesKey, truncateToWidth, visibleWidth } from "@earendil-works/pi-tui";
 import type { AgentManager } from "../agent-manager.js";
 import { getConfig } from "../agent-types.js";
 import type { AgentInvocation, AgentRecord, SubagentType, WidgetMode } from "../types.js";
@@ -238,6 +238,24 @@ export function describeActivity(activeTools: Map<string, string>, responseText?
   return "thinking…";
 }
 
+/**
+ * Structural check for pi's prompt editor.
+ *
+ * `instanceof Editor` is unusable here: an extension can resolve its own copy
+ * of `@earendil-works/pi-tui` at a different version than the host's, and the
+ * two `Editor` class objects are then unrelated identities, so the check is
+ * always false. Modals opened with `ctx.ui.custom()` — including the `/agents`
+ * menus — focus a plain `{ render, invalidate, handleInput }` object instead,
+ * so the editor's text-buffer methods identify it across pi-tui copies.
+ */
+function isPromptEditor(component: unknown): boolean {
+  if (typeof component !== "object" || component === null) return false;
+  const candidate = component as { getText?: unknown; setText?: unknown; submitValue?: unknown };
+  return typeof candidate.getText === "function"
+    && typeof candidate.setText === "function"
+    && typeof candidate.submitValue === "function";
+}
+
 // ---- Widget manager ----
 
 export class AgentWidget {
@@ -373,10 +391,17 @@ export class AgentWidget {
     return [...running, ...queued, ...finished];
   }
 
-  /** True when pi's prompt editor owns the keyboard. */
+  /**
+   * True when pi's prompt editor owns the keyboard.
+   *
+   * Deliberately fails closed: an unknown or absent focus target means the
+   * widget does not own the keyboard, so its global terminal listener stays out
+   * of the way. The previous `focused == null` fallback claimed input during
+   * teardown and transient render states, which let roster navigation swallow
+   * ↑/↓/enter/escape from an open modal.
+   */
   private editorHasFocus(): boolean {
-    const focused = (this.tui as { focusedComponent?: unknown } | undefined)?.focusedComponent;
-    return focused == null || focused instanceof Editor;
+    return isPromptEditor((this.tui as { focusedComponent?: unknown } | undefined)?.focusedComponent);
   }
 
   private selectedIndexOf(records: readonly AgentRecord[]): number {