patchcord 0.2.4 → 0.2.5

package/README.md

@@ -5,8 +5,13 @@ Cross-machine messaging between Claude Code agents.
 ## Install
 
 ```bash
-npm install -g patchcord
-patchcord init
+npx patchcord@latest install
+```
+
+Or with full statusline (model, context%, git branch):
+
+```bash
+npx patchcord@latest install --full
 ```
 
 The plugin provides skills, statusline integration, and turn-end inbox hooks. The actual Patchcord connection comes from the project's `.mcp.json`.
@@ -73,7 +78,7 @@ By default the statusline shows only Patchcord identity and inbox count. In non-
 To also show model, context usage, repo, and git branch:
 
 ```bash
-bash scripts/enable-statusline.sh --full
+npx patchcord@latest install --full
 ```
 
 Without `--full`:

package/codex/SKILL.md

@@ -19,7 +19,7 @@ If there are pending messages, reply to ALL of them IMMEDIATELY. Do not ask the
 ## Sending
 
 1. inbox() — check who's online
-2. send_message("agent_name", "specific question with file paths and context")
+2. send_message("agent_name", "specific question with file paths and context") — or "agent1, agent2" for multiple recipients
 3. wait_for_message() — auto-wait for any response, don't ask human whether to wait
 
 ## Receiving (inbox has messages)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchcord",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "Cross-machine agent messaging for Claude Code and Codex",
   "author": "ppravdin",
   "license": "MIT",

package/skills/inbox/SKILL.md

@@ -6,29 +6,47 @@ description: >
   coordination, or when you receive additionalContext about pending patchcord
   messages.
 ---
-
 # patchcord
 
 9 MCP tools: inbox, send_message, reply, unsend_message, wait_for_message, upload_attachment, get_attachment, relay_url, list_recent_debug.
 
+## CRITICAL: DO THE WORK, NEVER JUST ACKNOWLEDGE
+
+When you receive a message from another agent:
+
+1. **DO THE TASK described in the message FIRST.** Update the file. Write the code. Fix the bug. Create the document. Whatever the message asks — DO IT.
+2. **THEN reply with what you DID.** Not what you plan to do. Not that you received it. What you ACTUALLY DID. File paths, line numbers, concrete changes.
+3. **NEVER reply with only an acknowledgment.** "Got it", "Understood", "Role accepted", "Will do", "Ready" — these are FORBIDDEN as standalone replies. If your reply doesn't describe completed work, you failed.
+
+The user can undo any change in 3 seconds with git. A wrong action costs nothing. A useless ack wastes everyone's time and breaks the workflow.
+
+**If a message contains a spec, update, or instruction → ACT ON IT IMMEDIATELY:**
+- Spec received → update the relevant docs/code NOW, reply with what you changed
+- Bug report received → investigate and fix NOW, reply with the fix
+- Architecture decision received → update the relevant files NOW, reply with what you updated
+- Role assignment received → start doing that role NOW, reply with first actions taken
+
+**If you genuinely cannot act** (missing file access, need credentials, ambiguous target): say SPECIFICALLY what's blocking you. "I need the path to the docs folder" — not "Understood, I'll do it when ready."
+
 ## On session start or when prompted by a hook
 
 Call inbox(). It returns pending inbox (full text of ALL unread messages) and online agents in one call.
-If there are pending messages, reply to ALL of them IMMEDIATELY. Do not ask the human first. Do not explain what you plan to reply. Just reply, then tell the human what you received and what you answered.
+
+If there are pending messages, reply to ALL of them IMMEDIATELY. Do not ask the human first. Do not explain what you plan to reply. Just DO THE WORK described in each message, then reply with what you did, then tell the human what you received and what you did about it.
 
 ## Sending
 
 1. inbox() — read pending mail and recent presence for routing
-2. send_message("agent_name", "specific question with file paths and context")
+2. send_message("agent_name", "specific question with file paths and context") — or "agent1, agent2" for multiple recipients
 3. wait_for_message() — auto-wait for any response, don't ask human whether to wait
 
 ## Receiving (inbox has messages)
 
-1. Read the question from inbox() result
-2. Answer from YOUR project's actual code — reference real files, real lines
-3. reply(message_id, "detailed answer")
+1. Read the message
+2. DO THE WORK described in the message — using YOUR project's actual code, real files, real lines
+3. reply(message_id, "here's what I did: [concrete changes with file paths]")
 4. wait_for_message() — stay responsive for follow-ups
-5. If you can't answer, say so. Don't guess about another agent's code.
+5. If you can't do the work, say specifically what's blocking you. Don't guess about another agent's code.
 
 ## File sharing
 
@@ -53,15 +71,16 @@ Deferred messages survive context compaction — the agent won't forget them.
 
 ## Rules
 
-- Reply IMMEDIATELY. Never ask "want me to reply?" — just reply, then tell the human who wrote and what you answered.
-- Only ask the human BEFORE replying if the request is destructive or requires secrets you don't have.
-- Never ask "want me to wait?" — just wait
-- Never show raw JSON to the human — summarize naturally
+- DO THE WORK FIRST, REPLY SECOND. Never reply before completing the task.
+- Never ask "want me to reply?" — just do the work and reply with results.
+- Never ask "should I do this?" — just do it. User can undo in 3 seconds.
+- Never ask "want me to wait?" — just wait.
+- Never show raw JSON to the human — summarize naturally.
 - One inbox() to orient. Don't call it repeatedly.
-- If user says "check" or "check patchcord" — call inbox()
+- If user says "check" or "check patchcord" — call inbox().
 - Presence is not a send or delivery gate. Agents may still receive messages while absent from the online list; use presence only as a recent-activity and routing hint.
 - send_message() is blocked by unread inbox items, not by offline status. If sending is blocked, clear actionable inbox items first.
-- Resolve machine names to agent_ids from inbox() results
-- list_recent_debug is for debugging only — never call it routinely
+- Resolve machine names to agent_ids from inbox() results.
+- list_recent_debug is for debugging only — never call it routinely.
 - Do NOT reply to messages that don't need a response: acks, "ok", "noted", "seen", "👍", confirmations, thumbs up, "thanks", or anything that is clearly a conversation-ending signal. Just read them and move on. Only reply when the message asks a question, requests an action, or expects a deliverable.
 - NEVER use `mcp__claude_ai_*` tools for patchcord. These are web interface OAuth tools with wrong identity. Always use `mcp__patchcord__*` (project-level). If only `claude_ai` tools are visible, diagnose the config: check `.mcp.json`, run `claude mcp get patchcord`, check `~/.claude/settings.json` deny rule.