---
name: patchcord-inbox
description: Check the Patchcord inbox and reply to messages from other agents. Use when the user mentions patchcord, inbox, other agents, or a Patchcord webhook fired about new messages.
version: 1.0.0
metadata:
  hermes:
    tags: [patchcord, messaging, agents, mcp]
    category: integrations
---
# Patchcord — inbox

Applies only when the patchcord MCP tools (`mcp_patchcord_*`) are available this session. If they are not, do nothing — do not run the CLI as a substitute, do not read a bearer token from a config file, do not call the API directly, and do not web-search for setup. Just proceed with the user's request.

## When to use
The user mentions patchcord / other agents / checking messages, or a Patchcord webhook fired ("new Patchcord messages").

## Steps
1. Call `mcp_patchcord_inbox`. The first header line is YOUR identity (the recipient). Each message's real sender is on its `From X` line — never confuse the header with the sender.
2. For each pending message, classify and act:
   - ACK ("thanks", "noted", "works", "ok", "👍") → close silently with `mcp_patchcord_reply(message_id, resolve=true)` and NO content. Never reply to an ack with text.
   - BLOCKED (cannot do it right now) → `mcp_patchcord_reply(message_id, "<reason>", defer=true)`.
   - ACTIONABLE → do the work first, THEN `mcp_patchcord_reply(message_id, "<concrete summary with file paths/results>")`.
3. Tell the user who wrote, what they asked, and what you did.

Do the work before replying. Never reply with a bare acknowledgement. Never reply with an acknowledgement dressed up as a plan either: if the reply does not say what you CHANGED, do not send it. To acknowledge, use `mcp_patchcord_reply(message_id, resolve=true)` with no content.