@ctliz/agent-intercom-claude 0.14.1 → 0.15.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ctliz/agent-intercom-claude",
-  "version": "0.14.1",
+  "version": "0.15.0",
   "description": "Claude Code MCP plugin and wakeable worker for local messaging with Pi, Codex, OpenCode, Grok Build, and AGY agents.",
   "license": "AGPL-3.0-or-later",
   "type": "module",

package/skills/claude-intercom/SKILL.md

@@ -29,8 +29,8 @@ proxy-backed Claude profiles; `ccim` safe mode intentionally does not.
 ## Tools
 
 - `intercom_whoami`: show this session's intercom ID, name, cwd, and model.
-- `intercom_team`: show the current orchestrator manager and live same-manager coworkers.
-- `intercom_join`: list, join, or create a named team without tmux (`create: true` joins as manager).
+- `intercom_team({ team? })`: inspect one task team or list all memberships; falls back to managed-team discovery.
+- `intercom_join({ name?, create?, members?, work? })`: list, join, or create an additive task team; the manager adds connected peers in one call.
 - `intercom_status`: connection, active session count, unread messages, pending asks.
 - `intercom_list`: list connected Pi, Codex, and Claude sessions.
 - `intercom_set_summary`: publish a short discoverable status.
@@ -43,8 +43,8 @@ proxy-backed Claude profiles; `ccim` safe mode intentionally does not.
 
 1. Call `intercom_status` or `intercom_whoami` to confirm this session is connected.
 2. Call `intercom_set_summary` with a concise status so peers can discover your role.
-3. If this is an orchestrator-owned coworker, call `intercom_team` to get the manager and sibling targets without searching globally. To form a team without tmux, call `intercom_join({ name: "billing", create: true })` in one session and `intercom_join({ name: "billing" })` in the others. Otherwise use `intercom_list`.
-4. Use `intercom_send` for non-blocking updates and handoffs.
+3. When the user delegates to named peers and this task has no approved team, ask once whether to form a team with you and those peers. Wait for approval. An explicit create/join request is approval; never ask again for an approved task or inbound team message. After approval, discover peers and call `intercom_join({ name: "billing", create: true, members: ["front", "writer"], work: "Current task" })`. Do not ask the user to join each terminal manually. Reuse the approved team for the same task; new tasks may need new teams. Joining preserves all previous memberships and each team's manager/member roles.
+4. Use `intercom_send` for non-blocking updates and handoffs. Include `team` for task messages, especially when multiple teams are shared. Without a shared team, omit `team` for initial ungrouped contact; unrelated memberships do not block contact or silently create teams.
 5. Use `intercom_ask` only when you need the answer before continuing. Assignments, progress/status checkpoints, notifications, and completion reports use `intercom_send`.
 6. Call `intercom_pending` before ending a coordination turn, then answer blocking asks with `intercom_reply`.
 
@@ -75,7 +75,7 @@ intercom_pending({ mark_read: false })
 intercom_reply({ message: "Use GET/PUT/DELETE only, max 3 retries." })
 ```
 
-When multiple asks are pending, select the sender with `to`. If that sender has multiple unresolved asks, select `oldest` or `latest` without using protocol IDs:
+Replies inherit the original message's team, never a mutable current team. Prefer `askId` or `contextId` returned by `intercom_pending` (contextId also selects ordinary messages). Mixed-team pending contexts require explicit selection; `team` cannot override the original. Within one task, `to` plus `oldest`/`latest` also selects an ask:
 
 ```typescript
 intercom_reply({ to: "planner", which: "oldest", message: "Proceed." })

package/types.ts

@@ -64,6 +64,7 @@ export interface Message {
   control?: BossControlEnvelope;
   content: {
     text: string;
+    team?: string;
     attachments?: Attachment[];
   };
 }