@ctliz/agent-intercom-pi 0.12.0-connect.6 → 0.12.0-connect.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +32 -4
  2. package/package.json +11 -2
package/README.md CHANGED
@@ -17,7 +17,35 @@
17
17
  | AGY | [`agent-intercom-agy`](https://github.com/ctliz/agent-intercom-agy) |
18
18
  | Fleet lifecycle | [`agent-intercom-orchestrator`](https://github.com/ctliz/agent-intercom-orchestrator) |
19
19
 
20
- Grok Build and AGY use lightweight npm-packaged MCP launchers backed by the Claude MCP runtime. They retain inbound messages for `intercom_pending` polling but do not provide wake-on-message.
20
+ ## Grok Build and AGY support
21
+
22
+ Grok Build and AGY are supported as first-class protocol peers through two dedicated npm packages:
23
+
24
+ | Host | npm package | Installed MCP launcher |
25
+ |---|---|---|
26
+ | Grok Build | [`@ctliz/agent-intercom-grok`](https://www.npmjs.com/package/@ctliz/agent-intercom-grok) | `agent-intercom-grok-mcp` |
27
+ | AGY | [`@ctliz/agent-intercom-agy`](https://www.npmjs.com/package/@ctliz/agent-intercom-agy) | `agent-intercom-agy-mcp` |
28
+
29
+ The host packages depend on `@ctliz/agent-intercom-claude` and load its MCP runtime internally. Users do **not** need to install or place `claude-intercom-mcp` on `PATH` separately. Once connected, Grok and AGY sessions share the same local broker and protocol as Pi, Codex, Claude Code, and OpenCode, and expose all nine MCP operations: `intercom_whoami`, `intercom_list`, `intercom_send`, `intercom_ask`, `intercom_reply`, `intercom_pending`, `intercom_status`, `intercom_team`, and `intercom_set_summary`.
30
+
31
+ Install the host adapter before installing its plugin:
32
+
33
+ ```bash
34
+ npm install -g @ctliz/agent-intercom-grok
35
+ npm install -g @ctliz/agent-intercom-agy
36
+ ```
37
+
38
+ For multi-pane or Auto-Team-style use, the supervisor must give every MCP child a unique literal identity and the same scope as its intended peers:
39
+
40
+ ```text
41
+ AGENT_INTERCOM_SESSION_ID=<unique-pane-or-worker-id>
42
+ AGENT_INTERCOM_SESSION_NAME=<human-readable-name>
43
+ AGENT_INTERCOM_SCOPE_ID=<shared-team-or-workspace-scope>
44
+ ```
45
+
46
+ The plugin manifests intentionally do not contain static session IDs, because sharing one ID across concurrent panes would create identity collisions. `CLAUDE_INTERCOM_SESSION_ID` and `CLAUDE_INTERCOM_NAME` remain higher-priority compatibility aliases.
47
+
48
+ Grok Build and AGY currently provide polling-only MCP integrations. Messages are durably retained, but there is no host-specific wake bridge to inject a new turn. Each active agent should call `intercom_pending` at startup and at natural work boundaries. They can join an existing team and exchange messages with every other adapter, but Agent Intercom Orchestrator does not currently spawn or lifecycle-manage Grok or AGY workers.
21
49
 
22
50
  ## Maintenance & Upstream Provenance
23
51
 
@@ -65,7 +93,7 @@ Each pi session that has `pi-intercom` loaded and enabled connects to a tiny loc
65
93
  ## Install
66
94
 
67
95
  ```bash
68
- pi install git:github.com/ctliz/agent-intercom-pi@v0.12.0-connect.6
96
+ pi install git:github.com/ctliz/agent-intercom-pi@v0.12.0-connect.8
69
97
  ```
70
98
 
71
99
  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.
@@ -75,7 +103,7 @@ Then restart Pi. The extension auto-connects to the broker on startup and regist
75
103
  On a supported Linux host (or WSL with a systemd user manager enabled) you can optionally install the orchestrator Pi plugin, which lets Pi create and safely own persistent Pi, Codex, Claude Code, and OpenCode coworkers. It is not required, and it is not available on macOS:
76
104
 
77
105
  ```bash
78
- pi install git:github.com/ctliz/agent-intercom-orchestrator@v0.12.0-connect.4
106
+ pi install git:github.com/ctliz/agent-intercom-orchestrator@v0.12.0-connect.5
79
107
  ```
80
108
 
81
109
  Restart Pi or run `/reload`, then verify:
@@ -113,7 +141,7 @@ A session becomes intercom-connected when all of these are true:
113
141
 
114
142
  The session list only shows intercom-connected sessions, not every open Pi process on the machine.
115
143
 
116
- If you upgrade pi-intercom or the orchestrator while sessions are already open, run `/reload` in each open Pi session (and restart any companion `coi`, `cci`, or OpenCode adapter). Update the packages by reinstalling the exact release tags with `pi install git:github.com/ctliz/agent-intercom-pi@v0.12.0-connect.6` and, only where Orchestrator is actually installed, `pi install git:github.com/ctliz/agent-intercom-orchestrator@v0.12.0-connect.4`. Extensions are loaded into the running host process, so an existing session cannot adopt new broker/discovery code until it reloads. This is especially important when upgrading from a release that allowed multiple broker processes to form separate session-list "islands": the broker ownership fix prevents new splits, but it cannot move clients that are still running the old code. After every host has reloaded once, they converge on the same broker automatically.
144
+ If you upgrade pi-intercom or the orchestrator while sessions are already open, run `/reload` in each open Pi session (and restart any companion `coi`, `cci`, or OpenCode adapter). Update the packages by reinstalling the exact release tags with `pi install git:github.com/ctliz/agent-intercom-pi@v0.12.0-connect.8` and, only where Orchestrator is actually installed, `pi install git:github.com/ctliz/agent-intercom-orchestrator@v0.12.0-connect.5`. Extensions are loaded into the running host process, so an existing session cannot adopt new broker/discovery code until it reloads. This is especially important when upgrading from a release that allowed multiple broker processes to form separate session-list "islands": the broker ownership fix prevents new splits, but it cannot move clients that are still running the old code. After every host has reloaded once, they converge on the same broker automatically.
117
145
 
118
146
  If `/intercom` still reports no peers, first confirm the other Pi windows have pi-intercom loaded and have also been reloaded. Open Pi processes without the extension, disabled sessions, and sessions using a different `PI_CODING_AGENT_DIR` intentionally do not appear in the same list.
119
147
 
package/package.json CHANGED
@@ -1,6 +1,7 @@
1
1
  {
2
2
  "name": "@ctliz/agent-intercom-pi",
3
- "version": "0.12.0-connect.6",
3
+ "version": "0.12.0-connect.8",
4
+ "description": "Pi coding-agent intercom for local messaging with Codex, Claude Code, OpenCode, Grok Build, and AGY agents.",
4
5
  "license": "AGPL-3.0-or-later",
5
6
  "type": "module",
6
7
  "main": "index.ts",
@@ -33,7 +34,15 @@
33
34
  "typecheck": "tsc --noEmit"
34
35
  },
35
36
  "keywords": [
36
- "pi-package"
37
+ "pi-package",
38
+ "intercom",
39
+ "multi-agent",
40
+ "codex",
41
+ "claude",
42
+ "opencode",
43
+ "grok",
44
+ "grok-build",
45
+ "agy"
37
46
  ],
38
47
  "pi": {
39
48
  "extensions": [