--- name: log-discord-server-reply description: "Replying in a Discord server channel. A log play (docs/useCases/discord/serverReply.md): Answer someone in a channel of a Discord server: a mention of the account, a reply to its message, or a question in a channel the owner is part of, like \"pennyserver #general\". A server channel is not a group chat. It is a room inside someone else's server, with members who never joined a conversation with the owner, an owner and its own rules, so it is read, answered and sent differently from a DM or a group DM. DMs and group DMs are [channelReply](channelReply.md)." when_to_use: "Use when the owner asks for this, in words like: \"reply to in \", \"answer him in the general\", \"message the guy in # who mentioned me\", \"reply in the server\", \"find what said in and answer it\"" metadata: summary: "Replying in a Discord server channel" --- # Replying in a Discord server channel This is the log play `discord/serverReply`. Before anything else, call the log MCP tool `getGuide({ useCase: "discord/serverReply" })`: it returns this page and makes it the session's play, so every log tool's answer says which step you are on and a send with no play loaded is refused (rules 157, 158). Then follow the steps in order. Draft every message from that person's own thread and the owner's real replies (`voice` with no text, `search`), never from memory, and never send two that read alike (`sameAsSent`). Answer someone in a channel of a Discord server: a mention of the account, a reply to its message, or a question in a channel the owner is part of, like "pennyserver #general". A server channel is not a group chat. It is a room inside someone else's server, with members who never joined a conversation with the owner, an owner and its own rules, so it is read, answered and sent differently from a DM or a group DM. DMs and group DMs are [channelReply](../log-discord-channel-reply/SKILL.md). How the owner asks for it: "reply to in ", "answer him in the general", "message the guy in # who mentioned me", "reply in the server", "find what said in and answer it" ## Run it from a fresh context Say: **"go on docs/useCases/discord/serverReply.md for #"**. The agent reads this page and runs the steps. ## A server channel, a group DM and a DM | | Server channel | Group DM | DM | | --- | --- | --- | --- | | What it is | A channel inside a server: a room with an owner, mods, rules and members who aren't in a conversation with the owner | A private chat of a few people the owner is in, with no server and no owner but its members | The owner and one person | | How it is named | `" #"`, like `"pennyserver #general"` | its name, or the members' names when it has none | the person | | In `discordChats` | `kind: "channel"`, with `server` and `serverId` | `kind: "group"` | `kind: "dm"` | | What the watcher keeps | only mentions of the account and replies to it; the rest of the channel is never stored | every message | every message | | Where a read comes from | always from Discord, never log.db, since log.db holds only those mentions and replies | log.db when the account is caught up and the chat backfilled | the same as a group DM | | `search` finds | only the mentions and replies the watcher kept, and what an earlier read stored | the whole conversation | the whole conversation | | A send while the account is behind | refused with `accountBehind` until the account catches up | that one chat is caught up, then it sends | the same as a group DM | | Who the answer is for | one person in a room everyone reads: tag them | everyone in the group | the person | | The page | this one | [channelReply](../log-discord-channel-reply/SKILL.md) | [channelReply](../log-discord-channel-reply/SKILL.md) | ## The steps | # | Step | Tool | Done when | | --- | --- | --- | --- | | 1 | Find the server's channel by its name | `discordChannels` { account, server: "" } | the channel by its name and kind; for a forum, the post from `discordPosts`, named `" # > "` | | 2 | Claim the channel, so no other session answers it | `inboxClaim` { platform: "discord", account, chat: "", event: "" } | this session holds the channel | | 3 | Read the channel or post from Discord, far enough back to have what they said, what it answers and anything the owner already said after it | `discordRead` { account, channel: " #", limit: 50 } | their message with its `fromId`, the messages before it, and none from the owner after it | | 4 | Write the answer to that one person, from what they asked and what the owner said to tell them, in the owner's words and length, then gate it | `voice` { to: "", context: "", text: "" } | `PASS`, or the owner's own words given for this message | | 5 | Send it to the channel by its name, tagging the person with `<@their fromId>` | `discordSendLive` { account, channel: " #", text: "<@fromId> ", approvedBy: "", confirmLive: true } | Discord answers `sent` with the message id | ## What to know - **It is someone else's room.** The server has an owner and rules. Answer what was asked and stay in the channel's topic. A pitch or a sales line in someone's server is not a reply: a server owner once asked the owner not to use their Discord for selling services. - **Tag the one person.** Everyone in the channel reads every message, so the answer starts with `<@their fromId>` (from the read in step 3), the way the owner tags people there ("have you ever made generative ui before <@their fromId>"). The AI artifact check passes a mention. Never talk to the whole room as if it were a DM. - **The read is always live.** log.db keeps only the mentions and replies from a server channel, so `discordRead` reads the channel from Discord every time and says so. Up to 1000 messages, 100 a page. A 429 stops the read and pauses the account (rule 94). - **Finding an old conversation in a server.** Log's own `search` doesn't hold a server's history, only the mentions and replies the watcher kept. Use `discordSearch` on the server: [serverSearch](../log-discord-server-search/SKILL.md). Reading a channel back to look for something is the slow way: one piece of advice took a 400-message read of "pennyserver #general" on 12 Nov 2026. - **When the owner is already there, leave it to the owner.** If the owner's own message comes after theirs, the owner is answering: send nothing and release the claim with `inboxRelease` { platform: "discord", account, chat: "" }. A send releases the claim by itself. - **A send waits for the account.** A send to a server channel needs the account caught up; while it is behind, Discord isn't contacted and the answer is `accountBehind`. Wait for the catch-up, never go around it (rules 94, 105). - **The voice gate can't find a server channel by name.** Gate with `to` and `context` only, never `with`. - **The owner's own words.** When the owner says what to tell them, the answer is the owner's words. When the gate still refuses them, `overGate` on `discordSendLive` sends that exact message; the AI artifact check still runs (rule 137). - **One message per line.** A draft on several lines goes out one message per line, and in a busy channel other people's messages can land between them. Keep a server answer to one or two lines (rule 90). - **X links embed as fixupx.** Share an X post on Discord as https://fixupx.com//status/, never x.com: Discord only embeds the post and its video from fixupx. `discordSendLive` turns any x.com or twitter.com post link into fixupx.com itself (the owner, 2026-11-13). - **Name the channel, never its id.** The chat-names hook refuses an id: `" #"`, or `" # > "` for a forum post (rule 154). - **Forums and threads.** A forum holds posts, each its own conversation: answer inside the post, never in the forum. What each part of a server is: the `discordServers` skill in the discord guide; going through a forum for posts to answer: [forumPosts](../log-discord-forum-posts/SKILL.md).