@oh-my-pi/pi-coding-agent 13.7.3 → 13.7.5

package/CHANGELOG.md

@@ -2,6 +2,15 @@
 
 ## [Unreleased]
 
+## [13.7.4] - 2026-03-04
+### Added
+- Added `fetch.useKagiSummarizer` setting to toggle Kagi Universal Summarizer usage in the fetch tool.
+
+### Fixed
+
+- Fixed incorrect message history reference in session title generation that could cause missing or stale titles on first message
+- Added startup check requiring Bun 1.3.7+ for JSONL session parsing (`Bun.JSONL.parseChunk`) and clear upgrade guidance so `/resume` and `--resume` do not silently report missing sessions on older Bun runtimes
+
 ## [13.7.3] - 2026-03-04
 
 ### Added

package/package.json

@@ -1,7 +1,7 @@
 {
 	"type": "module",
 	"name": "@oh-my-pi/pi-coding-agent",
-	"version": "13.7.3",
+	"version": "13.7.5",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"homepage": "https://github.com/can1357/oh-my-pi",
 	"author": "Can Boluk",
@@ -41,12 +41,12 @@
 	},
 	"dependencies": {
 		"@mozilla/readability": "^0.6",
-		"@oh-my-pi/omp-stats": "13.7.3",
-		"@oh-my-pi/pi-agent-core": "13.7.3",
-		"@oh-my-pi/pi-ai": "13.7.3",
-		"@oh-my-pi/pi-natives": "13.7.3",
-		"@oh-my-pi/pi-tui": "13.7.3",
-		"@oh-my-pi/pi-utils": "13.7.3",
+		"@oh-my-pi/omp-stats": "13.7.5",
+		"@oh-my-pi/pi-agent-core": "13.7.5",
+		"@oh-my-pi/pi-ai": "13.7.5",
+		"@oh-my-pi/pi-natives": "13.7.5",
+		"@oh-my-pi/pi-tui": "13.7.5",
+		"@oh-my-pi/pi-utils": "13.7.5",
 		"@sinclair/typebox": "^0.34",
 		"@xterm/headless": "^6.0",
 		"ajv": "^8.18",

package/src/cli.ts

@@ -1,11 +1,39 @@
 #!/usr/bin/env bun
-import { APP_NAME, VERSION } from "@oh-my-pi/pi-utils";
+import { APP_NAME, MIN_BUN_VERSION, VERSION } from "@oh-my-pi/pi-utils";
 /**
  * CLI entry point — registers all commands explicitly and delegates to the
  * lightweight CLI runner from pi-utils.
  */
 import { type CommandEntry, run } from "@oh-my-pi/pi-utils/cli";
 
+function parseSemver(version: string): [number, number, number] {
+	function toint(value: string): number {
+		const int = Number.parseInt(value, 10);
+		if (Number.isNaN(int) || !Number.isFinite(int)) return 0;
+		return int;
+	}
+	const [majorRaw, minorRaw, patchRaw] = version.split(".").map(toint);
+	return [majorRaw, minorRaw, patchRaw];
+}
+
+function isAtLeastBunVersion(minimum: string): boolean {
+	const ver = parseSemver(Bun.version);
+	const min = parseSemver(minimum);
+	for (let i = 0; i < 3; i++) {
+		if (ver[i] !== min[i]) {
+			return ver[i] > min[i];
+		}
+	}
+	return true;
+}
+
+if (typeof Bun.JSONL?.parseChunk !== "function" || !isAtLeastBunVersion(MIN_BUN_VERSION)) {
+	process.stderr.write(
+		`error: Bun runtime must be >= ${MIN_BUN_VERSION} (found v${Bun.version}). Please update Bun: bun upgrade\n`,
+	);
+	process.exit(1);
+}
+
 // Detect known Bun errata that cause TUI crashes (e.g. Bun.stringWidth mishandling OSC sequences).
 if (Bun.stringWidth("\x1b[0m\x1b]8;;\x07") !== 0) {
 	process.stderr.write(`error: Bun runtime errata detected (v${Bun.version}). Please update Bun: bun upgrade\n`);

package/src/config/settings-schema.ts

@@ -490,6 +490,15 @@ export const SETTINGS_SCHEMA = {
 		default: true,
 		ui: { tab: "tools", label: "Enable Fetch", description: "Enable the fetch tool for URL fetching" },
 	},
+	"fetch.useKagiSummarizer": {
+		type: "boolean",
+		default: true,
+		ui: {
+			tab: "tools",
+			label: "Use Kagi in Fetch",
+			description: "Use Kagi Universal Summarizer when rendering HTML in fetch",
+		},
+	},
 	"web_search.enabled": {
 		type: "boolean",
 		default: true,

package/src/modes/controllers/input-controller.ts

@@ -300,7 +300,7 @@ export class InputController {
 			this.ctx.flushPendingBashComponents();
 
 			// Generate session title on first message
-			const hasUserMessages = this.ctx.agent.state.messages.some((m: AgentMessage) => m.role === "user");
+			const hasUserMessages = this.ctx.session.messages.some((m: AgentMessage) => m.role === "user");
 			if (!hasUserMessages && !this.ctx.sessionManager.getSessionName() && !$env.PI_NO_TITLE) {
 				const registry = this.ctx.session.modelRegistry;
 				const smolModel = this.ctx.settings.getModelRole("smol");
@@ -393,7 +393,7 @@ export class InputController {
 		if (allQueued.length === 0) {
 			this.ctx.updatePendingMessagesDisplay();
 			if (options?.abort) {
-				this.ctx.agent.abort();
+				this.ctx.session.abort();
 			}
 			return 0;
 		}
@@ -403,7 +403,7 @@ export class InputController {
 		this.ctx.editor.setText(combinedText);
 		this.ctx.updatePendingMessagesDisplay();
 		if (options?.abort) {
-			this.ctx.agent.abort();
+			this.ctx.session.abort();
 		}
 		return allQueued.length;
 	}

package/src/prompts/tools/hashline.md

@@ -1,41 +1,40 @@
-Applies precise file edits using `LINE#ID` tags from `read` output.
+Applies precise, surgical file edits by referencing `LINE#ID` tags from `read` output. Each tag uniquely identifies a line, so edits remain stable even when lines shift.
 
 <workflow>
-1. You **SHOULD** issue a `read` call before editing if you have no tagged context for a file.
-2. You **MUST** pick the smallest operation per change site.
-3. You **MUST** submit one `edit` call per file with all operations, think your changes through before submitting.
+Follow these steps in order for every edit:
+1. You **SHOULD** issue a `read` call before editing to get fresh `LINE#ID` tags. Editing without current tags causes mismatches because other edits or external changes may have shifted line numbers since your last read.
+2. You **MUST** submit one `edit` call per file with all operations. Multiple calls to the same file require re-reading between each one (tags shift after each edit), so batching avoids wasted round-trips. Think your changes through before submitting.
+3. You **MUST** pick the smallest operation per change site. Each operation should be one logical mutation — a single replace, insert, or delete. Combining unrelated changes into one operation makes errors harder to diagnose and recover from.
 </workflow>
 
 <operations>
 **`path`** — the path to the file to edit.
 **`move`** — if set, move the file to the given path.
 **`delete`** — if true, delete the file.
-**`edits.[n].pos`** — the anchor line. Meaning depends on `op`:
+**`edits[n].pos`** — the anchor line. Meaning depends on `op`:
 - `replace`: start of range (or the single line to replace)
 - `prepend`: insert new lines **before** this line; omit for beginning of file
 - `append`: insert new lines **after** this line; omit for end of file
-**`edits.[n].end`** — range replace only. The last line of the range (inclusive). Omit for single-line replace.
-**`edits.[n].lines`** — the replacement content:
+**`edits[n].end`** — range replace only. The last line of the range (inclusive). Omit for single-line replace.
+**`edits[n].lines`** — the replacement content:
 - `["line1", "line2"]` — replace with these lines (array of strings)
 - `"line1"` — shorthand for `["line1"]` (single-line replace)
 - `[""]` — replace content with a blank line (line preserved, content cleared)
 - `null` or `[]` — **delete** the line(s) entirely
 
-Tags should be referenced from the last `read` output.
-Edits are applied bottom-up, so earlier tags stay valid even when later ops add or remove lines.
+Tags are applied bottom-up: later edits (by position) are applied first, so earlier tags remain valid even when subsequent ops add or remove lines. Tags **MUST** be referenced from the most recent `read` output.
 </operations>
 
 <rules>
-1. **Minimize scope:** You **MUST** use one logical mutation per operation.
-2. **Prefer insertion over neighbor rewrites:** You **SHOULD** anchor on structural boundaries (`}`, `]`, `},`), not interior lines.
-3. **Range end tag (inclusive):** `end` is inclusive and **MUST** point to the final line being replaced.
-   - If `lines` includes a closing boundary token (`}`, `]`, `)`, `);`, `},`), `end` **MUST** include the original boundary line.
-   - You **MUST NOT** set `end` to an interior line and then re-add the boundary token in `lines`; that duplicates the next surviving line.
+1. **Anchor on unique, structural lines.** You **SHOULD** choose anchors like function signatures, class declarations, or distinct statements — lines that appear exactly once. Blank lines, `}`, and `return null;` repeat throughout a file; anchoring on them risks matching the wrong location. When inserting between blocks, anchor on the nearest unique declaration using `prepend` or `append`.
+2. **Prefer insertion over neighbor rewrites.** You **SHOULD** use `prepend`/`append` anchored on a structural boundary (`}`, `]`, `},`) rather than replacing adjacent lines when adding code near existing code. This keeps the edit minimal and avoids accidentally rewriting lines that should stay.
+3. **Include boundary lines in the replaced range.** `end` is inclusive and **MUST** point to the final line being replaced. If your replacement `lines` include a closing token (`}`, `]`, `)`, `);`, `},`), `end` **MUST** include the original closing line. Otherwise the original closer survives and you get a duplicate.
 </rules>
 
 <recovery>
-**Tag mismatch (`>>>`):** You **MUST** retry using fresh tags from the error snippet. If snippet lacks context, or if you repeatedly fail, you **MUST** re-read the file and issue less ambitious edits, i.e. single op.
-**No-op (`identical`):** You **MUST NOT** resubmit. Re-read target lines and adjust the edit.
+Edits can fail in two ways. Here is exactly what to do for each:
+1. **Tag mismatch (`>>>`):** The file changed since your last read, so the tag no longer matches. You **MUST** retry using the fresh tags from the error snippet. If the snippet lacks enough context, or if you fail repeatedly, you **MUST** re-read the entire file and submit a simpler, single-op edit.
+2. **No-op (`identical`):** Your replacement is identical to the existing content — nothing changed. You **MUST NOT** resubmit the same edit. Re-read the target lines to understand what is actually there, then adjust your edit.
 </recovery>
 
 <example name="single-line replace">
@@ -121,6 +120,7 @@ Range — add `end`:
 </example>
 
 <example name="inclusive end avoids duplicate boundary">
+This example demonstrates why `end` must include the original closing line when your replacement also contains that closer.
 ```ts
 {{hlinefull 70 "if (ok) {"}}
 {{hlinefull 71 "  run();"}}
@@ -159,7 +159,6 @@ Good — include original `}` in the replaced range when replacement keeps `}`:
   }]
 }
 ```
-Also apply the same rule to `);`, `],`, and `},` closers: if replacement includes the closer token, `end` must include the original closer line.
 </example>
 
 <example name="insert between sibling declarations">
@@ -191,7 +190,7 @@ Use a trailing `""` to preserve the blank line between top-level sibling declara
 </example>
 
 <example name="disambiguate anchors">
-Blank lines and repeated patterns (`}`, `return null;`) appear many times — never anchor on them when a unique line exists nearby.
+Blank lines and repeated patterns (`}`, `return null;`) appear many times. Always anchor on a unique line nearby instead.
 ```ts
 {{hlinefull 101 "}"}}
 {{hlinefull 102 ""}}
@@ -233,8 +232,8 @@ Good — anchor on the unique declaration line:
 
 <critical>
 - Edit payload: `{ path, edits[] }`. Each entry: `op`, `lines`, optional `pos`/`end`. No extra keys.
-- Every tag **MUST** be copied exactly from fresh tool result as `N#ID`.
-- You **MUST** re-read after each edit call before issuing another on same file.
-- Formatting is a batch operation. You **MUST NOT** use this tool to reformat, reindent, or adjust whitespace — run the project's formatter instead. If the only change is whitespace, it is formatting; do not touch it.
-- `lines` entries **MUST** be literal file content with indentation copied exactly from the `read` output. If the file uses tabs, use `\t` in JSON (a real tab character) — you **MUST NOT** use `\\t` (two characters: backslash + t), which produces the literal string `\t` in the file.
+- Every tag **MUST** be copied exactly from your most recent `read` output as `N#ID`. Stale or mistyped tags cause mismatches.
+- You **MUST** re-read the file after each edit call before issuing another on the same file. Tags shift after every edit, so reusing old tags produces mismatches.
+- You **MUST NOT** use this tool to reformat, reindent, or adjust whitespace — run the project's formatter instead. If the only difference is whitespace, it is formatting; leave it alone.
+- `lines` entries **MUST** be literal file content with indentation copied exactly from the `read` output. If the file uses tabs, use `\t` in JSON (a real tab character). Using `\\t` (backslash + t) writes the literal two-character string `\t` into the file.
 </critical>

package/src/tools/fetch.ts

@@ -429,6 +429,7 @@ async function renderHtmlToText(
 	url: string,
 	html: string,
 	timeout: number,
+	useKagiSummarizer: boolean,
 	userSignal?: AbortSignal,
 ): Promise<{ content: string; ok: boolean; method: string }> {
 	const signal = ptree.combineSignals(userSignal, timeout * 1000);
@@ -440,15 +441,17 @@ async function renderHtmlToText(
 		signal,
 	};
 
-	// Try Kagi Universal Summarizer first (if KAGI_API_KEY is configured)
-	try {
-		const kagiSummary = await summarizeUrlWithKagi(url, { signal });
-		if (kagiSummary && kagiSummary.length > 100 && !isLowQualityOutput(kagiSummary)) {
-			return { content: kagiSummary, ok: true, method: "kagi" };
+	// Try Kagi Universal Summarizer first (if enabled and KAGI_API_KEY is configured)
+	if (useKagiSummarizer) {
+		try {
+			const kagiSummary = await summarizeUrlWithKagi(url, { signal });
+			if (kagiSummary && kagiSummary.length > 100 && !isLowQualityOutput(kagiSummary)) {
+				return { content: kagiSummary, ok: true, method: "kagi" };
+			}
+		} catch {
+			// Kagi failed, continue to next method
+			signal?.throwIfAborted();
 		}
-	} catch {
-		// Kagi failed, continue to next method
-		signal?.throwIfAborted();
 	}
 
 	// Try jina next (reader API)
@@ -564,7 +567,13 @@ async function handleSpecialUrls(url: string, timeout: number, signal?: AbortSig
 /**
  * Main render function implementing the full pipeline
  */
-async function renderUrl(url: string, timeout: number, raw: boolean, signal?: AbortSignal): Promise<RenderResult> {
+async function renderUrl(
+	url: string,
+	timeout: number,
+	raw: boolean,
+	useKagiSummarizer: boolean,
+	signal?: AbortSignal,
+): Promise<RenderResult> {
 	const notes: string[] = [];
 	const fetchedAt = new Date().toISOString();
 	if (signal?.aborted) {
@@ -803,7 +812,7 @@ async function renderUrl(url: string, timeout: number, raw: boolean, signal?: Ab
 		}
 
 		// Step 6: Render HTML with lynx or html2text
-		const htmlResult = await renderHtmlToText(finalUrl, rawContent, timeout, signal);
+		const htmlResult = await renderHtmlToText(finalUrl, rawContent, timeout, useKagiSummarizer, signal);
 		if (!htmlResult.ok) {
 			notes.push("html rendering failed (lynx/html2text unavailable)");
 			const output = finalizeOutput(rawContent);
@@ -926,7 +935,8 @@ export class FetchTool implements AgentTool<typeof fetchSchema, FetchToolDetails
 			throw new ToolAbortError();
 		}
 
-		const result = await renderUrl(url, effectiveTimeout, raw, signal);
+		const useKagiSummarizer = this.session.settings.get("fetch.useKagiSummarizer");
+		const result = await renderUrl(url, effectiveTimeout, raw, useKagiSummarizer, signal);
 		const truncation = truncateHead(result.content, {
 			maxBytes: DEFAULT_MAX_BYTES,
 			maxLines: FETCH_DEFAULT_MAX_LINES,