@oh-my-pi/pi-coding-agent 16.1.17 → 16.1.19

package/dist/types/cli/usage-cli.d.ts

@@ -78,4 +78,18 @@ export declare function formatUsageBreakdown(reports: UsageReport[], accounts: U
  * peak-per-bucket sparkline per limit window plus latest/peak percentages.
  */
 export declare function formatUsageHistory(entries: UsageHistoryEntry[], sinceMs: number, nowMs: number, redaction?: Map<string, string>): string;
+/**
+ * Keep only accounts worth a usage row: those whose provider has a usage
+ * provider, so a missing report is a real gap rather than the absence of any
+ * usage concept. Providers with no usage endpoint (web-search keys, local /
+ * keyless servers, inference providers without a usage API) would only ever
+ * render as noise, so they are dropped.
+ *
+ * `hasUsageProvider` is injected (in practice {@link AuthStorage.usageProviderFor})
+ * so custom/broker resolvers stay authoritative — no provider list is duplicated
+ * here. An explicit `--provider` request bypasses the cull, so
+ * `omp usage --provider xai` can still confirm the stored credential has no
+ * usage endpoint.
+ */
+export declare function selectReportableAccounts(accounts: UsageAccountIdentity[], hasUsageProvider: (provider: string) => boolean, explicitProvider?: string): UsageAccountIdentity[];
 export declare function runUsageCommand(cmd: UsageCommandArgs): Promise<void>;

package/dist/types/commands/token.d.ts

@@ -19,6 +19,15 @@ export default class Token extends Command {
             description: string;
             default: boolean;
         };
+        account: import("@oh-my-pi/pi-utils/cli").FlagDescriptor<"integer"> & {
+            char: string;
+            description: string;
+        };
+        list: import("@oh-my-pi/pi-utils/cli").FlagDescriptor<"boolean"> & {
+            char: string;
+            description: string;
+            default: boolean;
+        };
     };
     static examples: string[];
     run(): Promise<void>;

package/dist/types/edit/hashline/filesystem.d.ts

@@ -1,21 +1,3 @@
-/**
- * Coding-agent specific {@link Filesystem} adapter for the hashline patcher.
- *
- * Wires hashline's storage abstraction to the agent runtime:
- *
- * - Section paths are resolved through the plan-mode redirect so a bare
- *   `PLAN.md` lands at the canonical session artifact location.
- * - Reads go through `readEditFileText` (notebook-aware) and the
- *   auto-generated-file guard.
- * - Writes go through `serializeEditFileText` (notebook-aware) and the
- *   LSP writethrough, with FS-scan cache invalidation on success. The
- *   resulting `FileDiagnosticsResult` is captured per-path so the
- *   orchestrator can attach it to the tool result.
- *
- * Construct one per `executeHashlineSingle` call: per-section state
- * (batch request, diagnostics) lives on the instance and isn't safe to
- * share across concurrent edit tools.
- */
 import { Filesystem, type WriteResult } from "@oh-my-pi/hashline";
 import type { FileDiagnosticsResult, WritethroughCallback, WritethroughDeferredHandle } from "../../lsp";
 import type { ToolSession } from "../../tools";
@@ -50,6 +32,7 @@ export declare class HashlineFilesystem extends Filesystem {
     consumeDiagnostics(path: string): FileDiagnosticsResult | undefined;
     resolveAbsolute(relativePath: string): string;
     canonicalPath(relativePath: string): string;
+    allowTagPathRecovery(authoredPath: string, resolvedPath: string): boolean;
     readText(relativePath: string): Promise<string>;
     preflightWrite(relativePath: string): Promise<void>;
     writeText(relativePath: string, content: string): Promise<WriteResult>;

package/dist/types/extensibility/plugins/legacy-pi-bundled-keys.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Canonical keys served by the `omp-legacy-pi-bundled:` virtual namespace.
+ * Mirrors `Object.keys(BUNDLED_PI_REGISTRY)` from
+ * `legacy-pi-bundled-keys.ts`'s sibling registry file. `legacy-pi-compat.ts`
+ * statically imports this set to seed `LEGACY_PI_PACKAGE_ROOT_OVERRIDES` in
+ * compiled-binary mode without dragging the heavy registry's transitive
+ * graph into dev/test runs (the registry itself stays behind a dynamic
+ * import — see `ensureBundledRegistryLoaded` in `legacy-pi-compat.ts`).
+ */
+export declare const BUNDLED_PI_REGISTRY_KEYS: ReadonlySet<string>;

package/dist/types/extensibility/plugins/legacy-pi-bundled-registry.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Canonical specifier → live module namespace. Keys MUST match the right-hand
+ * side of `bundledRegistryVirtualSpecifier(...)` calls in
+ * `legacy-pi-compat.ts`; the synthesizer enumerates each namespace's own
+ * enumerable exports at extension load time. The companion
+ * `legacy-pi-bundled-keys.ts` mirrors `Object.keys(BUNDLED_PI_REGISTRY)` and
+ * is statically imported by `legacy-pi-compat.ts` to seed the override map
+ * without paying the cascade above.
+ */
+export declare const BUNDLED_PI_REGISTRY: Readonly<Record<string, Readonly<Record<string, unknown>>>>;

package/dist/types/extensibility/plugins/legacy-pi-compat.d.ts

@@ -1,26 +1,16 @@
 import * as path from "node:path";
 /**
- * Compute the bunfs package root from the compiled binary's `import.meta.dir`
- * (or any stand-in supplied by tests). Bun compiled binaries report one of:
- *
- * - the bunfs mount root itself — `/$bunfs/root` or `<drive>:\~BUN\root` (Bun
- *   1.2.x and early 1.3.x). Append `packages` for the canonical layout.
- * - the bunfs mount root followed by the binary's basename — `//root/<bin>`
- *   on POSIX or `<drive>:\~BUN\root\<bin>.exe` on Windows (observed on Bun
- *   1.3.14 with the cross-compiled `omp-darwin-arm64` release asset — issue
- *   #3329). The trailing segment is stripped so the result still lands on
- *   `<root>/packages`.
- * - the module's own source directory if a future Bun release switches to
- *   module-specific `import.meta.dir` values:
- *   `<bunfs>/packages/coding-agent/src/extensibility/plugins`.
- * The bunfs-root-with-binary branch slices the original `metaDir`, and
- * `bunfsPath` uses a matching double-slash-preserving join, so the bunfs-native
- * prefix is preserved verbatim — `path.posix.join` collapses `//root` to
- * `/root`, but Bun's bunfs lookup is keyed on the exact `//root` form.
- *
- * Exported for tests; production callers use `BUNFS_PACKAGE_ROOT` below.
+ * Test seam: builds the synthetic ES module source for a virtual specifier
+ * against an explicit registry. Pure (no globalThis read); the emitted source
+ * still routes runtime lookups through `globalThis[BUNDLED_REGISTRY_GLOBAL]`.
+ */
+export declare function __synthesizeLegacyPiBundledSourceWithRegistry(registryKey: string, registry: Readonly<Record<string, Readonly<Record<string, unknown>>>>): string;
+/**
+ * Test seam: returns the globalThis key the synthetic loader reads from. Tests
+ * assert that the emitted source addresses the exact stash key the install
+ * function writes to, so a rename can't break extension loads silently.
  */
-export declare function __computeBunfsPackageRoot(metaDir: string, pathImpl?: typeof path): string;
+export declare function __getLegacyPiBundledRegistryGlobal(): string;
 /**
  * Compute the package root for the npm prebuilt `dist/cli.js` bundle.
  *
@@ -31,20 +21,46 @@ export declare function __computeBunfsPackageRoot(metaDir: string, pathImpl?: ty
  */
 export declare function __computeBundledSelfPackageRoot(metaDir: string, pathImpl?: typeof path): string;
 /**
- * Join a computed bunfs package root with descendants without collapsing
- * Bun's POSIX `//root` mount prefix.
+ * Resolve the path the TypeBox compatibility shim ships at, then drop it when
+ * the source file is missing.
  *
- * Exported for tests; production callers use `bunfsPath` below.
+ * In compiled-binary mode the shim is served through the
+ * `omp-legacy-pi-bundled:` virtual namespace (issue #3423) — bunfs paths are
+ * unreachable on Bun 1.3.14+, so the virtual specifier is always available and
+ * needs no filesystem probe. In dev / source-link / installed-package mode the
+ * shim is an on-disk source file; validation mirrors
+ * `__validateLegacyPiPackageRootOverrides` (#2168): if the computed candidate
+ * doesn't exist (e.g. an install that dropped the source — issue #3414),
+ * `resolveTypeBoxSpecifier` returns `undefined` and
+ * `rewriteLegacyExtensionSource` leaves bare `typebox` / `@sinclair/typebox`
+ * specifiers alone, so Bun falls through to native resolution against the
+ * extension's own `node_modules`.
+ *
+ * Exported for tests; production callers use `TYPEBOX_SHIM_PATH`.
  */
-export declare function __joinBunfsPath(root: string, segments: readonly string[], pathImpl?: typeof path): string;
+export declare function __resolveTypeBoxShimPath(isCompiled: boolean, sourcePath: string, pathExistsSync?: (p: string) => boolean): string | null;
 /**
- * Drop overrides whose targets are missing on disk so they can fall through to
- * the canonical-resolution path. Exported for the test seam in #2168.
+ * Drop overrides whose filesystem targets are missing so they can fall
+ * through to the canonical-resolution path. Virtual `omp-legacy-pi-bundled:`
+ * entries always pass — the bundled registry is the source of truth in
+ * compiled-binary mode where bunfs paths are unreachable (issue #3423).
  *
- * `pathExistsSync` defaults to `fs.existsSync`; the tests inject a stub to
+ * `pathExistsSync` defaults to `fs.existsSync`; tests inject a stub to
  * simulate the missing-entrypoint failure mode without touching the real FS.
  */
 export declare function __validateLegacyPiPackageRootOverrides(candidates: Record<string, string>, pathExistsSync?: (p: string) => boolean): Record<string, string>;
+/**
+ * Compute the override map keyed by every canonical specifier the host serves
+ * directly: the pi-ai / pi-coding-agent roots (compat shims that re-attach
+ * legacy helpers) plus, in compiled-binary mode, every other canonical pi-*
+ * package root AND every non-wildcard subpath registered in the bundled
+ * registry (see `legacy-pi-bundled-keys.ts`). Subpath coverage is what stops
+ * `@(scope)/pi-ai/oauth` and friends from falling through to the extension's
+ * own — possibly absent — peer install when bunfs filesystem walks fail
+ * (issue #3442 follow-up to #3423). Exported as a test seam so the
+ * compiled-binary branch is verifiable from dev tests.
+ */
+export declare function __buildLegacyPiPackageRootOverrides(isCompiled: boolean): Record<string, string>;
 /**
  * Load a legacy Pi extension module from its real on-disk location.
  *

package/dist/types/internal-urls/skill-protocol.d.ts

@@ -1,4 +1,4 @@
-import type { InternalResource, InternalUrl, ProtocolHandler, UrlCompletion } from "./types";
+import type { InternalResource, InternalUrl, ProtocolHandler, ResolveContext, UrlCompletion } from "./types";
 /**
  * Validate that a path is safe (no traversal, no absolute paths).
  */
@@ -9,6 +9,6 @@ export declare function validateRelativePath(relativePath: string): void;
 export declare class SkillProtocolHandler implements ProtocolHandler {
     readonly scheme = "skill";
     readonly immutable = true;
-    resolve(url: InternalUrl): Promise<InternalResource>;
+    resolve(url: InternalUrl, context?: ResolveContext): Promise<InternalResource>;
     complete(): Promise<UrlCompletion[]>;
 }

package/dist/types/internal-urls/types.d.ts

@@ -4,6 +4,7 @@
  * Internal URLs (`agent://`, `artifact://`, `history://`, `issue://`, `local://`, `mcp://`, `memory://`, `omp://`, `pr://`, `rule://`, `skill://`, and `vault://`) are resolved by tools like read,
  * providing access to agent outputs and server resources without exposing filesystem paths.
  */
+import type { Skill } from "../extensibility/skills";
 import type { LocalProtocolOptions } from "./local-protocol";
 /**
  * Raw resource payload returned by protocol handlers. The `immutable` flag is
@@ -85,6 +86,8 @@ export interface ResolveContext {
      * [#1608](https://github.com/can1357/oh-my-pi/issues/1608).
      */
     localProtocolOptions?: LocalProtocolOptions;
+    /** Calling session's loaded skills. Prefer this over process-global skill state. */
+    skills?: readonly Skill[];
 }
 /**
  * Caller context for write operations dispatched to host-owned URI handlers.

package/dist/types/modes/components/custom-editor.d.ts

@@ -87,8 +87,6 @@ export declare class CustomEditor extends Editor {
     onPasteImage?: () => Promise<boolean>;
     /** Called when a bracketed paste contains one or more image-file paths. */
     onPasteImagePath?: (path: string) => void | Promise<void>;
-    /** Called when a bracketed paste contains one or more non-image file paths. */
-    onPasteFilePath?: (path: string) => void | Promise<void>;
     /** Called when the configured raw text-paste shortcut is pressed. */
     onPasteTextRaw?: () => void;
     /** Called when the configured dequeue shortcut is pressed. */

package/dist/types/modes/components/extensions/extension-dashboard.d.ts

@@ -1,19 +1,29 @@
 /**
- * ExtensionDashboard - Tabbed layout for the Extension Control Center.
+ * ExtensionDashboard - Fullscreen alternate-screen control center for extensions.
  *
- * Layout:
- * - Top: Horizontal tab bar for provider selection
- * - Body: 2-column grid (inventory list | preview panel)
+ * Chrome mirrors the `/settings` overlay: a titled rounded box, a shared
+ * {@link TabBar} for provider selection, and a two-column body (inventory list |
+ * inspector). Both panes are mouse-aware — wheel scrolls, hover highlights, and
+ * clicks select/activate — routed from a single SGR-mouse handler.
  *
  * Navigation:
- * - TAB/Shift+TAB: Cycle through provider tabs
- * - Up/Down/j/k: Navigate list
- * - Space: Toggle selected item (or master switch)
- * - Esc: Close dashboard (clears search first if active)
+ * - Tab/Shift+Tab or ←/→: switch provider tab
+ * - Up/Down/j/k or wheel: move list selection
+ * - Space/Enter or click: toggle selected item (or provider master switch)
+ * - Wheel over the inspector: scroll the detail pane
+ * - Esc: clear search (if active) then close
  */
-import { Container } from "@oh-my-pi/pi-tui";
+import { type Component, type Tab } from "@oh-my-pi/pi-tui";
 import { Settings } from "../../../config/settings";
-export declare class ExtensionDashboard extends Container {
+import type { ProviderTab } from "./types";
+/**
+ * Map dashboard provider tabs to {@link TabBar} tabs. Empty *enabled* providers
+ * are muted — skipped by keyboard nav and unclickable; disabled providers stay
+ * selectable (with a leading disabled glyph) so their master switch can be
+ * re-enabled from the list. The "all" tab is never muted or marked.
+ */
+export declare function buildTabBarTabs(tabs: ProviderTab[]): Tab[];
+export declare class ExtensionDashboard implements Component {
     #private;
     private readonly cwd;
     private readonly settings;
@@ -22,6 +32,12 @@ export declare class ExtensionDashboard extends Container {
     onRequestRender?: () => void;
     private constructor();
     static create(cwd: string, settings?: Settings | null, terminalHeight?: number): Promise<ExtensionDashboard>;
+    /**
+     * Fullscreen frame: titled top border, the tab row(s), a divider, the
+     * two-column body sized to fill the viewport, a divider, the footer hint, and
+     * the bottom border. Records row geometry for mouse hit-testing.
+     */
     render(width: number): readonly string[];
+    invalidate(): void;
     handleInput(data: string): void;
 }

package/dist/types/modes/components/extensions/extension-list.d.ts

@@ -35,5 +35,18 @@ export declare class ExtensionList implements Component {
     clearSearch(): void;
     invalidate(): void;
     render(width: number): readonly string[];
+    /** Highlight the row under the pointer (null clears). */
+    setHoverIndex(index: number | null): void;
+    /**
+     * Map a 0-based line within this component's render to the absolute list-item
+     * index, or null when the line is the search banner, a padding row, or outside
+     * the visible window. The first two lines are the search banner and a blank
+     * separator; item rows follow, windowed at the current scroll offset.
+     */
+    hitTest(line: number): number | null;
+    /** Wheel notch: move the selection (and the inspector) one row. */
+    handleWheel(delta: -1 | 1): void;
+    /** Click: select the row under the pointer, or activate it when already selected. */
+    handleClick(line: number): void;
     handleInput(data: string): void;
 }

package/dist/types/modes/controllers/input-controller.d.ts

@@ -38,7 +38,6 @@ export declare class InputController {
         abort?: boolean;
         currentText?: string;
     }): number;
-    handleFilePathPaste(filePath: string): Promise<void>;
     handleImagePathPaste(path: string): Promise<void>;
     handleImagePaste(): Promise<boolean>;
     handleClipboardTextRawPaste(): Promise<void>;

package/dist/types/tools/path-utils.d.ts

@@ -1,3 +1,4 @@
+import type { Skill } from "../extensibility/skills";
 import { type LocalProtocolOptions } from "../internal-urls";
 export declare function expandTilde(filePath: string, home?: string): string;
 export declare function expandPath(filePath: string): string;
@@ -189,6 +190,8 @@ export interface ToolScopeOptions {
     signal?: AbortSignal;
     /** Calling session's `local://` root mapping — pins resolutions to the calling session. */
     localProtocolOptions?: LocalProtocolOptions;
+    /** Calling session's loaded skills — lets skill:// resolve without process-global state. */
+    skills?: readonly Skill[];
 }
 export interface ToolScopeResolution {
     searchPath: string;

package/package.json

@@ -1,7 +1,7 @@
 {
 	"type": "module",
 	"name": "@oh-my-pi/pi-coding-agent",
-	"version": "16.1.17",
+	"version": "16.1.19",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"homepage": "https://omp.sh",
 	"author": "Can Boluk",
@@ -48,17 +48,17 @@
 		"@agentclientprotocol/sdk": "0.25.0",
 		"@babel/parser": "^7.29.7",
 		"@mozilla/readability": "^0.6.0",
-		"@oh-my-pi/hashline": "16.1.17",
-		"@oh-my-pi/omp-stats": "16.1.17",
-		"@oh-my-pi/pi-agent-core": "16.1.17",
-		"@oh-my-pi/pi-ai": "16.1.17",
-		"@oh-my-pi/pi-catalog": "16.1.17",
-		"@oh-my-pi/pi-mnemopi": "16.1.17",
-		"@oh-my-pi/pi-natives": "16.1.17",
-		"@oh-my-pi/pi-tui": "16.1.17",
-		"@oh-my-pi/pi-utils": "16.1.17",
-		"@oh-my-pi/pi-wire": "16.1.17",
-		"@oh-my-pi/snapcompact": "16.1.17",
+		"@oh-my-pi/hashline": "16.1.19",
+		"@oh-my-pi/omp-stats": "16.1.19",
+		"@oh-my-pi/pi-agent-core": "16.1.19",
+		"@oh-my-pi/pi-ai": "16.1.19",
+		"@oh-my-pi/pi-catalog": "16.1.19",
+		"@oh-my-pi/pi-mnemopi": "16.1.19",
+		"@oh-my-pi/pi-natives": "16.1.19",
+		"@oh-my-pi/pi-tui": "16.1.19",
+		"@oh-my-pi/pi-utils": "16.1.19",
+		"@oh-my-pi/pi-wire": "16.1.19",
+		"@oh-my-pi/snapcompact": "16.1.19",
 		"@opentelemetry/api": "^1.9.1",
 		"@opentelemetry/context-async-hooks": "^2.7.1",
 		"@opentelemetry/exporter-trace-otlp-proto": "^0.218.0",

package/scripts/build-binary.ts

@@ -51,6 +51,17 @@ async function main(): Promise<void> {
 	try {
 		await runCommand(["bun", "--cwd=../stats", "scripts/generate-client-bundle.ts", "--generate"]);
 		await runCommand(["bun", "scripts/generate-docs-index.ts", "--generate"]);
+		// `legacy-pi-bundled-registry.ts` static-imports
+		// `@oh-my-pi/pi-coding-agent/export/html` (one of pi-coding-agent's
+		// named subpath exports, see scripts/generate-legacy-pi-bundled-registry.ts),
+		// whose source pulls in `tool-views.generated.js`. The root
+		// `package.json` "prepare" lifecycle hook builds that file on
+		// `bun install`, but a clean binary build that skips install hooks
+		// would `bun build --compile` against the registry entry and fail
+		// resolving the missing generated bundle. Rebuilding the tool views
+		// here makes the compile self-contained and matches what `prepack`
+		// does for the npm bundle.
+		await runCommand(["bun", "--cwd=../collab-web", "run", "build:tool-views"]);
 		await runCommand(
 			["bun", "--cwd=../natives", "run", "embed:native"],
 			crossTarget
@@ -58,6 +69,15 @@ async function main(): Promise<void> {
 				: Bun.env,
 		);
 		await runCommand(["bun", "scripts/embed-mupdf-wasm.ts", "--generate"]);
+		// Regenerate the bundled-pi registry + key set before the compile so any
+		// new pi-* subpath export added under `packages/*/package.json` is served
+		// from the host's in-process copy. Without this, `bun build --compile`
+		// would freeze whatever the committed registry happened to enumerate at
+		// the time of the last manual `--generate`, and a new subpath added
+		// since then would crash extension validation with `Cannot find module`
+		// (issue #3442). The generator also normalizes formatting, so the diff
+		// against the committed copy stays clean.
+		await runCommand(["bun", "scripts/generate-legacy-pi-bundled-registry.ts", "--generate"]);
 		try {
 			const buildEnv = shouldAdhocSignDarwinBinary() ? { ...Bun.env, BUN_NO_CODESIGN_MACHO_BINARY: "1" } : Bun.env;
 			await runCommand(
@@ -82,22 +102,15 @@ async function main(): Promise<void> {
 					"--root",
 					".",
 					"./packages/coding-agent/src/cli.ts",
-					// Legacy pi-* extension compat entrypoints served by
-					// `legacy-pi-compat.ts`. These are reached via computed bunfs paths
-					// (which `--compile`'s static analyzer cannot trace), so each must be
-					// listed here to land in bunfs at
-					// `/$bunfs/root/packages/<pkg>/<entry>.js`. The coding-agent's own
-					// `./src/index.ts` is intentionally NOT listed: bun --compile silently
-					// breaks the CLI entry when the same package's barrel appears as an
-					// extra entrypoint (issue #1474), so legacy `pi-coding-agent` imports
-					// resolve through `legacy-pi-coding-agent-shim.ts` instead.
-					"./packages/agent/src/index.ts",
-					"./packages/natives/native/index.js",
-					"./packages/tui/src/index.ts",
-					"./packages/utils/src/index.ts",
-					"./packages/coding-agent/src/extensibility/typebox.ts",
-					"./packages/coding-agent/src/extensibility/legacy-pi-ai-shim.ts",
-					"./packages/coding-agent/src/extensibility/legacy-pi-coding-agent-shim.ts",
+					// Legacy pi-* extension compat surfaces (host packages + shims)
+					// were previously listed as explicit `--compile` entries so the
+					// rewrite path could emit `/$bunfs/root/...` URLs against them.
+					// Bun 1.3.14 made bunfs files unreachable at runtime (issue
+					// #3423), so `legacy-pi-compat.ts` now serves them through a
+					// virtual namespace backed by `legacy-pi-bundled-registry.ts`,
+					// which static-imports each surface — the bundler already
+					// includes them via the main module graph, so no `--compile`
+					// extras are required.
 					"--outfile",
 					`packages/coding-agent/dist/${outName}`,
 				],