@alphacoder-v0/pi-loops 0.22.5 → 0.22.7

package/CHANGELOG.md

@@ -5,6 +5,41 @@ All notable changes to pi-loops are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.22.7] - 2026-10-28
+
+### Changed
+- **Both READMEs install with one line you can paste.** The install block held the npm command, a
+  GitHub command pinned to the current tag, a local checkout and `pi -e`. The pinned tag had to
+  change with every release, and the extra lines kept the block from being pasted as it is. The
+  block is now `pi install npm:@alphacoder-v0/pi-loops`; the text below it gives the checkout
+  routes to people who work on the code.
+
+### Fixed
+- **The browser's thinking picker offers `max`.** Its fallback list, and the options in the page
+  before the script replaces them, was a copy of the thinking levels kept by hand. It had lost
+  `max`, which pi-loops accepts. It now offers every level pi accepts, and a test keeps the fallback
+  equal to `THINKING_LEVELS`. [#84](https://github.com/alphacoder-v0/pi-loops/pull/84)
+- **In the browser, a reply shares one line with the work before it.** A turn with work took two
+  header lines: the work row's summary (`6 steps · thinking, read, bash`) and the reply's
+  `ASSISTANT` label with its copy button. The label and the copy button are now in the work row's
+  summary, and the reply no longer ends the stretch, so steps after the answer join the same row.
+  A reply with no work keeps its own label row. [#86](https://github.com/alphacoder-v0/pi-loops/pull/86)
+
+## [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

@@ -37,15 +37,13 @@ one message, make sure you get an answer. pi-loops runs sub-agents while you are
 the first sign of credentials that do not work should not be an empty inbox tomorrow morning.
 
 ```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 /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
+pi install npm:@alphacoder-v0/pi-loops
 ```
 
-Install one of them, not two. Two copies register the same tools, and pi refuses to load the
-second — `Tool "cron_create" conflicts with …`, and it exits. If you are working on the code, the
-checkout is the one to keep.
+Working on the code? Install your checkout instead — `pi install .` in this repo — or try it for
+one run with `pi -e .`, which installs nothing. Keep one copy, not two: two copies register the
+same tools, and pi refuses to load the second — `Tool "cron_create" conflicts with …`, and it
+exits.
 
 Then restart pi, and that is the whole install: `/cron`, `/inbox`, `/triggers` and `/goal` are
 registered by the extension itself, so they work with nothing on your `PATH` and no launcher. The

package/README.zh-CN.md

@@ -44,12 +44,10 @@ pi-loops 自己没有任何运行时依赖。
 ### 2. 装上
 
 ```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 /path/to/pi-loops                                # 或者本地检出；本仓库里就是 pi install .
+pi install npm:@alphacoder-v0/pi-loops
 ```
 
-**几种装法挑一种，不要装两份。** 两份副本注册同名工具，pi 会拒绝加载第二份并直接退出（`Tool "cron_create" conflicts with …`）。如果你在改这份代码，留本地检出那份。
+如果你在改这份代码，就改装本地检出：在本仓库里 `pi install .`。**只装一份，不要装两份。** 两份副本注册同名工具，pi 会拒绝加载第二份并直接退出（`Tool "cron_create" conflicts with …`）。
 
 重启 pi，装到这里就够了——那四个斜杠命令现在就能用。下面这段只跟 `pi-loops` 这个命令有关：浏览器窗口和几个 shell 子命令靠它，不要浏览器窗口可以先跳过。
 

package/docs/web-ui-parity.md

@@ -67,9 +67,12 @@ weaker, and worth converting whenever one of them breaks.
 - [x] Assistant text, thinking, tool calls, tool results, errors, and the end of a turn.
 - [x] The conversation is what the conversation is for. A whole stretch of work — thinking and tool
       calls, interleaved as they arrive — is **one** row, closed: what is happening while it happens,
-      what happened afterwards. One button in the header opens or closes every one of them.
+      what happened afterwards. The reply that follows it shares the row — its label and copy
+      button sit in the summary, so "ASSISTANT" and "6 steps · thinking, bash" are one line, not
+      two — and the stretch continues past the reply rather than being cut in two. One button in
+      the header opens or closes every one of them.
       `test/web-page.test.ts`: *a stretch of work is one row, and one button opens every one of
-      them*.
+      them*, *a reply without work keeps its own label row*.
 - [x] Replies render as Markdown — headings, lists, quotes, rules, tables, inline code, fenced
       code, and http(s) links. Everything is escaped first: a reply is not trusted input, and a
       tool result quoted inside one is whatever some web page said. `test/web-page.test.ts`: *a
@@ -114,7 +117,7 @@ weaker, and worth converting whenever one of them breaks.
       `test/web-page.test.ts`: *a reply can show a picture*, *an image that came back from a tool*.
 - [x] A tool call and what it returned are one block, and it starts closed. A tool that prints two
       hundred lines must not push the conversation off the screen to do it.
-      `test/web-page.test.ts`: *a run of tool calls is one row, and the next run is a new one*.
+      `test/web-page.test.ts`: *a run of tool calls is one row, and the reply shares it*.
 - [x] You are on the right in a bubble and the model is full-width prose: the shape says who is
       speaking before a word is read. Status lines are small, monospace and quiet — context, not
       conversation.
@@ -237,7 +240,9 @@ weaker, and worth converting whenever one of them breaks.
       heard of it*.
 - [x] The thinking levels offered are the ones this model has — asked for per model rather than
       drawn from one fixed list, because picking a level a model does not implement does nothing at
-      all.
+      all. When the per-model list is unknown, the picker offers the whole menu pi accepts rather
+      than a list of its own.
+      `test/web-page.test.ts`: *the thinking-level picker offers every level pi knows, not a list of its own*.
 - [x] Attaching an image is refused, with the reason, by a model that cannot see one.
 - [x] Cost and token counts.
 - [x] Compact, undo (fork from your last message), find across the whole session including

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alphacoder-v0/pi-loops",
-  "version": "0.22.5",
+  "version": "0.22.7",
   "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?.() ?? [])] };
 		},
 	});

package/src/web.mjs

@@ -2222,6 +2222,12 @@ details.work{border:1px solid transparent;border-radius:10px;overflow:hidden}
 details.work[open]{border-color:var(--line);background:var(--side)}
 details.work:not([open])>summary{padding-left:0;padding-right:0}
 details.work>summary{cursor:pointer;display:flex;align-items:center;gap:8px;padding:7px 11px;font-family:var(--font-mono);font-size:12px;color:var(--muted);list-style:none}
+/* The reply that follows a stretch of work shares its row: the label and the copy button sit in
+   the summary, so "ASSISTANT" and "6 steps · thinking, bash" are one line rather than two. */
+details.work>summary>span.tag{flex:0 0 auto;color:var(--faint);font-size:11px;letter-spacing:.03em;text-transform:uppercase}
+details.work>summary>button{border:0;background:none;color:var(--faint);padding:0 5px;font-size:11px;min-height:0;opacity:0;text-transform:none}
+details.work:hover>summary>button,details.work:focus-within>summary>button{opacity:1}
+@media (pointer:coarse){details.work>summary>button{opacity:.7}}
 details.work>summary::-webkit-details-marker{display:none}
 details.work>summary::before{content:"▸";color:var(--faint);flex:0 0 auto}
 details.work[open]>summary::before{content:"▾"}
@@ -2441,7 +2447,7 @@ dialog menu{display:flex;gap:8px;justify-content:flex-end;padding:0;margin:14px
     <span class="cwd" id="cwd"></span>
     <select id="model" title="Model"></select>
     <select id="thinking" title="Thinking level">
-      <option>off</option><option>minimal</option><option>low</option><option>medium</option><option>high</option><option>xhigh</option>
+      <option>off</option><option>minimal</option><option>low</option><option>medium</option><option>high</option><option>xhigh</option><option>max</option>
     </select>
     <span class="grow">
       <span class="badge" id="queue" hidden></span>
@@ -3116,20 +3122,40 @@ function row(cls, role, text) {
   const el = document.createElement("div");
   el.className = "row " + cls;
   const b = document.createElement("span");
+  // The answer that follows a turn's work shares its row: the label and its copy button go into
+  // the summary, so "ASSISTANT" and "6 steps · thinking, bash" are one line, not two — and the
+  // stretch continues past the answer rather than being cut in two.
+  const shared = role === "assistant" && toolGroup;
   if (role) {
-    const r = document.createElement("div");
-    r.className = "role";
-    const name = document.createElement("span");
-    name.textContent = role;
-    r.append(name);
-    // Only where there is something worth copying: a status line is not.
-    if (cls === "" || cls === "tool" || cls === "user") r.append(copyBtn(() => b.raw ?? b.textContent ?? ""));
-    el.append(r);
+    if (shared) {
+      toolGroup.answerEl = b;
+      if (!toolGroup.roleTag) {
+        const name = document.createElement("span");
+        name.className = "tag";
+        name.textContent = role;
+        const btn = copyBtn(() => {
+          const a = (toolGroup && toolGroup.answerEl) ?? b;
+          return a.raw ?? a.textContent ?? "";
+        });
+        toolGroup.summary.insertBefore(name, toolGroup.what);
+        toolGroup.summary.insertBefore(btn, toolGroup.what);
+        toolGroup.roleTag = name;
+      }
+    } else {
+      const r = document.createElement("div");
+      r.className = "role";
+      const name = document.createElement("span");
+      name.textContent = role;
+      r.append(name);
+      // Only where there is something worth copying: a status line is not.
+      if (cls === "" || cls === "tool" || cls === "user") r.append(copyBtn(() => b.raw ?? b.textContent ?? ""));
+      el.append(r);
+    }
   }
   if (text) b.textContent = plain(text);
   el.append(b);
   clearEmpty();
-  endToolGroup();
+  if (!shared) endToolGroup();
   feed.append(stamp(el));
   scroll();
   return b;
@@ -3174,6 +3200,7 @@ function toolGroupFor() {
   s.append(what);
   d.append(s);
   d.what = what;
+  d.summary = s;
   d.names = [];
   clearEmpty();
   feed.append(stamp(d));
@@ -3759,7 +3786,7 @@ function drawModels(catalog, current) {
 /** Only the levels this model has. A level pi maps to null is a level that does nothing. */
 function drawThinking(levels, current) {
   const picker = $("thinking");
-  const list = (levels && levels.length ? levels : ["off", "minimal", "low", "medium", "high", "xhigh"]).map(String);
+  const list = (levels && levels.length ? levels : ["off", "minimal", "low", "medium", "high", "xhigh", "max"]).map(String);
   if (picker.dataset.levels !== list.join(",")) {
     picker.dataset.levels = list.join(",");
     picker.innerHTML = "";