@selesai/code 0.8.3 → 0.8.4

package/dist/extensions/pi-intercom/skills/pi-intercom/SKILL.md

@@ -23,6 +23,7 @@ This skill covers how to handle those orchestrator-side escalations.
 - **Context handoffs**: Send findings from a research session to an execution session
 - **Clarification loops**: Worker asks questions, planner answers, work continues
 - **Multi-session workflows**: Coordinate between specialized sessions (frontend/backend, research/implementation)
+- **Cross-codebase peer messages**: Message an explicit live peer in another project, or open a visible Herdr project pane when a long-lived conversation is needed
 
 ## Core Patterns
 
@@ -126,7 +127,39 @@ intercom({
 })
 ```
 
-### Pattern 6: Handle Subagent Escalations (Orchestrator Side)
+### Pattern 6: Cross-Codebase Peer Messages
+
+Use `to` alone to message any explicit live peer on the machine, even when it is
+in another codebase. Use `cwd` alone when there should be exactly one live peer
+in that repo. Use `to` plus `cwd` when the directory is a safety guard.
+
+```typescript
+intercom({
+  action: "ask",
+  cwd: "/path/to/other-repo",
+  to: "workbench-agent",
+  message: "Which module owns workbench source slices?"
+})
+```
+
+Only open a Herdr project pane when you need a durable visible peer session in
+that repo. For bounded work, prefer `pi-subagents` with an explicit `cwd`; the
+child can use `contact_supervisor` for owner decisions and regular `intercom`
+for explicit peer coordination.
+
+```typescript
+intercom({
+  action: "send",
+  cwd: "/path/to/other-repo",
+  openProjectPaneIfMissing: true,
+  message: "Let's discuss the workbench API ergonomics in this repo."
+})
+```
+
+If a live session already exists in that `cwd`, intercom reuses it. If multiple
+sessions are active there, pass `to` to select one by name or session ID.
+
+### Pattern 7: Handle Subagent Escalations (Orchestrator Side)
 
 When `pi-subagents` spawns a delegated child and supplies child bridge metadata,
 that child can reach you through `contact_supervisor`. You receive a formatted
@@ -190,13 +223,15 @@ intercom({ action: "reply", to: "subagent-worker-78f659a3-1", message: "Use the
 **Important:** Only sessions where `pi-subagents` supplied child bridge metadata
 get the `contact_supervisor` tool. Normal sessions use the regular `intercom`
 tool. If you see the formatted supervisor decision/progress update message, treat
-it as a `contact_supervisor` escalation.
+it as a `contact_supervisor` escalation. A subagent may use regular `intercom` for
+peer coordination, including peers in other directories, but owner decisions and
+new visible project panes should go through the supervisor.
 
 ## Key Differences
 
 | Action | Behavior | Use When |
 |--------|----------|----------|
-| `send` | Fire-and-forget | You don't need a response |
+| `send` | Fire-and-forget; infers the sole pending ask as its reply | You don't need a response |
 | `ask` | Blocks until reply (10 min default, configurable with `PI_INTERCOM_ASK_TIMEOUT_MS`) | You need an answer to continue |
 | `reply` | Responds to the active or pending inbound ask | You were asked something and need to answer naturally |
 | `pending` | Lists unresolved inbound asks | You need to see who is waiting before replying |
@@ -301,9 +336,10 @@ If neither `cmux` nor `tmux` is available, skip this path and use normal `interc
 
 ### `ask` Limitations
 
+- **Connected targets only**: `ask` fails immediately when the target is not in the live intercom roster. Use `list` before asking when liveness is uncertain; use `send` for non-blocking mailbox delivery.
 - **Configurable timeout**: If no reply arrives before the shared ask timeout, the ask fails. The default is 10 minutes; set `PI_INTERCOM_ASK_TIMEOUT_MS` to a positive millisecond value to change it.
 - **One at a time**: Cannot have multiple pending asks from the same session
-- **Cannot self-target**: A session cannot ask itself
+- **Cannot self-target**: A session cannot ask itself, including through disconnected-mailbox remapping
 
 ```typescript
 // Check if already waiting before asking
@@ -316,8 +352,10 @@ if (result.isError && result.content[0].text.includes("Already waiting")) {
 ### `send` Behavior
 
 - **No timeout**: Message is delivered or fails immediately
-- **Confirmation dialogs**: If `confirmSend: true` in config, interactive sessions show a confirmation dialog
-- **Replies skip confirmation**: Messages with `replyTo` never show confirmation dialogs
+- **Sole pending ask inference**: If the destination has exactly one pending inbound ask, `send` attaches its `replyTo` and reports `Reply sent to <target> (inferred from pending ask)`
+- **Ambiguity stays unthreaded**: Zero or multiple matching asks leave the send as an ordinary message
+- **Confirmation dialogs**: If `confirmSend: true` in config, interactive sessions confirm ordinary and inferred sends
+- **Explicit replies skip confirmation**: A caller-supplied `replyTo` skips the dialog
 
 ## Best Practices
 
@@ -351,7 +389,9 @@ intercom({
 
 ### Include reply hints in messages
 
-Make it easy for recipients to respond:
+Make it easy for recipients to respond. Busy recipients receive your message
+through Selesai's steering queue at the next safe model boundary without aborting
+their active turn, so a reply hint keeps the conversation actionable:
 
 ```typescript
 // GOOD: Recipient sees exact command to reply
@@ -402,7 +442,7 @@ if (!result.delivered) {
   await intercom({ action: "list" });
 }
 ```
-Replies to recently disconnected named senders can be queued by the broker and delivered if that sender reconnects with the same name. New sends still need a known live or recently disconnected target.
+Replies to recently disconnected explicitly named senders can be queued by the broker and delivered if that sender reconnects with the same name and directory. Runtime-only `subagent-chat-...` aliases are not reconnect identities. New `send` calls may target a known live or recently disconnected session; blocking `ask` calls require a live target.
 
 **Ask timeout**
 ```typescript
@@ -432,7 +472,7 @@ if (!result.delivered) {
 
 ### Connection lost
 
-Sessions automatically reconnect if the broker restarts. If persistently disconnected:
+Sessions automatically reconnect if the broker restarts. A liveness heartbeat round-trips a lightweight request and tears down half-open sockets (for example after the broker is killed without a clean shutdown), so the `disconnected` → reconnect path fires within a bounded window. If persistently disconnected:
 
 ```typescript
 intercom({ action: "status" })

package/dist/extensions/pi-intercom/test/inline-message.test.ts

@@ -115,11 +115,11 @@ test("inline message colors follow the tool-title, text, muted-border, and dim-m
   const lines = component.render(72);
   const rendered = lines.join("\n");
 
-  assert.match(lines[0], /^\u001b\[34m╭\u001b\[0m\u001b\[32m 📨 From:/);
+  assert.match(lines[0], /^\u001b\[34m╭\u001b\[0m\u001b\[32m From:/);
   assert.match(rendered, /\u001b\[34m│\u001b\[0m\u001b\[33mBody copy\u001b\[0m/);
-  assert.match(rendered, /\u001b\[35m ↩ To reply: intercom reply\u001b\[0m/);
-  assert.match(rendered, /\u001b\[35m 📎 note\.txt\u001b\[0m/);
-  assert.match(rendered, /\u001b\[35m ↳ Reply to parent-m\u001b\[0m/);
+  assert.match(rendered, /\u001b\[35m To reply: intercom reply\u001b\[0m/);
+  assert.match(rendered, /\u001b\[35m Attachment: note\.txt\u001b\[0m/);
+  assert.match(rendered, /\u001b\[35m Reply to parent-m\u001b\[0m/);
   assert.match(lines.at(-1)!, /^\u001b\[34m╰─+╯\u001b\[0m$/);
   assert.ok(calls.includes("toolTitle"));
   assert.ok(calls.includes("text"));
@@ -134,9 +134,9 @@ test("collapsed inline messages preserve the same hierarchy without accent", ()
 
   const rendered = component.render(72).join("\n");
 
-  assert.match(rendered, /\u001b\[32m 📨 From:/);
+  assert.match(rendered, /\u001b\[32m From:/);
   assert.match(rendered, /\u001b\[33mThis is a long message/);
-  assert.match(rendered, /\u001b\[35m ↩ To reply:/);
+  assert.match(rendered, /\u001b\[35m To reply:/);
   assert.ok(!calls.includes("accent"));
 });
 
@@ -146,7 +146,7 @@ test("semantic styling remains ANSI- and Unicode-width safe", () => {
     ...message,
     content: { text: "\u001b[36m色付き本文\u001b[0m with emoji 🧪 and a long Unicode tail 計画計画計画" },
   };
-  const component = new InlineMessageComponent(unicodeFrom, unicodeMessage, styledTheme() as any, "返信 📨");
+  const component = new InlineMessageComponent(unicodeFrom, unicodeMessage, styledTheme() as any, "返信");
 
   for (const width of [18, 31, 52]) {
     const lines = component.render(width);
@@ -176,8 +176,8 @@ test("inline messages pick up mutable theme proxy changes on rerender", () => {
   palette.muted = 90;
   const after = component.render(72).join("\n");
 
-  assert.match(before, /\u001b\[32m 📨 From:/);
-  assert.match(after, /\u001b\[96m 📨 From:/);
+  assert.match(before, /\u001b\[32m From:/);
+  assert.match(after, /\u001b\[96m From:/);
   assert.match(after, /\u001b\[97mThis is a long message/);
   assert.match(after, /\u001b\[90m╭/);
   assert.notEqual(before, after);

package/dist/extensions/pi-intercom/types.ts

@@ -3,6 +3,8 @@ export const EXTENSION_BUS_FEATURE = "extension-bus-v1";
 export interface SessionInfo {
   id: string;
   name?: string;
+  /** True only when the extension synthesized name for an unnamed runtime. */
+  runtimeFallbackAlias?: boolean;
   cwd: string;
   model: string;
   pid: number;
@@ -83,7 +85,7 @@ export type ClientMessage =
   | { type: "message_receipt"; receipt: MessageReceipt }
   | { type: "cancel_message"; messageId: string }
   | { type: "cancel_ask"; messageId: string }
-  | { type: "presence"; name?: string; status?: string; model?: string; contextPct?: number | null; contextTokens?: number | null; contextWindow?: number | null }
+  | { type: "presence"; name?: string; runtimeFallbackAlias?: boolean; status?: string; model?: string; contextPct?: number | null; contextTokens?: number | null; contextWindow?: number | null }
   | {
       type: "extension_publish";
       namespace: string;

package/dist/extensions/pi-intercom/ui/inline-message.ts

@@ -42,7 +42,7 @@ export class InlineMessageComponent implements Component {
     }
     const bodyWidth = Math.max(1, width - 2);
 
-    const header = ` 📨 From: ${senderName} (${this.from.cwd}) `;
+    const header = ` From: ${senderName} (${this.from.cwd}) `;
     const headerText = truncateToWidth(this.collapsed ? `${header} Ctrl+O expands ` : header, bodyWidth, "");
     const headerPadding = Math.max(0, bodyWidth - visibleWidth(headerText));
     lines.push(
@@ -62,12 +62,12 @@ export class InlineMessageComponent implements Component {
       lines.push(frameLine(this.theme.fg("text", this.collapsedPreview)));
 
       const meta: string[] = [];
-      if (this.replyCommand) meta.push(`↩ To reply: ${this.replyCommand}`);
+      if (this.replyCommand) meta.push(`To reply: ${this.replyCommand}`);
       if (this.message.content.attachments?.length) {
         const count = this.message.content.attachments.length;
-        meta.push(`📎 ${count} attachment${count === 1 ? "" : "s"}`);
+        meta.push(`${count} attachment${count === 1 ? "" : "s"}`);
       }
-      if (this.message.replyTo && !this.message.expectsReply) meta.push(`↳ Reply to ${this.message.replyTo.slice(0, 8)}`);
+      if (this.message.replyTo && !this.message.expectsReply) meta.push(`Reply to ${this.message.replyTo.slice(0, 8)}`);
       meta.push("Ctrl+O to expand");
 
       lines.push(frameLine(this.theme.fg("dim", ` ${meta.join(" · ")}`)));
@@ -87,7 +87,7 @@ export class InlineMessageComponent implements Component {
 
     if (this.replyCommand) {
       lines.push(frameLine(""));
-      const replyLines = wrapTextWithAnsi(this.theme.fg("dim", ` ↩ To reply: ${this.replyCommand}`), bodyWidth);
+      const replyLines = wrapTextWithAnsi(this.theme.fg("dim", ` To reply: ${this.replyCommand}`), bodyWidth);
       for (const line of replyLines) {
         lines.push(frameLine(line));
       }
@@ -96,13 +96,13 @@ export class InlineMessageComponent implements Component {
     if (this.message.content.attachments?.length) {
       lines.push(frameLine(""));
       for (const att of this.message.content.attachments) {
-        lines.push(frameLine(this.theme.fg("dim", ` 📎 ${att.name}`)));
+        lines.push(frameLine(this.theme.fg("dim", ` Attachment: ${att.name}`)));
       }
     }
 
     if (this.message.replyTo && !this.message.expectsReply) {
       lines.push(frameLine(""));
-      lines.push(frameLine(this.theme.fg("dim", ` ↳ Reply to ${this.message.replyTo.slice(0, 8)}`)));
+      lines.push(frameLine(this.theme.fg("dim", ` Reply to ${this.message.replyTo.slice(0, 8)}`)));
     }
 
     lines.push(this.theme.fg("muted", `╰${borderChar.repeat(bodyWidth)}╯`));

package/dist/extensions/pi-powerline-footer/.github/workflows/test.yml

@@ -14,8 +14,8 @@ jobs:
       matrix:
         os: [ubuntu-latest, windows-latest]
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/checkout@v5
+      - uses: actions/setup-node@v5
         with:
           node-version: 24
           cache: npm

package/dist/extensions/pi-powerline-footer/CHANGELOG.md

@@ -7,9 +7,22 @@
 - **Guide defaults to compact mode** — When `selesaiGuide.mode` is unset, the recurring guide opens in compact mode instead of the full tour. Explicit `full`, `compact`, or `off` settings are still honored.
 
 ### Changed
-- **Upstream 0.12.3 merge (Selesai fork)** — Updated from upstream v0.5.4 to v0.12.3. Adopts the Powerline queue/inbox (`/idea`, `/ideas`, `/queue`, `/ideas next`, `/ideas issue`), compaction-aware queue delivery, `/cd` session directory switching, cost currency and subagent cost accounting, `powerline.separator`/`layout`/`placement`/`disabledSegments`/`welcome` options, git host icons, cached session token stats, strict TypeScript gate, and all upstream fixes through 0.12.3. Selesai-specific features are preserved: the guide overlay, the TPS tracker, session-usage accounting, and mode-aware autocomplete trigger forwarding.
+- **Upstream 0.13.0 merge (Selesai fork)** — Updated from upstream v0.12.3 to v0.13.0. Adopts editor typing/cursor responsiveness work (opt-in profiling, bounded fast render path, cached queue/prompt render, async git completion lookups, debounced bash ghost completion), opt-in bash completions, and read-only git polling that no longer takes `.git/index.lock`. Follows upstream's removal of the saved idea inbox (idea capture commands, sigil capture, and issue handoff). Selesai-specific features are preserved: the guide overlay, the TPS tracker, session-usage accounting, mode-aware autocomplete trigger forwarding, the fixed-editor prompt glyph and border color, and `@selesai/code` path resolvers.
 - **Native fullscreen dock** — Removed the unsupported terminal-split compositor and its fixed-editor/mouse-scroll/chat-jump controls. Powerline status, editor, and widgets now use Pi 0.84.1's native fullscreen dock; Selesai defaults to fullscreen while `tuiMode: "regular"` opts out.
 
+## [0.13.0] - 2026-08-12
+
+### Changed
+- **Editor typing responsiveness** — Avoid expanding paste markers or joining full drafts in editor hot paths, debounce bash ghost completion, run git completion lookups asynchronously, cache queue/prompt render work, use a bounded fast render path for large editor drafts, and avoid full grapheme scans when deleting plain ASCII from long lines. Opt-in profiling and render A/B flags now identify remaining editor costs without affecting normal sessions.
+- **Editor hot-path cleanup** — Simplified type narrowing in the fast Backspace path without changing behavior.
+- **Bash completions are opt-in** — Disable Powerline bash ghost suggestions and one-off `!command` predictions by default. Set `bashMode.completions` to `true` to re-enable them.
+- **GitHub Actions runtime** — Updated checkout and Node setup actions to their Node 24 runtime versions.
+
+### Fixed
+- **Git polling no longer takes `.git/index.lock`** — Read-only git commands now run with `GIT_OPTIONAL_LOCKS=0`, so polling `git status` stops refreshing the index as a side effect, which raced interactive git in the same repo and could leave an orphaned lock behind. Thanks to Max Kaye (@XertroV) for #156.
+
+### Removed
+- **Saved idea inbox** — Removed unused idea capture commands, sigil capture, and issue handoff. The queue now manages queued prompts only.
 
 ## [0.12.3] - 2026-08-09
 

package/dist/extensions/pi-powerline-footer/README.md

@@ -13,7 +13,7 @@ Customizes the default [pi](https://github.com/badlogic/pi-mono) editor with a p
 
 **Editor stash** — Press `Alt+S` to save your editor content and clear the editor, type a quick prompt, and your stashed text auto-restores when the agent finishes. Toggles between stash, pop, and update-existing-stash. A `stash` indicator appears in the powerline bar while text is stashed.
 
-**Powerline Queue + Inbox** — Capture thoughts without interrupting the current agent. Type `# <idea>` and press Enter to save an idea instead of sending it; `# @global <idea>`, `# @current <idea>`, and `# @alias <idea>` route it. Messages typed during compaction are held by Powerline and delivered after successful compaction instead of disappearing into Pi's native queue. `/idea`, `/ideas`, and `/queue` provide a file-backed inbox for current-session prompts, project ideas, aliases, retries, clears, and manual delivery. Use `/ideas next` to work the oldest active idea in the current session, or `/ideas issue` to hand it to the current agent for safe GitHub issue triage. Active queue, idea, and blocked counts appear in the `queue` segment only when there is something to show.
+**Powerline Queue** — Messages typed during compaction are held by Powerline and delivered after successful compaction instead of disappearing into Pi's native queue. `/queue` provides a file-backed queue for aliases, retries, clears, and manual delivery. Active queued and blocked counts appear in the `queue` segment only when there is something to show.
 
 **Working Vibes** — AI-generated themed loading messages. Set `/vibe star trek` and your "Working..." becomes "Running diagnostics..." or "Engaging warp drive...". Supports any theme: pirate, zen, noir, cowboy, etc.
 
@@ -37,7 +37,7 @@ Customizes the default [pi](https://github.com/badlogic/pi-mono) editor with a p
 
 **Sticky bash mode** — Toggle bash mode with `ctrl+shift+b` or `/bash-mode`. It keeps a managed shell session alive for the current pi session, shows a dedicated `shell_mode` segment, streams command output into an embedded transcript below the editor, and lets `cd` or exported state persist across commands.
 
-**Shell ghost suggestions** — Bash mode is now ghost-first. Successful per-project shell history is the primary source, while deterministic path and git continuations can still extend an existing command. Shell-native completion probes are disabled so `!command` predictions never spawn interactive shell completion subprocesses. At command position, short stems first resolve from the newest successful local command, can use guarded global shell history for high-confidence heads like `git`, and finally fall back to a tiny curated default set when history is absent. Right now that curated set is `g` → `git status` and `c` → `cd ..`. If the bash prompt is empty, bash mode shows the newest successful project-history ghost suggestion when one exists, otherwise it stays empty. The same inline predictions now also kick in for one-off `!command` and `!!command` prompts. Right Arrow or Tab accepts ghost text into the editor, and Enter runs the current shell command.
+**Shell ghost suggestions** — Optional bash-mode completions can show inline ghost suggestions from successful project shell history, deterministic path and git continuations, guarded global history for high-confidence heads like `git`, and a tiny curated default set. Right now that curated set is `g` → `git status` and `c` → `cd ..`. Shell-native completion probes stay disabled. Set `bashMode.completions` to `true` to enable bash-mode ghosts and one-off `!command` / `!!command` predictions.
 
 ## Installation
 
@@ -53,40 +53,16 @@ Activates automatically. Toggle with `/powerline`, switch presets with `/powerli
 
 Use `/cd <path>` to continue the current conversation from another working directory. It supports relative paths, absolute paths, `~`, `~/...`, and directory completions. With no argument, `/cd` prints the current Pi session directory. The command switches into a cwd-updated session file so Pi tools and the footer path segment agree after the change.
 
-Powerline Queue + Inbox commands and capture shortcuts:
+Powerline Queue commands:
 
-- `# <text>` — capture an idea for the current project without sending it to the agent
-- `# @global <text>` — capture a global idea
-- `# @current <text>` — capture an idea targeted to the current session
-- `/queue alias <name> [path]` — save a project alias, defaulting to the current cwd when `path` is omitted
-- `# @name <text>` — capture an idea for a saved project alias
 - `/compact <text>` — compact now and queue `<text>` as the next prompt after successful compaction
-- `/idea [@target] <text>` — command form of idea capture, useful for scripts and users who disable the sigil
-- `/idea issue [id]` — hand the oldest active idea, or a specific idea, to the current agent for safe GitHub issue triage
-- `/ideas` — open the captured-ideas picker
-- `/ideas next` — send the oldest active idea to the current session
-- `/ideas issue [id]` — ask the current agent to dedupe and file a GitHub issue only when the target repo is clear and owned/controlled
-- `/ideas send <id>` — send an idea to the current session
 - `/queue` — open the queued-prompt picker
-- `/queue send [id]` / `/queue retry [id]` — deliver a queued item now
-- `/queue clear <id|all>` — clear queued prompt items
-- `/queue target <id> @name|global|current` — retarget a queued item
-
-The default capture sigil is `#`. When the editor text starts with `# `, the prompt glyph changes to `#`; pressing Enter saves the idea, clears the editor, and leaves the original sigil text in editor history for quick recovery. Configure or disable this under `powerline.queue.captureSigil`:
-
-```json
-{
-  "powerline": {
-    "queue": {
-      "captureSigil": "#"
-    }
-  }
-}
-```
-
-Set `captureSigil` to `false` if you often submit markdown headings and prefer `/idea` instead.
+- `/queue alias <name> [path]` — save a project alias, defaulting to the current cwd when `path` is omitted
+- `/queue send [id]` / `/queue retry [id]` — deliver a queued prompt now
+- `/queue clear <id|all>` — clear queued prompts
+- `/queue target <id> @name|global|current` — retarget a queued prompt
 
-Captured data is stored under the Pi agent directory in `powerline-footer/inbox.jsonl` and `powerline-footer/projects.json`. `inbox.jsonl` is a stable read surface for orchestrators and helper agents; each line is a queue item with `id`, `text`, `createdAt`, `updatedAt`, `source`, `target`, `intent`, `status`, and optional `error`. Writes should still go through Powerline commands or the store so locking and atomic writes are preserved. Ideas sent with `/ideas next` or `/ideas send <id>` include a small provenance header so the receiving agent can treat them as deferred captured context. `/idea issue` and `/ideas issue` do not file issues directly from the extension; they send a guarded handoff prompt that tells the current agent to dedupe open issues first, create a GitHub issue only for a clear owned/controlled repo, and ask before filing when the target is unclear.
+Queued data is stored under the Pi agent directory in `powerline-footer/inbox.jsonl` and `powerline-footer/projects.json`. `inbox.jsonl` is a stable read surface for orchestrators and helper agents; each line is a queue item with `id`, `text`, `createdAt`, `updatedAt`, `source`, `target`, `intent`, `status`, and optional `error`. Writes should still go through Powerline commands or the store so locking and atomic writes are preserved.
 
 - `/powerline placement below` — move the primary powerline row below the editor
 - `/powerline placement above` — restore the default placement
@@ -117,6 +93,14 @@ You can also set it in the agent settings file (`~/.selesai/agent/settings.json`
 
 **Environment:** `POWERLINE_NERD_FONTS=1` to force Nerd Fonts, `=0` for ASCII.
 
+For typing diagnostics, start Pi with `POWERLINE_DEBUG_PERF=1`, reproduce the slow editor case, then run `/powerline-perf`. Use `/powerline-perf reset` before a focused run. Profiling is off by default. While it is enabled, these A/B flags can disable one render seam before `/reload`:
+
+- `POWERLINE_PERF_FAST_RENDER=0`
+- `POWERLINE_PERF_EDITOR_CHROME=0`
+- `POWERLINE_PERF_WIDGETS=0`
+- `POWERLINE_PERF_BASH_WIDGETS=0`
+- `POWERLINE_PERF_LAST_PROMPT=0`
+
 Preset selection is saved under `powerline` in the agent settings file and restored on startup.
 Run `/powerline default` to switch back to the default preset.
 
@@ -259,13 +243,12 @@ Reset the managed shell with `/bash-reset`.
 While bash mode is active:
 
 - Enter runs the current shell command
-- Right Arrow accepts ghost text into the editor without running it
-- Tab accepts the current ghost suggestion when one exists; otherwise it does nothing
 - Up and Down browse matching shell history
 - `escape` exits bash mode and returns to normal prompt mode
 - `ctrl+c` interrupts the active shell job before falling back to normal pi behavior
+- When `bashMode.completions` is `true`, Right Arrow or Tab accepts ghost text into the editor without running it
 
-The managed shell is persistent for the current pi session. Command output appears in a transcript below the editor, and shell cwd changes are reflected in the footer path and `shell_mode` segment. If the bash prompt is empty, bash mode shows the newest successful project-history ghost suggestion immediately when one exists, including right after mode entry or after the prompt is cleared again. One-off `!command` and `!!command` prompts reuse the same shell prediction pipeline, including ghost text. Mode entry stays quiet: there is no automatic or manual dropdown completion surface, and ghost suggestions do not run shell-native completion probes.
+The managed shell is persistent for the current pi session. Command output appears in a transcript below the editor, and shell cwd changes are reflected in the footer path and `shell_mode` segment. Bash-mode ghost suggestions and one-off `!command` / `!!command` predictions are opt-in because they add editor work. When enabled, bash mode can show the newest successful project-history ghost on an empty prompt. Mode entry stays quiet: there is no automatic or manual dropdown completion surface, and ghost suggestions do not run shell-native completion probes.
 
 ### Bash mode configuration
 
@@ -275,6 +258,7 @@ In `~/.selesai/agent/settings.json` (or under `SELESAI_CODING_AGENT_DIR` when th
 {
   "bashMode": {
     "toggleShortcut": "ctrl+shift+b",
+    "completions": false,
     "transcriptMaxLines": 2000,
     "transcriptMaxBytes": 524288
   }
@@ -308,7 +292,7 @@ Prompt history now has two sources:
 - stashed prompts — up to 12 recent stashed prompts (newest first)
 - recent project prompts — up to 50 recent user-submitted prompts pulled from pi sessions in the current project folder
 
-Selecting a stashed entry lets you insert it or promote it to an idea. Project prompt history entries insert into the editor. If the editor already has text, you can choose `Replace`, `Append`, or `Cancel`.
+Selecting a stashed or project prompt-history entry inserts it into the editor. If the editor already has text, you can choose `Replace`, `Append`, or `Cancel`.
 
 ### Editor clipboard and navigation shortcuts
 
@@ -330,7 +314,6 @@ You can override shortcut keys in the agent settings file:
     "stashHistory": "ctrl+alt+h",
     "copyEditor": "ctrl+alt+c",
     "cutEditor": "ctrl+alt+x",
-    "ideaCapture": null,
     "queueOpen": "ctrl+alt+q",
     "editorStart": "cmd+shift+up",
     "editorEnd": "cmd+shift+down"

package/dist/extensions/pi-powerline-footer/bash-mode/completion.ts

@@ -1,5 +1,5 @@
 import { readdirSync } from "node:fs";
-import { spawnSync } from "node:child_process";
+import { execFile } from "node:child_process";
 import { basename, dirname, isAbsolute, join, resolve } from "node:path";
 import type { AutocompleteItem, AutocompleteProvider, AutocompleteSuggestions } from "@earendil-works/pi-tui";
 import { matchHistoryEntries, readGlobalShellHistory, readProjectHistory } from "./history.ts";
@@ -208,22 +208,28 @@ function getPathSuggestions(token: string, cwd: string): ExtendedCompletionItem[
   }
 }
 
-function runGit(args: string[], cwd: string): string[] {
-  try {
-    const result = spawnSync("git", args, {
-      cwd,
-      encoding: "utf8",
-      stdio: ["ignore", "pipe", "ignore"],
-    });
-    if (result.status !== 0 || !result.stdout) return [];
-    return result.stdout.split("\n").map((line) => line.trim()).filter(Boolean);
-  } catch {
-    // Git-aware completions are optional and should not break the main completion flow.
-    return [];
-  }
+function runGit(args: string[], cwd: string, signal: AbortSignal): Promise<string[]> {
+  return new Promise((resolve) => {
+    try {
+      execFile("git", args, { cwd, encoding: "utf8", signal }, (error, stdout) => {
+        if (error || !stdout) {
+          resolve([]);
+          return;
+        }
+        resolve(stdout.split("\n").map((line) => line.trim()).filter(Boolean));
+      });
+    } catch {
+      // Git-aware completions are optional and should not break the main completion flow.
+      resolve([]);
+    }
+  });
 }
 
-function getGitSuggestions(ctx: TokenContext, cwd: string): ExtendedCompletionItem[] {
+async function getGitSuggestions(
+  ctx: TokenContext,
+  cwd: string,
+  signal: AbortSignal,
+): Promise<ExtendedCompletionItem[]> {
   const tokens = ctx.previousTokens;
   if (tokens[0] !== "git") return [];
 
@@ -246,12 +252,13 @@ function getGitSuggestions(ctx: TokenContext, cwd: string): ExtendedCompletionIt
     return [];
   }
 
-  const refs = [
-    ...runGit(["branch", "--format=%(refname:short)"], cwd),
-    ...runGit(["tag", "--list"], cwd),
-  ];
+  const [branches, tags] = await Promise.all([
+    runGit(["branch", "--format=%(refname:short)"], cwd, signal),
+    runGit(["tag", "--list"], cwd, signal),
+  ]);
+  if (signal.aborted) return [];
 
-  return [...new Set(refs)]
+  return [...new Set([...branches, ...tags])]
     .filter((ref) => ref.startsWith(ctx.token))
     .slice(0, 100)
     .map((ref) => ({
@@ -365,7 +372,8 @@ export class BashCompletionEngine {
       return this.getCommandPositionGhostSuggestion(line, readGlobalShellHistory(shellPath));
     }
 
-    const deterministic = this.getDeterministicInlineSuggestions(ctx, cwd);
+    const deterministic = await this.getDeterministicInlineSuggestions(ctx, cwd, signal);
+    if (signal.aborted) return null;
     const globalHistory = matchHistoryEntries(readGlobalShellHistory(shellPath), line, 5);
     const ranked = boostValidatedItemsFromGlobalHistory(
       line,
@@ -397,10 +405,17 @@ export class BashCompletionEngine {
     return getCuratedCommandFallback(line);
   }
 
-  private getDeterministicInlineSuggestions(ctx: TokenContext, cwd: string): ExtendedCompletionItem[] {
-    const items: ExtendedCompletionItem[] = [];
-    items.push(...withRange(getGitSuggestions(ctx, cwd), ctx.tokenStart, ctx.tokenEnd));
-    items.push(...withRange(getPathSuggestions(ctx.token, cwd), ctx.tokenStart, ctx.tokenEnd));
+  private async getDeterministicInlineSuggestions(
+    ctx: TokenContext,
+    cwd: string,
+    signal: AbortSignal,
+  ): Promise<ExtendedCompletionItem[]> {
+    const gitSuggestions = getGitSuggestions(ctx, cwd, signal);
+    const pathSuggestions = getPathSuggestions(ctx.token, cwd);
+    const items = [
+      ...withRange(await gitSuggestions, ctx.tokenStart, ctx.tokenEnd),
+      ...withRange(pathSuggestions, ctx.tokenStart, ctx.tokenEnd),
+    ];
 
     return uniqueByReplacement(items);
   }