@ctliz/agent-intercom-pi 0.14.0 → 0.14.3

package/README.md

@@ -17,9 +17,9 @@
 | AGY | [`agent-intercom-agy`](https://github.com/ctliz/agent-intercom-agy) |
 | Fleet lifecycle | [`agent-intercom-orchestrator`](https://github.com/ctliz/agent-intercom-orchestrator) |
 
-## Pi 1.0 compatibility and codemode
+## Pi 1.1 compatibility and codemode
 
-Version 0.14.0 is tested with Pi 1.0.0. The preceding 0.13.0 release was tested with Pi 0.99.1. The development test baseline now uses Pi 1.0.0; host-provided Pi modules remain peer dependencies, not runtime dependencies. The existing protocol v4 broker, durable queues, acknowledgements, and cross-harness routing are unchanged.
+Version 0.14.3 is tested with Pi 1.1.0. Version 0.14.0 was tested with Pi 1.0.0, and 0.13.0 with Pi 0.99.1. The development test baseline now uses Pi 1.1.0; host-provided Pi modules remain peer dependencies, not runtime dependencies. The existing protocol v4 broker, durable queues, acknowledgements, and cross-harness routing are unchanged.
 
 Pi 1.0 defaults to fullscreen; set `tuiMode` to `"regular"` or launch with `--tui-mode regular` to retain terminal scrollback. Codemode's shorter declarations preserve Intercom's structured `{ ok, text, data }` results and team guidelines. To check tool existence in a script, use `"intercom_send" in tools`, not `typeof tools.intercom_send`, because unknown members now throw. Restart existing Pi processes to use a newly installed Pi version; `/reload` only reloads resources inside the running version.
 
@@ -41,7 +41,7 @@ Concurrent sends and independent asks are supported; do not create two unresolve
 The package includes an `intercom-send` executable. Install the alias globally for a shell command, or run it without relying on Pi's private installation path:
 
 ```bash
-npm exec --yes --package=@ctliz/pi-intercom@0.14.0 -- intercom-send worker 'Tests passed.'
+npm exec --yes --package=@ctliz/agent-intercom-pi@0.14.3 -- intercom-send worker 'Tests passed.'
 ```
 
 It prints one JSON result with `accepted`, `delivered`, `messageId`, and optional failure `code`/`reason`. Exit status is zero only for acknowledged delivery. It inherits the routing scope, but never inherits `PI_INTERCOM_SESSION_ID` or `AGENT_INTERCOM_SESSION_ID`: every invocation registers an independent sender, leaves running Pi sessions intact, and disconnects after sending. It is send-only; use the session tools for reply-tracked asks.
@@ -163,7 +163,18 @@ Each pi session that has `pi-intercom` loaded and enabled connects to a tiny loc
 ## Install
 
 ```bash
-pi install npm:@ctliz/pi-intercom@0.14.0
+pi install npm:@ctliz/agent-intercom-pi
+```
+
+Starting with 0.14.3, `@ctliz/agent-intercom-pi` is the only npm release name. The legacy `@ctliz/pi-intercom` alias receives no new versions; its published history remains available. The 0.14.2 rename candidate was not published to npm. The GitHub repository and existing Git sources remain unchanged.
+
+Existing `@ctliz/agent-intercom-pi` users do not need to switch packages. Update with `pi update npm:@ctliz/agent-intercom-pi`, then run `/reload` in open Pi sessions. If the configured source is pinned to a version, reinstall the unpinned source above to receive future update notifications.
+
+If you installed the legacy alias, remove it before installing the supported name to avoid loading the same extension twice:
+
+```bash
+pi remove npm:@ctliz/pi-intercom
+pi install npm:@ctliz/agent-intercom-pi
 ```
 
 If you are coming from `connect.1`, read [Upgrading from `connect.1`](#upgrading-from-connect1-to-connect2) first — the package namespace changed and the two versions must not be installed side by side.
@@ -789,7 +800,7 @@ Custom broker commands are trusted local configuration: anyone who can edit this
 }
 ```
 
-Pi-intercom publishes live session status automatically. Sessions register as `idle`, switch to `thinking` while the agent is running, show `tool:<name>` during tool execution, and return to `idle` on agent completion. If `status` is set in config, it is appended as context instead of replacing the lifecycle status.
+Pi-intercom publishes live session status automatically. Sessions register as `idle`, switch to `thinking` while the agent is running, and show `tool:<name>` during tool execution. They remain busy through automatic retries, compaction, and queued continuations until `agent_settled`. Normal settlement returns to `idle`; on Pi 1.1.0 or newer, `aborted: true` shows `cancelled` until the next run or session start. Older hosts without the `aborted` field continue to show `idle` after settlement. If `status` is set in config, it is appended as context instead of replacing the lifecycle status.
 
 By default, runtime state and config live under `~/.pi/agent/intercom`. If Pi is launched with `PI_CODING_AGENT_DIR`, pi-intercom uses `$PI_CODING_AGENT_DIR/intercom` instead, including `config.json`, broker PID/lock files, sockets, durable inboxes/outboxes, ask state, and launcher state. `PI_INTERCOM_ASK_WAIT_MS` controls the foreground ask wait (30 seconds by default); `PI_INTERCOM_ASK_TIMEOUT_MS` controls how long a deferred ask remains replyable (10 minutes by default).
 
@@ -916,7 +927,7 @@ Use pi-messenger for multi-agent swarms working on a shared task. Use pi-interco
 
 The `connect.1` tags, source commits, and published release assets are immutable and are not modified by this migration. Release notes may carry an explicit erratum, which corrects the description only and never moves a tag or replaces an asset.
 
-These packages are not published on the npm registry yet; install from the GitHub tags shown above.
+The historical `connect.*` Git tags shown above remain available. For current Pi installations, use the npm package in [Install](#install).
 
 ## Limitations
 
@@ -939,10 +950,9 @@ git tag -a vX.Y.Z -m "vX.Y.Z"
 git push origin vX.Y.Z
 ```
 
-The release workflow verifies that the tag points into `main`, runs typecheck and
-tests, publishes the public npm package with trusted OIDC provenance, and creates
-the GitHub Release. Existing npm versions and GitHub Releases are skipped safely
-when a workflow is rerun.
+The release workflow verifies that the tag points into `main` and the manifest name is `@ctliz/agent-intercom-pi`, runs typecheck and tests, publishes that one npm package with trusted OIDC provenance, and creates the GitHub Release. It does not publish or rewrite a second alias. Existing npm versions and GitHub Releases are skipped safely when a workflow is rerun.
+
+The npm trusted publisher is configured on **`@ctliz/agent-intercom-pi`** for GitHub owner `ctliz`, repository `agent-intercom-pi`, workflow filename `release.yml`, with no environment name (this workflow does not use one). Authorization is package-specific. Changing this account-side setting requires npm package-owner access; a repository commit alone cannot grant it. The workflow uses OIDC without a placeholder registry token.
 
 ## License
 

package/index.ts

@@ -721,6 +721,7 @@ export default function piIntercomExtension(pi: ExtensionAPI) {
   let runtimeStarted = false;
   let runtimeGeneration = 0;
   let agentRunning = false;
+  let lastRunAborted = false;
   const activeTools = new Map<string, string>();
   const replyTracker = new ReplyTracker();
   const registeredControlTypes = new Set<string>();
@@ -848,7 +849,8 @@ export default function piIntercomExtension(pi: ExtensionAPI) {
   function currentStatus(): string {
     const activeToolName = activeTools.values().next().value;
     const busy = agentRunning || getLiveContext()?.isIdle() === false;
-    const lifecycleStatus = activeToolName ? `tool:${activeToolName}` : busy ? "thinking" : "idle";
+    const settledStatus = lastRunAborted ? "cancelled" : "idle";
+    const lifecycleStatus = activeToolName ? `tool:${activeToolName}` : busy ? "thinking" : settledStatus;
     const queueStatus = inboundInbox?.size ? ` · inbox:${inboundInbox.size}` : "";
     const outboxStatus = client?.outboxSize ? ` · outbox:${client.outboxSize}` : "";
     return config.status ? `${lifecycleStatus}${queueStatus}${outboxStatus} · ${config.status}` : `${lifecycleStatus}${queueStatus}${outboxStatus}`;
@@ -1594,6 +1596,7 @@ export default function piIntercomExtension(pi: ExtensionAPI) {
     runtimeInstanceId = randomUUID();
     lastPresenceName = buildPresenceIdentity(pi, currentSessionId).name;
     agentRunning = false;
+    lastRunAborted = false;
     activeTools.clear();
     startNamePoll();
     if (authorizedRecovered.length > 0) scheduleInboundFlush(0);
@@ -1823,6 +1826,7 @@ export default function piIntercomExtension(pi: ExtensionAPI) {
     inboundLastQueuedAt = null;
     controlRegistrationGraceUntil = 0;
     agentRunning = false;
+    lastRunAborted = false;
     activeTools.clear();
     if (client) {
       await client.disconnect(true);
@@ -1844,6 +1848,7 @@ export default function piIntercomExtension(pi: ExtensionAPI) {
       return;
     }
     agentRunning = true;
+    lastRunAborted = false;
     activeTools.clear();
     syncPresenceStatus();
   });
@@ -1864,14 +1869,15 @@ export default function piIntercomExtension(pi: ExtensionAPI) {
   pi.on("agent_end", (_event, ctx) => {
     if (!getLiveContext(ctx)) return;
     replyTracker.endTurn();
-    agentRunning = !ctx.isIdle();
+    // Only agent_settled ends the busy state; retries and continuations can still follow.
     activeTools.clear();
     syncPresenceStatus();
     scheduleInboundFlush(0);
   });
-  pi.on("agent_settled", (_event, ctx) => {
+  pi.on("agent_settled", (event, ctx) => {
     if (!getLiveContext(ctx)) return;
     agentRunning = false;
+    lastRunAborted = event.aborted === true;
     activeTools.clear();
     syncPresenceStatus();
     scheduleInboundFlush(0);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ctliz/agent-intercom-pi",
-  "version": "0.14.0",
+  "version": "0.14.3",
   "description": "Pi coding-agent intercom for local messaging with Codex, Claude Code, OpenCode, Grok Build, and AGY agents.",
   "license": "AGPL-3.0-or-later",
   "type": "module",
@@ -67,9 +67,9 @@
     "typebox": "*"
   },
   "devDependencies": {
-    "@earendil-works/pi-ai": "^1.0.0",
-    "@earendil-works/pi-coding-agent": "^1.0.0",
-    "@earendil-works/pi-tui": "^1.0.0",
+    "@earendil-works/pi-ai": "^1.1.0",
+    "@earendil-works/pi-coding-agent": "^1.1.0",
+    "@earendil-works/pi-tui": "^1.1.0",
     "@types/node": "^22.15.0",
     "typebox": "*",
     "typescript": "^5.9.3"