---
name: feedback_discord_read_replies
description: Discord DM replies are invisible to coord/repo sync — use `discord-dm.sh read <user>` to see if mike/winter/rob actually answered.
metadata:
  type: feedback
---

When we DM someone via the `discord-dm` skill and wait on an answer, their reply does NOT
come through coord messages or repo sync — those channels never carry Discord replies. Before
telling the user "no reply yet / they didn't answer," READ the DM channel:

```bash
bash .claude/scripts/discord-dm.sh read mike 10      # last 10 in the mike DM
bash .claude/scripts/discord-dm.sh read #dev-alerts  # a channel
```

Output is oldest-first; lines marked `>>>` are from THEM (replies), indented lines are us.

**Why:** the bot participates in every DM channel it opened, so `GET /channels/<id>/messages`
returns full content — the Message Content privileged intent only gates gateway events, not this
REST fetch. Before adding `read` (2026-07-07, Howard flagged it) the wrapper was send-only, so
replies from mike/winter were silently missed.

**How to apply:** after DMing a question to mike/winter/rob, `read` that user to check for their
answer instead of assuming silence. Related: [[reference_community_forum]] is a different channel;
this is Discord DMs/channels via [[discord-dm]] (`.claude/scripts/discord-dm.sh`).
