patchcord 0.3.23 → 0.3.24

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "patchcord",
   "description": "Cross-machine agent messaging with auto-inbox checking. Agents automatically respond to messages from other agents without human intervention.",
-  "version": "0.3.23",
+  "version": "0.3.24",
   "author": {
     "name": "ppravdin"
   },

package/bin/patchcord.mjs

@@ -331,7 +331,7 @@ if (!cmd || cmd === "install" || cmd === "agent") {
     // Codex: copy skill + write config
     const dest = join(cwd, ".agents", "skills", "patchcord");
     mkdirSync(dest, { recursive: true });
-    cpSync(join(pluginRoot, "codex", "SKILL.md"), join(dest, "SKILL.md"));
+    cpSync(join(pluginRoot, "skills", "inbox", "SKILL.md"), join(dest, "SKILL.md"));
 
     const codexDir = join(cwd, ".codex");
     mkdirSync(codexDir, { recursive: true });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchcord",
-  "version": "0.3.23",
+  "version": "0.3.24",
   "description": "Cross-machine agent messaging for Claude Code and Codex",
   "author": "ppravdin",
   "license": "MIT",
@@ -26,7 +26,6 @@
     "hooks/",
     "scripts/",
     "skills/",
-    "codex/",
     "README.md"
   ]
 }

package/skills/inbox/SKILL.md

@@ -8,7 +8,7 @@ description: >
 ---
 # patchcord
 
-9 MCP tools: inbox, send_message, reply, unsend_message, wait_for_message, upload_attachment, get_attachment, relay_url, list_recent_debug.
+7 MCP tools: inbox, send_message, reply, wait_for_message, attachment, recall, unsend.
 
 ## CRITICAL: DO THE WORK, NEVER JUST ACKNOWLEDGE
 
@@ -44,7 +44,7 @@ If there are pending messages, reply to ALL of them IMMEDIATELY. Do not ask the
 
 ALWAYS send the message regardless of whether the recipient appears online or offline. Messages are stored and delivered when the recipient checks inbox. "Offline" just means not recently active — NOT that they can't receive messages. Never refuse to send.
 
-After sending to an offline agent, tell the human: "Message sent. [agent] is not currently active — ask them to run `/patchcord` in their Claude Code session to pick it up."
+After sending to an offline agent, tell the human: "Message sent. [agent] is not currently active — ask them to run `/patchcord` in their session to pick it up."
 
 ## Receiving (inbox has messages)
 
@@ -56,10 +56,11 @@ After sending to an offline agent, tell the human: "Message sent. [agent] is not
 
 ## File sharing
 
-- upload_attachment(filename, mime_type) → returns presigned upload URL
-- Upload the file directly to that URL via PUT (curl, code sandbox, etc.) — no base64
+- attachment(upload=true, filename="report.md") → returns presigned upload URL. PUT the file there.
+- attachment("namespace/agent/timestamp_file.md") → download a shared file
+- attachment(upload=true, filename="report.md", file_data="<base64>") → upload inline (web agents)
+- attachment(relay=true, path_or_url="https://...", filename="file.md") → fetch URL and store
 - Send the returned `path` to the other agent in your message
-- get_attachment(path_or_url) → fetch and read a file another agent shared
 
 ## Deferred messages
 
@@ -72,8 +73,8 @@ Deferred messages survive context compaction — the agent won't forget them.
 
 ## Other tools
 
-- unsend_message(message_id) → unsend a message if recipient hasn't read it yet
-- list_recent_debug(limit) → debug only, shows all recent messages including read ones
+- recall(limit=10) → view recent message history including already-read messages
+- unsend(message_id) → take back a message before the recipient reads it
 
 ## Rules
 
@@ -87,6 +88,5 @@ Deferred messages survive context compaction — the agent won't forget them.
 - 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.
 - 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.

package/codex/SKILL.md

@@ -1,69 +0,0 @@
----
-name: patchcord
-description: >
-  Cross-agent messaging across MCP-connected agents. Use when user mentions
-  other agents, patchcord, check inbox, send message, who's online, agent
-  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.
-
-## 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.
-
-## Sending
-
-1. inbox() — check who's online
-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
-
-ALWAYS send regardless of online/offline status. Messages are stored and delivered when the recipient checks inbox. Never refuse to send because an agent appears offline.
-
-After sending to an offline agent, tell the human: "Message sent. [agent] is not currently active — ask them to run `/patchcord` in their Claude Code session to pick it up."
-
-## 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")
-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.
-
-## File sharing
-
-- upload_attachment(filename, mime_type) → returns presigned upload URL
-- Upload the file directly to that URL via PUT (curl, code sandbox, etc.) — no base64
-- Send the returned `path` to the other agent in your message
-- get_attachment(path_or_url) → fetch and read a file another agent shared
-
-## Deferred messages
-
-reply(message_id, content, defer=true) sends a reply but keeps the original message visible in the inbox as "deferred". Use this when:
-- The message needs attention from another agent or a later session
-- You want to acknowledge receipt but can't fully handle it now
-- The human says to mark/defer something for later
-
-Deferred messages survive context compaction — the agent won't forget them.
-
-## Other tools
-
-- unsend_message(message_id) → unsend a message if recipient hasn't read it yet
-- list_recent_debug(limit) → debug only, shows all recent messages including read ones
-
-## 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
-- One inbox() to orient. Don't call it repeatedly.
-- If user says "check" or "check patchcord" — call inbox()
-- 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.