@alphacoder-v0/pi-loops 0.22.5 → 0.22.6

package/CHANGELOG.md

@@ -5,6 +5,21 @@ All notable changes to pi-loops are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.22.6] - 2026-10-20
+
+### Fixed
+- **A finished loop run no longer leaves the shared extensions stale.** Every run in one project
+  shares one loaded extension set, and a finished run's `session.dispose()` invalidated the
+  runtime those extensions captured at load time. The restore that was meant to undo it read a
+  flag pi keeps in a closure, so it never did anything: from the second run on, every `pi.*`
+  call from a shared extension threw "This extension ctx is stale", an extension that gates
+  tool calls (pi-permission-system, say) blocked every tool call, and the event-bus listeners
+  the extensions registered at load were gone. The shared runtime is now never invalidated; each
+  run's own ExtensionRunner still is. The cost: a listener an extension adds inside a per-run
+  handler is kept for the life of the host. `test/sdk-runner.test.ts`: *a finished run does not
+  leave the shared extensions stale for the next run*. [#81](https://github.com/alphacoder-v0/pi-loops/pull/81)
+  by [@advaitpaliwal](https://github.com/advaitpaliwal).
+
 ## [0.22.5] - 2026-09-28
 
 ### Changed

package/README.md

@@ -38,7 +38,7 @@ the first sign of credentials that do not work should not be an empty inbox tomo
 
 ```bash
 pi install npm:@alphacoder-v0/pi-loops                      # from npm, following new releases
-pi install git:github.com/alphacoder-v0/pi-loops@v0.22.5    # or from GitHub, at a pinned tag
+pi install git:github.com/alphacoder-v0/pi-loops@v0.22.6    # or from GitHub, at a pinned tag
 pi install /path/to/pi-loops                                # or a local checkout — `pi install .` in this repo
 pi -e /path/to/pi-loops                                     # or none of them: try it for one run, installing nothing
 ```

package/README.zh-CN.md

@@ -45,7 +45,7 @@ pi-loops 自己没有任何运行时依赖。
 
 ```bash
 pi install npm:@alphacoder-v0/pi-loops                      # 从 npm 装，跟着新版本走
-pi install git:github.com/alphacoder-v0/pi-loops@v0.22.5    # 或者从 GitHub 装，钉住一个 tag
+pi install git:github.com/alphacoder-v0/pi-loops@v0.22.6    # 或者从 GitHub 装，钉住一个 tag
 pi install /path/to/pi-loops                                # 或者本地检出；本仓库里就是 pi install .
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alphacoder-v0/pi-loops",
-  "version": "0.22.5",
+  "version": "0.22.6",
   "description": "An automation layer for pi: cron + stateful loops with a triage inbox, maker/checker verification, dynamic triggers, MCP notifications and tools, lifecycle hooks, session archives. A non-invasive pi extension.",
   "type": "module",
   "license": "MIT",

package/src/sdk-runner.ts

@@ -111,15 +111,12 @@ export function subSessionResources(req: Pick<SubagentRequest, "cwd">, deps: Pic
 			// staleness, which is what that message is really about, is untouched. The cost is that
 			// a `pi.*` action between runs reaches the most recently created session instead of
 			// throwing; pi rebinds those to the live session on the next run (`runner.js:160-175`).
-			// Only the staleness half is neutralised: the same call also runs pi's event-bus
-			// unsubscribers, and dropping those would leak every subscription a shared extension made,
-			// run after run, in a host that lives for days.
-			const invalidate = base.runtime.invalidate.bind(base.runtime);
-			base.runtime.invalidate = (message?: string) => {
-				const before = (base.runtime as any).staleMessage;
-				invalidate(message);
-				(base.runtime as any).staleMessage = before;
-			};
+			// pi keeps the runtime's stale flag in a closure (`createExtensionRuntime`'s `state`, dist/core/extensions/
+			// loader.js), not on the runtime object, so it cannot be read back and restored after `invalidate()`.
+			// And `invalidate()` also unsubscribes every event-bus listener the shared extensions made when they
+			// loaded, which the next run needs (pi-mcp-adapter's runtime tool calls, say). The shared runtime lives
+			// as long as this loaded set, so it is never invalidated; each run's own ExtensionRunner still is.
+			base.runtime.invalidate = () => {};
 			return { ...base, extensions: [...base.extensions.filter((e) => !isInsideDir(ownDir, e.resolvedPath) && !isInsideDir(ownDir, e.path)), subagentGuardExtension(deps.log, deps.allowCommands?.() ?? [])] };
 		},
 	});