little-coder 1.9.3 → 1.9.4

package/.pi/extensions/subagent/index.ts

@@ -8,6 +8,7 @@ import {
   type SubCoderResult,
 } from "./spawn.ts";
 import { SubCoderTracker } from "./tracker.ts";
+import { truncateLineToWidth } from "../_shared/width.ts";
 
 // The `dispatch` tool: the main little-coder spawns isolated child little-coder
 // sessions ("sub-coders") to research a focused question — they read the repo
@@ -190,11 +191,22 @@ export default function (pi: ExtensionAPI) {
   });
 }
 
-/** A minimal pi-tui Component backed by precomputed lines. */
-function makeComponent(lines: string[]) {
+/** A minimal pi-tui Component backed by precomputed lines.
+ *
+ * pi paints custom tool-result panels with a 1-char left margin + background-
+ * frame fill, so any line we hand back that's wider than `width - 1` overflows
+ * the terminal and crashes pi-tui (issue #51 / reopen of #48 — the dispatch
+ * renderer fed an unbounded sub-coder report sentence into the panel, and on
+ * `--resume` the same renderer paints session history, so the crash recurred
+ * even after v1.9.2 capped the *live* tracker). We respect the pi-supplied
+ * `width` here and truncate every line to `width - 2`, leaving a 2-char
+ * safety margin so wide unicode chars in the report can't sneak past our
+ * char-count-based visibleWidth approximation. */
+export function makeComponent(lines: string[]) {
   return {
-    render(_width: number): string[] {
-      return lines;
+    render(width: number): string[] {
+      const cap = Math.max(1, width - 2);
+      return lines.map((l) => truncateLineToWidth(l, cap));
     },
     invalidate() {},
   };

package/.pi/extensions/subagent/issue-51-repro.test.ts

@@ -0,0 +1,54 @@
+import { describe, it, expect } from "vitest";
+import { makeComponent } from "./index.ts";
+
+// Live regression for issue #51 (and the #48 reopen — same root cause from a
+// different code path). pi paints the dispatch tool-result panel with a 1-char
+// background-color left margin + fill; any line we return wider than
+// `width - 1` overflows pi-tui and crashes the session, including on
+// `--resume` because pi re-renders saved tool results from session history.
+//
+// The user's crash log showed a 134-char sub-coder report sentence rendered
+// at terminal width 133 → 135 > 133. This test drives makeComponent at the
+// same width with the same shape and asserts no emitted line exceeds.
+
+const stripAnsi = (s: string) => s.replace(/\x1b\[[0-9;]*[a-zA-Z]/g, "");
+const visibleWidth = (s: string) => stripAnsi(s).length;
+
+describe("issue #51 — dispatch renderResult doesn't overflow", () => {
+  it("caps a wide sub-coder report line to fit the pi-supplied width", () => {
+    const wideSentence =
+      "There is **no `rate_limits` table**. The entire file defines a single class, `ConversationStore`, which manages only one SQLite table:";
+    // Sanity: this is the exact 134-char shape from the user's crash log.
+    expect(wideSentence.length).toBeGreaterThan(133);
+    const comp = makeComponent([
+      "✓ Storage schema",
+      "**Report: `bot/storage.py` Schema Analysis**",
+      "",
+      wideSentence,
+      "",
+      "  …",
+      "(Ctrl+O to expand)",
+    ]);
+    const out = comp.render(133);
+    const max = Math.max(...out.map((l) => visibleWidth(l)));
+    expect(max).toBeLessThanOrEqual(133);
+    // The truncated wide sentence keeps its prefix verbatim — it's not blanked
+    // out, just clipped with an ellipsis so the user can still read most of it.
+    const truncated = out[3];
+    expect(stripAnsi(truncated).startsWith("There is **no")).toBe(true);
+  });
+
+  it("survives a narrow terminal (40 cols) without throwing", () => {
+    const comp = makeComponent([
+      "very long content " + "x".repeat(500),
+      "another long line " + "y".repeat(200),
+    ]);
+    const out = comp.render(40);
+    expect(Math.max(...out.map((l) => visibleWidth(l)))).toBeLessThanOrEqual(40);
+  });
+
+  it("preserves short lines unchanged", () => {
+    const comp = makeComponent(["short", "tiny"]);
+    expect(comp.render(133)).toEqual(["short", "tiny"]);
+  });
+});

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 All notable changes to little-coder are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and little-coder's public interface (CLI, providers, tools, skills) follows semver starting at `v0.0.1` post-rename.
 
+## [v1.9.4] — 2026-06-18
+
+### Fixed
+- **Dispatch tool-result panel overflows the terminal on wide report lines** ([#51](https://github.com/itayinbarr/little-coder/issues/51), reopen of [#48](https://github.com/itayinbarr/little-coder/issues/48)). v1.9.2 capped every line the *live* sub-coder tracker emitted, but the **dispatch tool's result renderer** (`subagent/index.ts`'s `makeComponent`) was still ignoring the `width` arg pi passes to `render(width)` — it returned the precomputed lines verbatim. pi paints the tool-result panel with a 1-char background-color left margin, so any sub-coder report sentence wider than `terminal_width - 1` overflowed pi-tui. Crash log line 453 was a 134-char markdown sentence rendered at terminal width 133 → 135 > 133. The same path runs on **`--resume`** (pi re-paints saved tool results from session history), so v1.9.2 users still hit it after upgrading whenever they resumed a session with a wide dispatch report saved — that's why @steverhoades caught the regression. `makeComponent` now truncates every emitted line to `width - 2` using the existing `_shared/width.ts` utility (2-char safety margin for wide unicode under our char-count-based `visibleWidth` approximation), so the dispatch panel can no longer crash a session — live, on resume, or anywhere else. New `subagent/issue-51-repro.test.ts` drives `makeComponent` with the user's exact 134-char content shape at width 133 and asserts no emitted line exceeds, plus a narrow-terminal (40-col) survival check.
+
+### Notes for upgraders
+- No CLI-flag or public-API changes. If you saw `Rendered line N exceeds terminal width` on v1.9.2 / 1.9.3 — especially while *resuming* a session — 1.9.4 fixes it. If you still see it after upgrading, the offending line in `~/.pi/agent/pi-crash.log` should let us spot the source; reopen #51 or #48 with the log attached.
+
+---
+
 ## [v1.9.3] — 2026-06-18
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "little-coder",
-  "version": "1.9.3",
+  "version": "1.9.4",
   "description": "A pi-based coding agent optimized for small local language models. Reproduces the whitepaper's scaffold-model-fit adaptations as pi extensions.",
   "homepage": "https://github.com/itayinbarr/little-coder",
   "repository": {