@herbertgao/pi-extensions 2026.8.4 → 2026.8.5

package/node_modules/@herbertgao/pi-subagents/src/ui/schedule-menu.ts

@@ -11,6 +11,7 @@
 import type { ExtensionCommandContext } from "@earendil-works/pi-coding-agent"
 import type { SubagentScheduler } from "../schedule.js"
 import type { ScheduledSubagent } from "../types.js"
+import { selectItem } from "./select-item.js"
 
 /** Format an ISO timestamp as relative time ("in 4h", "2d ago", "—"). */
 function relTime(iso: string | undefined, now = Date.now()): string {
@@ -88,16 +89,16 @@ export async function showSchedulesMenu(
     return
   }
 
-  const labels = jobs.map((j) => formatJob(j, scheduler))
-  const choice = await ctx.ui.select(
+  // Numbered + item-paired: two jobs whose names agree in the first 18
+  // characters format identically, and matching the returned string back
+  // against a parallel label array cancelled whichever came first.
+  const job = await selectItem(
+    ctx.ui,
     `Scheduled jobs (${jobs.length}) — select to cancel`,
-    labels,
+    jobs,
+    (j) => formatJob(j, scheduler),
   )
-  if (!choice) return
-
-  const idx = labels.indexOf(choice)
-  if (idx < 0) return
-  const job = jobs[idx]
+  if (!job) return
 
   const ok = await ctx.ui.confirm(
     `Cancel "${job.name}"?`,

package/node_modules/@herbertgao/pi-subagents/src/ui/select-item.ts

@@ -0,0 +1,48 @@
+/**
+ * select-item.ts — pick an item from a list via `ctx.ui.select`, safely.
+ *
+ * Pi's dialog API is `select(title, options: string[]) => Promise<string | undefined>`:
+ * strings in, string out, with no index or value form. Callers therefore have to
+ * map the returned string back to the item it came from, and the obvious way —
+ * `labels.indexOf(choice)` over a parallel array — silently resolves to the
+ * FIRST match whenever two rows format identically. Row formatters here truncate
+ * (job names to 18 chars, agent descriptions to whatever fits), and the text they
+ * truncate is LLM-authored, so collisions are ordinary rather than exotic.
+ *
+ * This numbers every row, which makes the labels unique by construction — no
+ * data-dependent branch that only executes in the case nobody exercises — and
+ * keeps each label paired with its item so a later edit that sorts or filters
+ * between building and resolving cannot desync them.
+ */
+
+/** Minimal shape of the `ctx.ui` surface this needs. */
+export interface SelectUI {
+  select(title: string, options: string[]): Promise<string | undefined>
+}
+
+/**
+ * Show a numbered picker and return the chosen item (not its label).
+ *
+ * Returns undefined when the user escapes, or when the returned string is not
+ * one we offered.
+ */
+export async function selectItem<T>(
+  ui: SelectUI,
+  title: string,
+  items: readonly T[],
+  format: (item: T, index: number) => string,
+): Promise<T | undefined> {
+  // Pad the number so a 10+ item list keeps its columns aligned.
+  const width = String(items.length).length
+  const rows = items.map((item, i) => ({
+    item,
+    label: `${String(i + 1).padStart(width)}. ${format(item, i)}`,
+  }))
+
+  const choice = await ui.select(
+    title,
+    rows.map((r) => r.label),
+  )
+  if (!choice) return undefined
+  return rows.find((r) => r.label === choice)?.item
+}

package/node_modules/@juicesharp/rpiv-ask-user-question/docs/keyboard.md

@@ -18,6 +18,13 @@ adapts to the size of your terminal.
 | `Ctrl+U` | Clear the current custom-answer draft. | `Type something.` input |
 | `Ctrl+]` | Collapse or expand the dialog. Configurable via `collapseKey`. | Everywhere, including while collapsed |
 
+The table names the default keys; the dialog actually follows your Pi keybindings.
+Confirm listens to both `tui.select.confirm` and `tui.input.submit`, and a key bound to
+`tui.input.newLine` always inserts a newline even if it also matches confirm. So a
+Slack-style configuration — `enter` folded into `tui.input.newLine`, submit moved to
+`ctrl+enter` — keeps working: `enter` breaks lines, and your submit key confirms
+everywhere `Enter` does.
+
 In a multi-select question, `Enter` on a regular row toggles its checkbox exactly like
 `Space` — it does not submit. Committing the question means focusing the `Next` row and
 pressing `Enter`. That is deliberate: it makes `Enter` a zero-cost way to flip boxes

package/node_modules/@juicesharp/rpiv-ask-user-question/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@juicesharp/rpiv-ask-user-question",
-	"version": "2.4.0",
+	"version": "2.5.2",
 	"description": "Pi extension. A structured questionnaire the model can put to you when it would otherwise guess, with typed options instead of free-form replies.",
 	"keywords": [
 		"pi-package",
@@ -93,7 +93,7 @@
 		}
 	},
 	"dependencies": {
-		"@juicesharp/rpiv-config": "^2.4.0",
+		"@juicesharp/rpiv-config": "^2.5.2",
 		"typebox": "^1.1.24"
 	}
 }

package/node_modules/@juicesharp/rpiv-ask-user-question/state/build-questionnaire.ts

@@ -130,6 +130,13 @@ class QuestionnaireBuilder {
 		const textEditorTheme = editorTheme(this.theme);
 		this.notesInput = new Editor(this.tui, textEditorTheme);
 		this.inlineInput = new Editor(this.tui, textEditorTheme);
+		// The key router owns confirm/submit semantics; keys reaching these headless
+		// editors are text-editing only. Without this, a `tui.input.submit` match inside
+		// Editor.handleInput would run submitValue(), which resets the buffer and
+		// silently destroys the draft — no onSubmit is wired here, so the text is
+		// unrecoverable (#156).
+		this.notesInput.disableSubmit = true;
+		this.inlineInput.disableSubmit = true;
 	}
 
 	build(): QuestionnaireBuilt {

package/node_modules/@juicesharp/rpiv-ask-user-question/state/key-router.ts

@@ -6,6 +6,7 @@ import type { QuestionnaireRuntime, QuestionnaireState } from "./state.js";
 const KEYBIND_UP = "tui.select.up";
 const KEYBIND_DOWN = "tui.select.down";
 const KEYBIND_CONFIRM = "tui.select.confirm";
+const KEYBIND_SUBMIT = "tui.input.submit";
 const KEYBIND_CANCEL = "tui.select.cancel";
 const KEYBIND_NEW_LINE = "tui.input.newLine";
 const KEYBIND_EDITOR_UP = "tui.editor.cursorUp";
@@ -39,6 +40,16 @@ export interface QuestionnaireKeybindings {
 	matches(data: string, name: string): boolean;
 }
 
+// Confirm has two semantic sources: `tui.select.confirm` (the select-list default)
+// and `tui.input.submit` (the user's "send" key). A Slack-style configuration folds
+// `enter` into `tui.input.newLine` and moves submit elsewhere (e.g. `ctrl+enter`);
+// the newline checks below stay first, so without the submit source every confirm
+// branch would be shadowed by the collision and no key could confirm (#156). With
+// pi defaults both names resolve to `enter`, so matching either is equivalent.
+function isConfirm(kb: QuestionnaireKeybindings, data: string): boolean {
+	return kb.matches(data, KEYBIND_CONFIRM) || kb.matches(data, KEYBIND_SUBMIT);
+}
+
 export function wrapTab(index: number, total: number): number {
 	if (total <= 0) return 0;
 	return ((index % total) + total) % total;
@@ -183,7 +194,7 @@ export function routeKey(data: string, state: QuestionnaireState, runtime: Quest
 	if (state.notesVisible) {
 		if (kb.matches(data, KEYBIND_CANCEL)) return { kind: "notes_exit" };
 		if (kb.matches(data, KEYBIND_NEW_LINE)) return { kind: "notes_forward", data };
-		if (kb.matches(data, KEYBIND_CONFIRM)) return { kind: "notes_exit" };
+		if (isConfirm(kb, data)) return { kind: "notes_exit" };
 		return { kind: "notes_forward", data };
 	}
 
@@ -191,7 +202,7 @@ export function routeKey(data: string, state: QuestionnaireState, runtime: Quest
 		// Newline takes precedence over confirmation if a user configuration binds
 		// the same physical key to both semantic actions.
 		if (kb.matches(data, KEYBIND_NEW_LINE)) return { kind: "ignore" };
-		if (kb.matches(data, KEYBIND_CONFIRM)) {
+		if (isConfirm(kb, data)) {
 			const answer = buildSingleSelectAnswer(state, runtime);
 			if (!answer) return { kind: "ignore" };
 			return { kind: "confirm", answer, autoAdvanceTab: computeAutoAdvanceTab(state, runtime) };
@@ -219,7 +230,7 @@ export function routeKey(data: string, state: QuestionnaireState, runtime: Quest
 			const next = wrapTab(state.submitChoiceIndex + delta, 2);
 			return { kind: "submit_nav", nextIndex: (next === 1 ? 1 : 0) as 0 | 1 };
 		}
-		if (kb.matches(data, KEYBIND_CONFIRM)) {
+		if (isConfirm(kb, data)) {
 			// D1 (revised): Submit always submits; Cancel always cancels. The warning header
 			// is informational only — `allAnswered(state)` no longer gates submission. Partial
 			// answers flow through `orderedAnswers()` in the host.
@@ -265,7 +276,7 @@ export function routeKey(data: string, state: QuestionnaireState, runtime: Quest
 			if (focusedMeta?.activatesInputMode) return { kind: "ignore" };
 			return { kind: "toggle", index: state.optionIndex };
 		}
-		if (kb.matches(data, KEYBIND_CONFIRM)) {
+		if (isConfirm(kb, data)) {
 			// Enter on the "Type something." row is handled by the inputMode block above
 			// (→ confirm kind:"custom"). Defensive: never enter the toggle/multi_confirm
 			// path for an inputMode-activating row.
@@ -289,7 +300,7 @@ export function routeKey(data: string, state: QuestionnaireState, runtime: Quest
 		return { kind: "ignore" };
 	}
 
-	if (kb.matches(data, KEYBIND_CONFIRM)) {
+	if (isConfirm(kb, data)) {
 		const answer = buildSingleSelectAnswer(state, runtime);
 		if (!answer) return { kind: "ignore" };
 		return { kind: "confirm", answer, autoAdvanceTab: computeAutoAdvanceTab(state, runtime) };

package/node_modules/@juicesharp/rpiv-ask-user-question/state/questionnaire-session.ts

@@ -139,7 +139,9 @@ export class QuestionnaireSession {
 	}
 
 	private mirrorNotesDraft(s: QuestionnaireState): QuestionnaireState {
-		const draft = this.notesInput.getText();
+		// Drafts restore through Editor.setText, which clears the backing paste map —
+		// read expanded so stored drafts never orphan a paste marker.
+		const draft = this.notesInput.getExpandedText?.() ?? this.notesInput.getText();
 		return s.notesDraft === draft ? s : { ...s, notesDraft: draft };
 	}
 
@@ -202,7 +204,7 @@ export class QuestionnaireSession {
 		const lastLine = this.inlineInput.getLines().length - 1;
 		return {
 			keybindings: this.keybindings,
-			inputBuffer: this.inlineInput.getText(),
+			inputBuffer: this.inlineInput.getExpandedText?.() ?? this.inlineInput.getText(),
 			canMoveInputUp: cursor.line > 0,
 			canMoveInputDown: cursor.line < lastLine,
 			questions: this.questions,

package/node_modules/@narumitw/pi-btw/README.md

@@ -58,14 +58,15 @@ Examples:
 /btw is this API name idiomatic?
 ```
 
-Running `/btw` alone opens a menu with **Start side thread** selected first. When the current Pi
-session has non-empty side threads in memory, **Resume side thread** opens a bounded choice list;
+Running `/btw` alone opens a menu with **Start side thread** selected first.
+When the current Pi session has non-empty side threads in memory, **Resume side thread** opens a bounded searchable choice list.
+Search matches the displayed first question and question count while returning the thread's raw in-memory ID.
 **Settings** changes the starting thinking level and whether shortcut changes are remembered.
-Each Resume row keeps the first question as its fixed title, shows its question count, and the list
-is ordered by the newest recorded answer or visible error. Opening and closing a thread without a
-new result does not reorder it. `/btw <question>` bypasses this menu and always starts a fresh side
-thread. Its answer opens above the side-thread editor. The side thread uses a dedicated full-screen
-terminal view.
+Each Resume row keeps the first question as its fixed title, shows its question count, and the list is ordered by the newest recorded answer or visible error.
+Opening and closing a thread without a new result does not reorder it.
+`/btw <question>` bypasses this menu and always starts a fresh side thread.
+Its answer opens above the side-thread editor.
+The side thread uses a dedicated full-screen terminal view.
 The main agent continues running in the background, but its screen rendering stays suspended until
 `/btw` closes, so new main-thread output cannot move a mouse selection inside the side thread.
 Drag the primary mouse button across side-thread text to select and copy it through Pi's terminal

package/node_modules/@narumitw/pi-btw/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@narumitw/pi-btw",
-	"version": "0.50.0",
+	"version": "0.51.0",
 	"description": "Pi extension that adds a /btw side-question command.",
 	"type": "module",
 	"license": "MIT",
@@ -43,7 +43,7 @@
 		"directory": "packages/pi-btw"
 	},
 	"dependencies": {
-		"@narumitw/pi-tui-kit": "^0.49.1"
+		"@narumitw/pi-tui-kit": "^0.54.0"
 	},
 	"peerDependencies": {
 		"@earendil-works/pi-ai": "*",

package/node_modules/@narumitw/pi-btw/src/menu.ts

@@ -120,6 +120,7 @@ export async function showBtwCommandMenu(
 			resume: () => ({
 				kind: "choice",
 				title: "Resume BTW side thread",
+				enableSearch: true,
 				items: resumeThreads.map((thread) => ({
 					id: thread.id,
 					label: thread.title,