@pratikgajjar/pi-recall 0.1.1 → 0.2.2

package/README.md

@@ -8,23 +8,25 @@ It's a thin wrapper over the [`recall`](https://github.com/pratikgajjar/recall)
 
 _The agent calls `recall_search` to find a past conversation, then reads it in full with `recall_transcript` — no copy-paste._
 
-## Prerequisites
-
-Install the `recall` CLI and build its index once:
+## Install
 
 ```bash
-go install github.com/pratikgajjar/recall@latest
-recall index        # one-time, ~1 minute on real data
-recall doctor        # confirm sources are detected
+pi install npm:@pratikgajjar/pi-recall
 ```
 
-## Install
+The prebuilt `recall` binary for your platform ships inside the package, so
+`pi install` / `pi update` keep the extension **and** the binary in lockstep —
+no separate `go install` or `brew`. The extension resolves the binary in this
+order: `--recall-bin` flag -> `RECALL_BIN` env -> bundled binary -> `recall` on `PATH`.
+
+Then build the index once:
 
 ```bash
-pi install npm:@pratikgajjar/pi-recall
+recall index        # one-time, ~1 minute on real data
+recall doctor       # confirm sources are detected
 ```
 
-Or, for local development, drop it in `.pi/extensions/` or load it ad-hoc:
+For local development, load the extension ad-hoc:
 
 ```bash
 pi -e ./packages/pi-recall/src/index.ts
@@ -43,13 +45,18 @@ All tools accept `repo` (pass `"."` for the current project), `source` (`cursor`
 
 ### Navigating large sessions
 
-Some sessions are huge (thousands of messages). `recall_transcript` takes two
-extra params to slice instead of dumping everything:
+Some sessions are huge (thousands of messages). `recall_transcript` takes
+three extra params to slice instead of dumping everything:
 
 - `range` — Python-style slice over the message list: `":100"` first 100,
   `"-50:"` last 50, `"305:315"` window. Negative indices count from the end.
 - `outline` — one line per message: `[N] role: first-line`. A cheap table of
   contents you can scan before slicing in.
+- `role` — comma-separated allowlist: `"user,assistant"` (skip tool noise),
+  `"user"` (just the prompts), `"tool"`. Tool-related labels (`toolResult`,
+  `toolCall`, `function_call`, …) all collapse to `tool`. In long agent loops,
+  ~50% of messages are tool noise; in some, 98% — a 30k-msg session shrinks to
+  ~600 with `role="user"`.
 
 Every rendered message carries its own `## msg N/TOTAL role` header so any
 slice is self-locating. **Default-cap:** if a session has more than 200

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pratikgajjar/pi-recall",
-  "version": "0.1.1",
+  "version": "0.2.2",
   "description": "pi extension: search your past AI chat history (Cursor, Claude Code, Codex, pi) via the recall CLI",
   "type": "module",
   "license": "MIT",
@@ -33,7 +33,8 @@
     "image": "https://raw.githubusercontent.com/pratikgajjar/recall/main/packages/pi-recall/assets/demo.png"
   },
   "files": [
-    "src"
+    "src",
+    "bin"
   ],
   "publishConfig": {
     "access": "public"

package/src/index.ts

@@ -8,11 +8,33 @@
  */
 
 import { execFile } from "node:child_process";
+import { chmodSync, existsSync, statSync } from "node:fs";
 import { homedir } from "node:os";
+import { dirname, join } from "node:path";
+import { fileURLToPath } from "node:url";
 import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
 import { Text } from "@earendil-works/pi-tui";
 import { Type } from "typebox";
 
+// Resolve the prebuilt binary bundled in this package's bin/ directory. The
+// release pipeline drops one binary per platform (recall-<os>-<arch>); we pick
+// the one matching the host. Returns undefined when none is present (e.g. a
+// source checkout), so the caller falls back to `recall` on PATH.
+function resolveBundledBin(): string | undefined {
+  const name = `recall-${process.platform}-${process.arch}`;
+  const binPath = join(dirname(fileURLToPath(import.meta.url)), "..", "bin", name);
+  if (!existsSync(binPath)) return undefined;
+  // npm has historically lost the +x bit on extracted tarball binaries;
+  // restore it best-effort so the first call succeeds.
+  try {
+    const mode = statSync(binPath).mode;
+    if (!(mode & 0o111)) chmodSync(binPath, 0o755);
+  } catch {
+    /* best effort */
+  }
+  return binPath;
+}
+
 const DEFAULT_SEARCH_LIMIT = 15;
 const DEFAULT_SESSIONS_LIMIT = 20;
 const DEFAULT_RELATED_LIMIT = 10;
@@ -89,11 +111,12 @@ export default function recallExtension(pi: ExtensionAPI) {
   }
 
   function resolveBin(): string {
-    return (
-      (pi.getFlag("recall-bin") as string | undefined) ??
-      process.env.RECALL_BIN ??
-      "recall"
-    );
+    // Precedence: explicit flag -> env override -> binary bundled in this
+    // package's bin/ (shipped by the release pipeline) -> `recall` on PATH.
+    const flag = pi.getFlag("recall-bin") as string | undefined;
+    if (flag) return flag;
+    if (process.env.RECALL_BIN) return process.env.RECALL_BIN;
+    return resolveBundledBin() ?? "recall";
   }
 
   function runRecall(args: string[], signal?: AbortSignal): Promise<RunResult> {
@@ -350,6 +373,12 @@ export default function recallExtension(pi: ExtensionAPI) {
           "One line per message ([N] role: first-line). Use to navigate a large session before slicing in with 'range'.",
       }),
     ),
+    role: Type.Optional(
+      Type.String({
+        description:
+          "Comma-separated roles to keep: 'user', 'assistant', 'tool'. Tool-related roles (toolResult, toolCall, function_call, etc.) collapse to 'tool'. Use 'user,assistant' to skip tool noise (~50% of long agent loops are tool messages).",
+      }),
+    ),
   });
 
   // Above this many messages, recall_transcript called without 'range' or
@@ -384,10 +413,11 @@ export default function recallExtension(pi: ExtensionAPI) {
       });
       const cmd = params.session_id ? ["show", params.session_id] : ["last", ...filterArgs];
 
-      // Honor an explicit slice as-is.
-      if (params.range || params.outline) {
+      // Honor an explicit slice as-is (range / outline / role all count).
+      if (params.range || params.outline || params.role) {
         if (params.range) cmd.push("--range", params.range);
         if (params.outline) cmd.push("--outline");
+        if (params.role) cmd.push("--role", params.role);
         const res = await runRecall(cmd, signal);
         if (!res.ok) {
           const msg = res.stderr || res.stdout.trim() || `recall exited with code ${res.code}`;