pi-link 0.5.0 → 0.5.1

package/CHANGELOG.md

@@ -6,6 +6,16 @@ This changelog is based on the git history from `2026-03-21` (initial commit) th
 
 ---
 
+## 0.5.1 — 2026-09-22
+
+### Fixed
+
+- **pi-link's tools are callable directly under Oh My Pi.** The three tools are registered with `loadMode: "essential"`, so harnesses that hide extension tools by default, such as Oh My Pi, list them with the other callable tools instead of behind a discovery path. Pi has no such field and ignores it.
+
+- **Peers see a terminal's context usage change after a model switch or tree navigation.** A terminal now republishes its context when its model changes or it moves to another branch of the session tree. Before, an idle terminal kept showing its previous figure until its next run.
+
+---
+
 ## 0.5.0 — 2026-09-16
 
 ### Added

package/README.md

@@ -663,11 +663,13 @@ The extension hooks into Pi's agent lifecycle events:
 - **`tool_execution_end`** → Drops that one call. The display stays `tool:<name>` while other calls remain, moves to the next call when the displayed one ends, and returns to `thinking` after the last one while the agent run continues.
 - **`session_before_compact`** → For a manual compaction, raises the gate that holds inbox delivery. Automatic (threshold/overflow) compaction is left alone: it runs inside the agent run, where Pi already queues and drains steered messages itself.
 - **`session_compact`** → Clears the local compaction gate and force-pushes a `status_update` so peers see the new (post-compaction) context usage immediately.
+- **`model_select`** → Force-pushes a `status_update`: the context window, and so the usage percentage, belongs to the model.
+- **`session_tree`** → Force-pushes a `status_update`: context usage belongs to the active branch.
 - **`session_shutdown`** → Full cleanup via `cleanup()`: closes all sockets, resolves pending promises, and disposes the extension.
 
-The five agent and tool handlers — `agent_start`, `agent_end`, `agent_settled` (when Pi still reports the session idle), `tool_execution_start` and `tool_execution_end` — each recompute the status and hand it to `pushStatus()`, which publishes only when the display identity changed since the last publish: a second concurrent tool starting behind the one already shown is silent, and so is a mutation that leaves a raised compaction gate on display. The session handlers keep the separate paths described in their own bullets, and `session_shutdown` cleans up rather than pushing. `disconnect()` is the only thing that clears the stored baseline, and `pushStatus()` returns immediately while the terminal is disconnected, so handler events in that interval restore nothing; once connected again, either a client's forced `welcome` push or the first of those ordinary handler events restores it. `session_compact` always pushes, whether the identity changed or not — including while a remote request's gate still holds the displayed identity.
+The five agent and tool handlers — `agent_start`, `agent_end`, `agent_settled` (when Pi still reports the session idle), `tool_execution_start` and `tool_execution_end` — each recompute the status and hand it to `pushStatus()`, which publishes only when the display identity changed since the last publish: a second concurrent tool starting behind the one already shown is silent, and so is a mutation that leaves a raised compaction gate on display. The session handlers keep the separate paths described in their own bullets, and `session_shutdown` cleans up rather than pushing. `disconnect()` is the only thing that clears the stored baseline, and `pushStatus()` returns immediately while the terminal is disconnected, so handler events in that interval restore nothing; once connected again, either a client's forced `welcome` push or the first of those ordinary handler events restores it. `session_compact`, `model_select` and `session_tree` always push, whether the identity changed or not — including while a remote request's gate still holds the displayed identity.
 
-Status updates are push-based: each terminal broadcasts changes to the hub, which fans them out. New joiners receive a status snapshot for all terminals in the `welcome` message. Context updates reuse the same status path, including a forced post-compaction update.
+Status updates are push-based: each terminal broadcasts changes to the hub, which fans them out. New joiners receive a status snapshot for all terminals in the `welcome` message. Context updates reuse the same status path, including forced updates after a compaction, a model change and tree navigation.
 
 ### Inbox
 

package/index.ts

@@ -44,6 +44,9 @@ const BATCH_MAX_ITEMS = 20;
 const BATCH_MAX_CHARS = 16_000;
 // Visual rows of an incoming message kept while Pi's global expansion is off.
 const PREVIEW_ROWS = 6;
+// Consumed by harnesses that hide extension tools by default (Oh My Pi);
+// ignored by Pi, whose ToolDefinition has no such field.
+const TOP_LEVEL_TOOL = { loadMode: "essential" } as const;
 
 // ─── Protocol ────────────────────────────────────────────────────────────────
 
@@ -1469,6 +1472,14 @@ export default function (pi: ExtensionAPI) {
     pushStatus(true);
   });
 
+  pi.on("model_select", async () => {
+    pushStatus(true); // the window, and so the usage percentage, belongs to the model
+  });
+
+  pi.on("session_tree", async () => {
+    pushStatus(true); // context usage belongs to the active branch
+  });
+
   pi.on("tool_execution_start", async (event) => {
     const before = statusIdentity(deriveStatus());
     activeTools.set(event.toolCallId, event.toolName);
@@ -1566,6 +1577,7 @@ export default function (pi: ExtensionAPI) {
   // ── Tools ────────────────────────────────────────────────────────────────
 
   pi.registerTool({
+    ...TOP_LEVEL_TOOL,
     name: "link_send",
     label: "Link Send",
     description: [
@@ -1630,6 +1642,7 @@ export default function (pi: ExtensionAPI) {
   });
 
   pi.registerTool({
+    ...TOP_LEVEL_TOOL,
     name: "link_compact",
     label: "Link Compact",
     description: [
@@ -1742,6 +1755,7 @@ export default function (pi: ExtensionAPI) {
   });
 
   pi.registerTool({
+    ...TOP_LEVEL_TOOL,
     name: "link_list",
     label: "Link List",
     description: "List the Pi terminals in your group currently connected to the link.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-link",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "WebSocket-based inter-terminal communication for Pi. Connect multiple Pi terminals over a local link network.",
   "author": "alvivar",
   "license": "MIT",