pi-repl-py 0.2.8 → 0.3.0

package/docs/ARCHITECTURE.md

@@ -57,15 +57,17 @@ That path is stable across updates because it sits outside the package's own dir
 which npm replaces on each update. If `python3` or the network is missing at install time,
 `postinstall` prints a clear notice and the host falls back at runtime.
 
-At spawn, `resolvePythonPath` picks the interpreter in this order:
+At spawn, `resolvePythonPath` uses exactly one interpreter, the install venv:
 
-1. the repo's own `.venv` (development)
-2. a venv in the current directory (per-project)
-3. `~/.pi/agent/pi-repl/venv` (package install)
-4. `$PYTHON`, then `python3` (the fallback)
+1. `~/.pi/agent/pi-repl/venv` (the package install)
+2. `$PYTHON`, then `python3` (only if the install venv is missing)
 
-The first one that exists wins. The tool's prompt tells the model it runs in a project-local
-venv, not the system interpreter, so it does not leak the wrong assumption into commands.
+It deliberately does NOT auto-pick the repo's or current directory's `.venv`: a per-project
+venv is not guaranteed to have `ipykernel`, so preferring it (as earlier versions did) made
+the kernel die from a `ModuleNotFoundError` whenever cwd happened to contain such a venv. The
+kernel therefore always runs in the stable install environment. The kernel starts in the
+session's cwd, falling back to the host's own cwd if that directory no longer exists (a
+deleted project dir), so a stale cwd can never prevent the kernel from coming up.
 
 ## The kernel client
 

package/index.ts

@@ -6,7 +6,7 @@ import type { ExtensionAPI } from "@mariozechner/pi-coding-agent";
 import { Type } from "typebox";
 import { EngineManager } from "./src/engine/index.js";
 import { ExecuteCellComponent, type ExecuteDetails, type ExecuteRenderState } from "./src/extension/render.js";
-import { EngineLifecycle, summarizeNames } from "./src/extension/session-engine.js";
+import { EngineLifecycle } from "./src/extension/session-engine.js";
 import { EXECUTE_DESCRIPTION, buildExecutePromptGuidelines, EXECUTE_PROMPT_SNIPPET } from "./src/extension/tool-meta.js";
 
 const executeSchema = Type.Object({
@@ -87,23 +87,13 @@ export default function (pi: ExtensionAPI) {
 		}
 		// --- active: the whole surface collapses to the one tool ---
 		pi.setActiveTools(["execute"]);
-		// --- revive the previous run; the engine also self-revives if session_start was skipped ---
+		// --- warm the engine (and its revive) in the background; no popup. ---
+		// --- acquire() dedupes, so the first execute awaits this same in-flight boot ---
 		location = { cwd: ctx.cwd, sessionFile: ctx.sessionManager.getSessionFile() ?? undefined };
-		const { restore } = await lifecycle.acquire("startup");
-		if (restore && restore.restored.length > 0) {
-			pi.sendMessage({
-				customType: "pi-repl-restore",
-				content: `Revived ${restore.restored.length} variable(s) from the previous run: ${summarizeNames(restore.restored, 8)}${
-					restore.failed.length > 0
-						? `. Failed: ${summarizeNames(
-								restore.failed.map((f) => f.name),
-								8,
-							)}`
-						: ""
-				}`,
-				display: true,
-			});
-		}
+		void lifecycle.acquire("startup").catch(() => {
+			// --- boot/revive handled on the execute path; swallow so a background warm can never
+			// --- surface an unhandled rejection and the model never needs the restore notice ---
+		});
 	});
 
 	pi.on("session_shutdown", async () => {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-repl-py",
-	"version": "0.2.8",
+	"version": "0.3.0",
 	"type": "module",
 	"description": "A pi extension with a single tool: execute, running a TypeScript host with a persistent Python (ipykernel) evaluator and a user-configurable toolbox of functions.",
 	"keywords": [

package/src/engine/index.ts

@@ -5,21 +5,16 @@
 import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs";
 import { homedir } from "node:os";
 import { dirname, join } from "node:path";
-import { fileURLToPath } from "node:url";
 import { KernelClient } from "./kernel.js";
 
-const GUEST_REL = fileURLToPath(new URL("./kernel.js", import.meta.url));
-
 function installVenvPython(): string {
 	return join(homedir(), ".pi", "agent", "pi-repl", "venv", "bin", "python3");
 }
 
 /** Prefer a venv with ipykernel; else $PYTHON or python3. */
-function resolvePythonPath(cwd: string | undefined): string {
-	const repoVenv = join(dirname(GUEST_REL), "..", "..", ".venv", "bin", "python3");
-	if (existsSync(repoVenv)) return repoVenv;
-	const cwdVenv = cwd ? join(cwd, ".venv", "bin", "python3") : "";
-	if (cwdVenv && existsSync(cwdVenv)) return cwdVenv;
+function resolvePythonPath(_cwd: string | undefined): string {
+	// Only ever use the install venv: a project or repo `.venv` may lack ipykernel and
+	// shadow the good environment, killing the kernel. No auto-picking.
 	const installVenv = installVenvPython();
 	if (existsSync(installVenv)) return installVenv;
 	return process.env.PYTHON ?? "python3";

package/src/engine/kernel.ts

@@ -54,7 +54,14 @@ export interface SnapshotReply {
 // --- boot preload: exec each helper; ls()/help() are gone, discovery is globals() ---
 
 /** Read the helpers dir (same skip rules as the extension's prompt loader). */
-export function readHelperSources(dir?: string): { name: string; source: string }[] {
+/** A directory for the kernel to start in; if the requested cwd is gone, fall back to the
+ * evaluator's own cwd rather than letting spawn() die with ENOENT. A deleted project dir is
+ * a real resume case (pi guards it too) — the kernel must still come up. */
+function resolveCwd(requested?: string): string {
+	if (requested && existsSync(requested)) return requested;
+	return process.cwd();
+}
+function readHelperSources(dir?: string): { name: string; source: string }[] {
 	// --- one fixed dir, resolved like the prompt side (helpers.ts) so both always agree ---
 	const d = dir ?? join(homedir(), ".pi", "agent", "pi-repl", "helpers");
 	if (!existsSync(d)) return [];
@@ -179,7 +186,7 @@ export class KernelClient {
 	static async start(pythonPath: string, opts: KernelOptions = {}): Promise<KernelClient> {
 		const connPath = join(tmpdir(), `pi-repl-kernel-${randomUUID()}.json`);
 		const child = spawn(pythonPath, ["-m", "ipykernel", "-f", connPath, "--no-stdout"], {
-			cwd: opts.cwd,
+			cwd: resolveCwd(opts.cwd),
 			env: { ...process.env, ...(opts.env ?? {}) },
 			stdio: ["ignore", "pipe", "pipe"],
 		});

package/src/extension/session-engine.ts

@@ -3,7 +3,7 @@
 import type { RestoreResult } from "../engine/index.js";
 
 /** Show enough names to orient, then count the rest (a revive can carry hundreds). */
-export function summarizeNames(names: readonly string[], limit: number): string {
+function summarizeNames(names: readonly string[], limit: number): string {
 	if (names.length <= limit) return names.join(", ");
 	return `${names.slice(0, limit).join(", ")} … and ${names.length - limit} more`;
 }