pi-famulus 0.2.1 → 0.2.2-beta.0

package/README.md

@@ -73,6 +73,7 @@ Run the full test suite and tell me what fails.
 - **One daemon for every shell and monitor**: The daemon is the parent of every shell and monitor task across your pi sessions. If it crashes or is killed with `kill -9`, each task's process group is stopped. Commands that move into a new session with `setsid` escape this.
 - **Shared capacity**: By default, at most 8 subagents run at once across all pi sessions on the machine (`pi-famulus config set max-agents <n>` changes it). The rest wait in a queue. Subagents labelled `work_kind: "test-suite"` or `"test"` are capped at 2 at a time; without a label, a subagent counts as `other`.
 - **Parent and subagent talk**: A subagent asks its parent a question with `contact_supervisor` and waits for the answer. You can answer it yourself with `/reply`. `agent_message` sends messages between parent and subagents.
+- **Cross-session messaging (agent-intercom)**: pi sessions join the local agent-intercom bridge over the same manager connection — no second socket. `SendMessage` / `ListSessions` tools, `/rename` and the `/intercom` session overlay, `@name` completion inserting `<RequestSendMessage … />` markers, a standing cross-session system-prompt section, `<cross-session-message>` deliver envelopes with read receipts, and authoritative busy/idle publication. Peer messages are input, not authority: they never grant consent. If the bridge is disabled (`PI_FAMULUS_NO_INTERCOM`) the feature stays silent; if it is down, pi-famulus says so once and retries every 3 seconds. Absorbed from the agent-intercom pi plugin (upstream baseline 98183fb); an installed legacy plugin is detected and you are asked to remove it.
 - **Inspectable**: In a terminal, `pi-famulus top` is a live dashboard of sessions, subagents, shells and monitors. Open a subagent to read its conversation or a task to read its output, and stop a running shell or monitor from there. `ls`, `show`, `agent` and `events` show what ran, why it ended, and why a notification did or did not arrive.
 - **Tested against real models**: Tool descriptions are graded on real-model runs. The latest matrix (2026-10-08; 12 xAI and OpenAI configurations, 10 scenarios, k=10) recorded 1198 passes and 2 failures, with 6 invalid or errored episodes excluded ([eval/RESULTS.md](https://github.com/Leechael/pi-famulus/blob/main/eval/RESULTS.md)). It predates a later wording change to the `subagent` and wake prompts ([PR #62](https://github.com/Leechael/pi-famulus/pull/62)), which has not been through the full matrix yet.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-famulus",
-  "version": "0.2.1",
+  "version": "0.2.2-beta.0",
   "description": "Keep your main agent's context clean: subagents on cheaper models, long bash in the background, and monitors that wake the agent. One Rust daemon runs the shells.",
   "keywords": [
     "pi-package",
@@ -54,12 +54,12 @@
     "pi-famulus": "./bin/pi-famulus.js"
   },
   "optionalDependencies": {
-    "pi-famulus-linux-x64": "0.2.1",
-    "pi-famulus-linux-arm64": "0.2.1",
-    "pi-famulus-darwin-x64": "0.2.1",
-    "pi-famulus-darwin-arm64": "0.2.1",
-    "pi-famulus-win-x64": "0.2.1",
-    "pi-famulus-win-arm64": "0.2.1"
+    "pi-famulus-linux-x64": "0.2.2-beta.0",
+    "pi-famulus-linux-arm64": "0.2.2-beta.0",
+    "pi-famulus-darwin-x64": "0.2.2-beta.0",
+    "pi-famulus-darwin-arm64": "0.2.2-beta.0",
+    "pi-famulus-win-x64": "0.2.2-beta.0",
+    "pi-famulus-win-arm64": "0.2.2-beta.0"
   },
   "pi": {
     "extensions": [

package/src/index.ts

@@ -28,6 +28,7 @@ import { describeManagerSearch, getFamulusHome, loadConfig, resolveManagerPath,
 import { ensureNativeManagerInstalled } from "./native-manager.js";
 import type { TaskExitInfo } from "./format";
 import { EXTENSION_VERSION, ManagerClient, type ManagerEvent, type TaskRecord } from "./manager-client";
+import { registerIntercom } from "./intercom/intercom";
 import { createMonitorTool, exitEventFromRecord, MonitorRegistry } from "./monitor";
 import { admitAgentChild, reregisterAgentLeases } from "./subagent/admission";
 import { NotifyCenter } from "./notify";
@@ -1284,5 +1285,11 @@ function createFamulusRuntime(retiring?: Promise<unknown>): FamulusRuntime {
     return message ? { message } : undefined;
   });
 
+  // The intercom port (cross-session messaging, absorbed from the
+  // agent-intercom pi plugin) rides the same manager connection. Registered
+  // after the session hooks above so its session_start sees the fresh
+  // client. Hosted children never reach here (child-mode returns early).
+  registerIntercom(pi, { getClient: () => client });
+
   return runtime;
 }