@symerian/symi 3.0.16 → 3.0.18

package/docs/automation/poll.md

@@ -11,7 +11,6 @@ title: "Polls"
 ## Supported channels
 
 - WhatsApp (web channel)
-- Discord
 - MS Teams (Adaptive Cards)
 
 ## CLI
@@ -23,10 +22,7 @@ symi message poll --target +15555550123 \
 symi message poll --target 123456789@g.us \
   --poll-question "Meeting time?" --poll-option "10am" --poll-option "2pm" --poll-option "4pm" --poll-multi
 
-# Discord
-symi message poll --channel discord --target channel:123456789 \
   --poll-question "Snack?" --poll-option "Pizza" --poll-option "Sushi"
-symi message poll --channel discord --target channel:123456789 \
   --poll-question "Plan?" --poll-option "A" --poll-option "B" --poll-duration-hours 48
 
 # MS Teams
@@ -36,9 +32,7 @@ symi message poll --channel msteams --target conversation:19:abc@thread.tacv2 \
 
 Options:
 
-- `--channel`: `whatsapp` (default), `discord`, or `msteams`
 - `--poll-multi`: allow selecting multiple options
-- `--poll-duration-hours`: Discord-only (defaults to 24 when omitted)
 
 ## Gateway RPC
 
@@ -57,13 +51,11 @@ Params:
 ## Channel differences
 
 - WhatsApp: 2-12 options, `maxSelections` must be within option count, ignores `durationHours`.
-- Discord: 2-10 options, `durationHours` clamped to 1-768 hours (default 24). `maxSelections > 1` enables multi-select; Discord does not support a strict selection count.
 - MS Teams: Adaptive Card polls (Symi-managed). No native poll API; `durationHours` is ignored.
 
 ## Agent tool (Message)
 
 Use the `message` tool with `poll` action (`to`, `pollQuestion`, `pollOption`, optional `pollMulti`, `pollDurationHours`, `channel`).
 
-Note: Discord has no “pick exactly N” mode; `pollMulti` maps to multi-select.
 Teams polls are rendered as Adaptive Cards and require the gateway to stay online
 to record votes in `~/.symi/msteams-polls.json`.

package/docs/automation/webhook.md

@@ -83,8 +83,6 @@ Payload:
 - `sessionKey` optional (string): The key used to identify the agent's session. By default this field is rejected unless `hooks.allowRequestSessionKey=true`.
 - `wakeMode` optional (`now` | `next-heartbeat`): Whether to trigger an immediate heartbeat (default `now`) or wait for the next periodic check.
 - `deliver` optional (boolean): If `true`, the agent's response will be sent to the messaging channel. Defaults to `true`. Responses that are only heartbeat acknowledgments are automatically skipped.
-- `channel` optional (string): The messaging channel for delivery. One of: `last`, `whatsapp`, `telegram`, `discord`, `slack`, `mattermost` (plugin), `signal`, `imessage`, `msteams`. Defaults to `last`.
-- `to` optional (string): The recipient identifier for the channel (e.g., phone number for WhatsApp/Signal, chat ID for Telegram, channel ID for Discord/Slack/Mattermost (plugin), conversation ID for MS Teams). Defaults to the last recipient in the main session.
 - `model` optional (string): Model override (e.g., `anthropic/claude-3-5-sonnet` or an alias). Must be in the allowed model list if restricted.
 - `thinking` optional (string): Thinking level override (e.g., `low`, `medium`, `high`).
 - `timeoutSeconds` optional (number): Maximum duration for the agent run in seconds.

package/docs/capabilities.md

@@ -34,7 +34,6 @@ block (Stage 3.5).
 | `channel-routing`     | Messaging conventions and channel routing rules. Reply in current session auto-routes to the source channel; cross-session messaging via sessions_send; sub-agent orchestration via subagents tool; syst | message, messaging, channel, route, routing, send, sessions_send, subagent |
 | `coding-agent`        | "Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large co | coding-agent, coding, agent                                                |
 | `connect-email`       | Connect a user's email account (Outlook 365 or Gmail) to Symi. Use when the user asks to connect, link, set up, configure, or troubleshoot email — including any mention of "my email", "work email", "o | connect-email, connect, email                                              |
-| `discord`             | "Discord ops via the message tool (channel=discord)."                                                                                                                                                    | discord                                                                    |
 | `document-generation` | Generate Word (.docx), Excel (.xlsx), PowerPoint (.pptx), and PDF documents via npm packages bundled with Symi. Write a short Node.js script (.cjs for CommonJS), execute via exec with host=gateway. Us | document, docx, xlsx, pptx, pdf, word, excel, powerpoint                   |
 | `eightctl`            | Control Eight Sleep pods (status, temperature, alarms, schedules).                                                                                                                                       | eightctl                                                                   |
 | `food-order`          | Reorder Foodora orders + track ETA/status with ordercli. Never confirm without explicit user approval. Triggers: order food, reorder, track ETA.                                                         | food-order, food, order                                                    |
@@ -97,7 +96,6 @@ auth providers all live here. Each ships its own `package.json`.
 | `bluebubbles`             | 2.9.4   | Symi BlueBubbles channel plugin                                                                       |
 | `copilot-proxy`           | 2.9.4   | Symi Copilot Proxy provider plugin                                                                    |
 | `diagnostics-otel`        | 2.9.4   | Symi diagnostics OpenTelemetry exporter                                                               |
-| `discord`                 | 2.9.4   | Symi Discord channel plugin                                                                           |
 | `feishu`                  | 2.9.4   | Symi Feishu/Lark channel plugin (community maintained by @m1heng)                                     |
 | `google-antigravity-auth` | 2.9.4   | Symi Google Antigravity OAuth provider plugin                                                         |
 | `google-gemini-cli-auth`  | 2.9.4   | Symi Gemini CLI OAuth provider plugin                                                                 |

package/docs/channels/broadcast-groups.md

@@ -278,7 +278,6 @@ Broadcast groups currently work with:
 
 - ✅ WhatsApp (implemented)
 - 🚧 Telegram (planned)
-- 🚧 Discord (planned)
 - 🚧 Slack (planned)
 
 ### Routing

package/docs/channels/channel-routing.md

@@ -1,5 +1,4 @@
 ---
-summary: "Routing rules per channel (WhatsApp, Telegram, Discord, Slack) and shared context"
 read_when:
   - Changing channel routing or inbox behavior
 title: "Channel Routing"
@@ -13,7 +12,6 @@ host configuration.
 
 ## Key terms
 
-- **Channel**: `whatsapp`, `telegram`, `discord`, `slack`, `signal`, `imessage`, `webchat`.
 - **AccountId**: per‑channel account instance (when supported).
 - **AgentId**: an isolated workspace + session store (“brain”).
 - **SessionKey**: the bucket key used to store context and control concurrency.
@@ -31,13 +29,11 @@ Groups and channels remain isolated per channel:
 
 Threads:
 
-- Slack/Discord threads append `:thread:<threadId>` to the base key.
 - Telegram forum topics embed `:topic:<topicId>` in the group key.
 
 Examples:
 
 - `agent:main:telegram:group:-1001234567890:topic:42`
-- `agent:main:discord:channel:123456:thread:987654`
 
 ## Routing rules (how an agent is chosen)
 
@@ -45,12 +41,10 @@ Routing picks **one agent** for each inbound message:
 
 1. **Exact peer match** (`bindings` with `peer.kind` + `peer.id`).
 2. **Parent peer match** (thread inheritance).
-3. **Guild + roles match** (Discord) via `guildId` + `roles`.
-4. **Guild match** (Discord) via `guildId`.
-5. **Team match** (Slack) via `teamId`.
-6. **Account match** (`accountId` on the channel).
-7. **Channel match** (any account on that channel, `accountId: "*"`).
-8. **Default agent** (`agents.list[].default`, else first list entry, fallback to `main`).
+3. **Team match** (Slack) via `teamId`.
+4. **Account match** (`accountId` on the channel).
+5. **Channel match** (any account on that channel, `accountId: "*"`).
+6. **Default agent** (`agents.list[].default`, else first list entry, fallback to `main`).
 
 When a binding includes multiple match fields (`peer`, `guildId`, `teamId`, `roles`), **all provided fields must match** for that binding to apply.
 

package/docs/channels/group-messages.md

@@ -9,8 +9,6 @@ title: "Group Messages"
 
 Goal: let Symi sit in WhatsApp groups, wake up only when pinged, and keep that thread separate from the personal DM session.
 
-Note: `agents.list[].groupChat.mentionPatterns` is now used by Telegram/Discord/Slack/iMessage as well; this doc focuses on WhatsApp-specific behavior. For multi-agent setups, set `agents.list[].groupChat.mentionPatterns` per agent (or use `messages.groupChat.mentionPatterns` as a global fallback).
-
 ## What’s implemented (2025-12-03)
 
 - Activation modes: `mention` (default) or `always`. `mention` requires a ping (real WhatsApp @-mentions via `mentionedJids`, regex patterns, or the bot’s E.164 anywhere in the text). `always` wakes the agent on every message but it should reply only when it can add meaningful value; otherwise it returns the silent token `NO_REPLY`. Defaults can be set in config (`channels.whatsapp.groups`) and overridden per group via `/activation`. When `channels.whatsapp.groups` is set, it also acts as a group allowlist (include `"*"` to allow all).

package/docs/channels/groups.md

@@ -1,5 +1,4 @@
 ---
-summary: "Group chat behavior across surfaces (WhatsApp/Telegram/Discord/Slack/Signal/iMessage/Microsoft Teams)"
 read_when:
   - Changing group chat behavior or mention gating
 title: "Groups"
@@ -7,8 +6,6 @@ title: "Groups"
 
 # Groups
 
-Symi treats group chats consistently across surfaces: WhatsApp, Telegram, Discord, Slack, Signal, iMessage, Microsoft Teams.
-
 ## Beginner intro (2 minutes)
 
 Symi “lives” on your own messaging accounts. There is no separate WhatsApp bot user.
@@ -152,7 +149,6 @@ Control how group/room messages are handled per channel:
       groupPolicy: "disabled",
       groupAllowFrom: ["user@org.com"],
     },
-    discord: {
       groupPolicy: "allowlist",
       guilds: {
         GUILD_ID: { channels: { help: { allow: true } } },
@@ -184,10 +180,8 @@ Notes:
 
 - `groupPolicy` is separate from mention-gating (which requires @mentions).
 - WhatsApp/Telegram/Signal/iMessage/Microsoft Teams: use `groupAllowFrom` (fallback: explicit `allowFrom`).
-- Discord: allowlist uses `channels.discord.guilds.<id>.channels`.
 - Slack: allowlist uses `channels.slack.channels`.
 - Matrix: allowlist uses `channels.matrix.groups` (room IDs, aliases, or names). Use `channels.matrix.groupAllowFrom` to restrict senders; per-room `users` allowlists are also supported.
-- Group DMs are controlled separately (`channels.discord.dm.*`, `channels.slack.dm.*`).
 - Telegram allowlist can match user IDs (`"123456789"`, `"telegram:123456789"`, `"tg:123456789"`) or usernames (`"@alice"` or `"alice"`); prefixes are case-insensitive.
 - Default is `groupPolicy: "allowlist"`; if your group allowlist is empty, group messages are blocked.
 
@@ -201,8 +195,6 @@ Quick mental model (evaluation order for group messages):
 
 Group messages require a mention unless overridden per group. Defaults live per subsystem under `*.groups."*"`.
 
-Replying to a bot message counts as an implicit mention (when the channel supports reply metadata). This applies to Telegram, WhatsApp, Slack, Discord, and Microsoft Teams.
-
 ```json5
 {
   channels: {
@@ -245,7 +237,6 @@ Notes:
 - Surfaces that provide explicit mentions still pass; patterns are a fallback.
 - Per-agent override: `agents.list[].groupChat.mentionPatterns` (useful when multiple agents share a group).
 - Mention gating is only enforced when mention detection is possible (native mentions or `mentionPatterns` are configured).
-- Discord defaults live in `channels.discord.guilds."*"` (overridable per guild/channel).
 - Group history context is wrapped uniformly across channels and is **pending-only** (messages skipped due to mention gating); use `messages.groupChat.historyLimit` for the global default and `channels.<channel>.historyLimit` (or `channels.<channel>.accounts.*.historyLimit`) for overrides. Set `0` to disable.
 
 ## Group/channel tool restrictions (optional)
@@ -285,7 +276,6 @@ Example (Telegram):
 Notes:
 
 - Group/channel tool restrictions are applied in addition to global/agent tool policy (deny still wins).
-- Some channels use different nesting for rooms/channels (e.g., Discord `guilds.*.channels.*`, Slack `channels.*`, MS Teams `teams.*.channels.*`).
 
 ## Group allowlists
 

package/docs/channels/index.md

@@ -15,7 +15,6 @@ Text is supported everywhere; media and reactions vary by channel.
 
 - [WhatsApp](/channels/whatsapp) — Most popular; uses Baileys and requires QR pairing.
 - [Telegram](/channels/telegram) — Bot API via grammY; supports groups.
-- [Discord](/channels/discord) — Discord Bot API + Gateway; supports servers, channels, and DMs.
 - [IRC](/channels/irc) — Classic IRC servers; channels + DMs with pairing/allowlist controls.
 - [Slack](/channels/slack) — Bolt SDK; workspace apps.
 - [Feishu](/channels/feishu) — Feishu/Lark bot via WebSocket (plugin, installed separately).

package/docs/channels/matrix.md

@@ -138,8 +138,6 @@ Once verified, the bot can decrypt messages in encrypted rooms.
 
 ## Multi-account
 
-Multi-account support: use `channels.matrix.accounts` with per-account credentials and optional `name`. See [`gateway/configuration`](/gateway/configuration#telegramaccounts--discordaccounts--slackaccounts--signalaccounts--imessageaccounts) for the shared pattern.
-
 Each account runs as a separate Matrix user on any homeserver. Per-account config
 inherits from the top-level `channels.matrix` settings and can override any option
 (DM policy, groups, encryption, etc.).

package/docs/channels/msteams.md

@@ -439,8 +439,6 @@ Symi handles this by returning quickly and sending replies proactively, but very
 
 ### Formatting
 
-Teams markdown is more limited than Slack or Discord:
-
 - Basic formatting works: **bold**, _italic_, `code`, links
 - Complex markdown (tables, nested lists) may not render correctly
 - Adaptive Cards are supported for polls and arbitrary card sends (see below)

package/docs/channels/pairing.md

@@ -36,8 +36,6 @@ symi pairing list telegram
 symi pairing approve telegram <CODE>
 ```
 
-Supported channels: `telegram`, `whatsapp`, `signal`, `imessage`, `discord`, `slack`, `feishu`.
-
 ### Where the state lives
 
 Stored under `~/.symi/credentials/`:
@@ -99,5 +97,4 @@ Stored under `~/.symi/devices/`:
   - Signal: [Signal](/channels/signal)
   - BlueBubbles (iMessage): [BlueBubbles](/channels/bluebubbles)
   - iMessage (legacy): [iMessage](/channels/imessage)
-  - Discord: [Discord](/channels/discord)
   - Slack: [Slack](/channels/slack)

package/docs/channels/signal.md

@@ -99,8 +99,6 @@ Example:
 }
 ```
 
-Multi-account support: use `channels.signal.accounts` with per-account config and optional `name`. See [`gateway/configuration`](/gateway/configuration#telegramaccounts--discordaccounts--slackaccounts--signalaccounts--imessageaccounts) for the shared pattern.
-
 ## Onboarding (option B): register dedicated bot number (SMS, Linux)
 
 Use this when you want a dedicated bot number instead of linking an existing Signal app account.

package/docs/channels/troubleshooting.md

@@ -53,17 +53,10 @@ Full troubleshooting: [/channels/whatsapp#troubleshooting-quick](/channels/whats
 
 Full troubleshooting: [/channels/telegram#troubleshooting](/channels/telegram#troubleshooting)
 
-## Discord
-
-### Discord failure signatures
-
 | Symptom                         | Fastest check                       | Fix                                                       |
 | ------------------------------- | ----------------------------------- | --------------------------------------------------------- |
 | Bot online but no guild replies | `symi channels status --probe`      | Allow guild/channel and verify message content intent.    |
 | Group messages ignored          | Check logs for mention gating drops | Mention bot or set guild/channel `requireMention: false`. |
-| DM replies missing              | `symi pairing list discord`         | Approve DM pairing or adjust DM policy.                   |
-
-Full troubleshooting: [/channels/discord#troubleshooting](/channels/discord#troubleshooting)
 
 ## Slack
 

package/docs/cli/channels.md

@@ -1,7 +1,6 @@
 ---
 summary: "CLI reference for `symi channels` (accounts, status, login/logout, logs)"
 read_when:
-  - You want to add/remove channel accounts (WhatsApp/Telegram/Discord/Google Chat/Slack/Mattermost (plugin)/Signal/iMessage)
   - You want to check channel status or tail channel logs
 title: "channels"
 ---
@@ -21,7 +20,6 @@ Related docs:
 symi channels list
 symi channels status
 symi channels capabilities
-symi channels capabilities --channel discord --target channel:123
 symi channels resolve --channel slack "#general" "@jane"
 symi channels logs --channel all
 ```
@@ -54,14 +52,11 @@ Fetch provider capability hints (intents/scopes where available) plus static fea
 
 ```bash
 symi channels capabilities
-symi channels capabilities --channel discord --target channel:123
 ```
 
 Notes:
 
 - `--channel` is optional; omit it to list every channel (including extensions).
-- `--target` accepts `channel:<id>` or a raw numeric channel id and only applies to Discord.
-- Probes are provider-specific: Discord intents + optional channel permissions; Slack bot + user scopes; Telegram bot flags + webhook; Signal daemon version; MS Teams app token + Graph roles/scopes (annotated where known). Channels without probes report `Probe: unavailable`.
 
 ## Resolve names to IDs
 
@@ -69,7 +64,6 @@ Resolve channel/user names to IDs using the provider directory:
 
 ```bash
 symi channels resolve --channel slack "#general" "@jane"
-symi channels resolve --channel discord "My Server/#support" "@someone"
 symi channels resolve --channel matrix "Project Room"
 ```
 

package/docs/cli/configure.md

@@ -23,7 +23,6 @@ Related:
 Notes:
 
 - Choosing where the Gateway runs always updates `gateway.mode`. You can select "Continue" without other sections if that is all you need.
-- Channel-oriented services (Slack/Discord/Matrix/Microsoft Teams) prompt for channel/room allowlists during setup. You can enter names or IDs; the wizard resolves names to IDs when possible.
 
 ## Examples
 

package/docs/cli/directory.md

@@ -34,7 +34,6 @@ symi message send --channel slack --target user:U012ABCDEF --message "hello"
 - WhatsApp: `+15551234567` (DM), `1234567890-1234567890@g.us` (group)
 - Telegram: `@username` or numeric chat id; groups are numeric ids
 - Slack: `user:U…` and `channel:C…`
-- Discord: `user:<id>` and `channel:<id>`
 - Matrix (plugin): `user:@user:server`, `room:!roomId:server`, or `#alias:server`
 - Microsoft Teams (plugin): `user:<id>` and `conversation:<id>`
 - Zalo (plugin): user id (Bot API)

package/docs/cli/index.md

@@ -372,8 +372,6 @@ Options:
 
 ### `channels`
 
-Manage chat channel accounts (WhatsApp/Telegram/Discord/Google Chat/Slack/Mattermost (plugin)/Signal/iMessage/MS Teams).
-
 Subcommands:
 
 - `channels list`: show configured channels and auth profiles.
@@ -387,7 +385,6 @@ Subcommands:
 
 Common options:
 
-- `--channel <name>`: `whatsapp|telegram|discord|googlechat|slack|mattermost|signal|imessage|msteams`
 - `--account <id>`: channel account id (default `default`)
 - `--name <label>`: display name for the account
 
@@ -419,8 +416,6 @@ Examples:
 
 ```bash
 symi channels add --channel telegram --account alerts --name "Alerts Bot" --token $TELEGRAM_BOT_TOKEN
-symi channels add --channel discord --account work --name "Work Bot" --token $DISCORD_BOT_TOKEN
-symi channels remove --channel discord --account work --delete
 symi channels status --probe
 symi status --deep
 ```
@@ -492,7 +487,6 @@ Subcommands:
 Examples:
 
 - `symi message send --target +15555550123 --message "Hi"`
-- `symi message poll --channel discord --target channel:123 --poll-question "Snack?" --poll-option Pizza --poll-option Sushi`
 
 ### `agent`
 
@@ -508,7 +502,6 @@ Options:
 - `--session-id <id>`
 - `--thinking <off|minimal|low|medium|high|xhigh>` (GPT-5.2 + Codex models only)
 - `--verbose <on|full|off>`
-- `--channel <whatsapp|telegram|discord|slack|mattermost|signal|imessage|msteams>`
 - `--local`
 - `--deliver`
 - `--json`

package/docs/cli/message.md

@@ -9,7 +9,6 @@ title: "message"
 # `symi message`
 
 Single outbound command for sending messages and channel actions
-(Discord/Google Chat/Slack/Mattermost (plugin)/Telegram/WhatsApp/Signal/iMessage/MS Teams).
 
 ## Usage
 
@@ -21,13 +20,11 @@ Channel selection:
 
 - `--channel` required if more than one channel is configured.
 - If exactly one channel is configured, it becomes the default.
-- Values: `whatsapp|telegram|discord|googlechat|slack|mattermost|signal|imessage|msteams` (Mattermost requires plugin)
 
 Target formats (`--target`):
 
 - WhatsApp: E.164 or group JID
 - Telegram: chat id or `@username`
-- Discord: `channel:<id>` or `user:<id>` (or `<@id>` mention; raw numeric ids are treated as channels)
 - Google Chat: `spaces/<spaceId>` or `users/<userId>`
 - Slack: `channel:<id>` or `user:<id>` (raw channel id is accepted)
 - Mattermost (plugin): `channel:<id>`, `user:<id>`, or `@username` (bare ids are treated as channels)
@@ -37,7 +34,6 @@ Target formats (`--target`):
 
 Name lookup:
 
-- For supported providers (Discord/Slack/etc), channel names like `Help` or `#help` are resolved via the directory cache.
 - On cache miss, Symi will attempt a live directory lookup when the provider supports it.
 
 ## Common flags
@@ -55,7 +51,6 @@ Name lookup:
 ### Core
 
 - `send`
-  - Channels: WhatsApp/Telegram/Discord/Google Chat/Slack/Mattermost (plugin)/Signal/iMessage/MS Teams
   - Required: `--target`, plus `--message` or `--media`
   - Optional: `--media`, `--reply-to`, `--thread-id`, `--gif-playback`
   - Telegram only: `--buttons` (requires `channels.telegram.capabilities.inlineButtons` to allow it)
@@ -64,14 +59,11 @@ Name lookup:
   - WhatsApp only: `--gif-playback`
 
 - `poll`
-  - Channels: WhatsApp/Telegram/Discord/Matrix/MS Teams
   - Required: `--target`, `--poll-question`, `--poll-option` (repeat)
   - Optional: `--poll-multi`
-  - Discord only: `--poll-duration-hours`, `--silent`, `--message`
   - Telegram only: `--poll-duration-seconds` (5-600), `--silent`, `--poll-anonymous` / `--poll-public`, `--thread-id`
 
 - `react`
-  - Channels: Discord/Google Chat/Slack/Telegram/WhatsApp/Signal
   - Required: `--message-id`, `--target`
   - Optional: `--emoji`, `--remove`, `--participant`, `--from-me`, `--target-author`, `--target-author-uuid`
   - Note: `--remove` requires `--emoji` (omit `--emoji` to clear own reactions where supported; see /tools/reactions)
@@ -79,96 +71,69 @@ Name lookup:
   - Signal group reactions: `--target-author` or `--target-author-uuid` required
 
 - `reactions`
-  - Channels: Discord/Google Chat/Slack
   - Required: `--message-id`, `--target`
   - Optional: `--limit`
 
 - `read`
-  - Channels: Discord/Slack
   - Required: `--target`
   - Optional: `--limit`, `--before`, `--after`
-  - Discord only: `--around`
 
 - `edit`
-  - Channels: Discord/Slack
   - Required: `--message-id`, `--message`, `--target`
 
 - `delete`
-  - Channels: Discord/Slack/Telegram
   - Required: `--message-id`, `--target`
 
 - `pin` / `unpin`
-  - Channels: Discord/Slack
   - Required: `--message-id`, `--target`
 
 - `pins` (list)
-  - Channels: Discord/Slack
   - Required: `--target`
 
 - `permissions`
-  - Channels: Discord
   - Required: `--target`
 
 - `search`
-  - Channels: Discord
   - Required: `--guild-id`, `--query`
   - Optional: `--channel-id`, `--channel-ids` (repeat), `--author-id`, `--author-ids` (repeat), `--limit`
 
 ### Threads
 
 - `thread create`
-  - Channels: Discord
   - Required: `--thread-name`, `--target` (channel id)
   - Optional: `--message-id`, `--message`, `--auto-archive-min`
 
 - `thread list`
-  - Channels: Discord
   - Required: `--guild-id`
   - Optional: `--channel-id`, `--include-archived`, `--before`, `--limit`
 
 - `thread reply`
-  - Channels: Discord
   - Required: `--target` (thread id), `--message`
   - Optional: `--media`, `--reply-to`
 
 ### Emojis
 
 - `emoji list`
-  - Discord: `--guild-id`
   - Slack: no extra flags
 
 - `emoji upload`
-  - Channels: Discord
   - Required: `--guild-id`, `--emoji-name`, `--media`
   - Optional: `--role-ids` (repeat)
 
 ### Stickers
 
 - `sticker send`
-  - Channels: Discord
   - Required: `--target`, `--sticker-id` (repeat)
   - Optional: `--message`
 
 - `sticker upload`
-  - Channels: Discord
   - Required: `--guild-id`, `--sticker-name`, `--sticker-desc`, `--sticker-tags`, `--media`
 
 ### Roles / Channels / Members / Voice
 
-- `role info` (Discord): `--guild-id`
-- `role add` / `role remove` (Discord): `--guild-id`, `--user-id`, `--role-id`
-- `channel info` (Discord): `--target`
-- `channel list` (Discord): `--guild-id`
-- `member info` (Discord/Slack): `--user-id` (+ `--guild-id` for Discord)
-- `voice status` (Discord): `--guild-id`, `--user-id`
-
 ### Events
 
-- `event list` (Discord): `--guild-id`
-- `event create` (Discord): `--guild-id`, `--event-name`, `--start-time`
-  - Optional: `--end-time`, `--desc`, `--channel-id`, `--location`, `--event-type`
-
-### Moderation (Discord)
+- Optional: `--end-time`, `--desc`, `--channel-id`, `--location`, `--event-type`
 
 - `timeout`: `--guild-id`, `--user-id` (optional `--duration-min` or `--until`; omit both to clear timeout)
 - `kick`: `--guild-id`, `--user-id` (+ `--reason`)
@@ -184,27 +149,16 @@ Name lookup:
 
 ## Examples
 
-Send a Discord reply:
-
 ```
-symi message send --channel discord \
   --target channel:123 --message "hi" --reply-to 456
 ```
 
-Send a Discord message with components:
-
 ```
-symi message send --channel discord \
   --target channel:123 --message "Choose:" \
   --components '{"text":"Choose a path","blocks":[{"type":"actions","buttons":[{"label":"Approve","style":"success"},{"label":"Decline","style":"danger"}]}]}'
 ```
 
-See [Discord components](/channels/discord#interactive-components) for the full schema.
-
-Create a Discord poll:
-
 ```
-symi message poll --channel discord \
   --target channel:123 \
   --poll-question "Snack?" \
   --poll-option Pizza --poll-option Sushi \

package/docs/cli/status.md

@@ -19,7 +19,6 @@ symi status --usage
 
 Notes:
 
-- `--deep` runs live probes (WhatsApp Web + Telegram + Discord + Google Chat + Slack + Signal).
 - Output includes per-agent session stores when multiple agents are configured.
 - Overview includes Gateway + node host service install/runtime status when available.
 - Overview includes update channel + git SHA (for source checkouts).

package/docs/concepts/architecture.md

@@ -12,7 +12,6 @@ Last updated: 2026-01-22
 ## Overview
 
 - A single long‑lived **Gateway** owns all messaging surfaces (WhatsApp via
-  Baileys, Telegram via grammY, Slack, Discord, Signal, iMessage, WebChat).
 - Control-plane clients (macOS app, CLI, web UI, automations) connect to the
   Gateway over **WebSocket** on the configured bind host (default
   `127.0.0.1:18789`).

package/docs/concepts/features.md

@@ -9,7 +9,6 @@ title: "Features"
 
 <Columns>
   <Card title="Channels" icon="message-square">
-    WhatsApp, Telegram, Discord, and iMessage with a single Gateway.
   </Card>
   <Card title="Plugins" icon="plug">
     Add Mattermost and more with extensions.
@@ -32,7 +31,6 @@ title: "Features"
 
 - WhatsApp integration via WhatsApp Web (Baileys)
 - Telegram bot support (grammY)
-- Discord bot support (channels.discord.js)
 - Mattermost bot support (plugin)
 - iMessage integration via local imsg CLI (macOS)
 - Agent bridge for Pi in RPC mode with tool streaming

package/docs/concepts/markdown-formatting.md

@@ -57,7 +57,6 @@ IR (schematic):
 ## Where it is used
 
 - Slack, Telegram, and Signal outbound adapters render from the IR.
-- Other channels (WhatsApp, iMessage, MS Teams, Discord) still use plain text or
   their own formatting rules, with Markdown table conversion applied before
   chunking when enabled.
 
@@ -74,13 +73,12 @@ Config keys:
 
 ```yaml
 channels:
-  discord:
-    markdown:
-      tables: code
-    accounts:
-      work:
-        markdown:
-          tables: off
+  markdown:
+    tables: code
+  accounts:
+    work:
+      markdown:
+        tables: off
 ```
 
 ## Chunking rules

package/docs/concepts/memory.md

@@ -203,9 +203,7 @@ out to QMD for retrieval. Key points:
   Default is DM-only (`deny` all, `allow` direct chats); loosen it to surface QMD
   hits in groups/channels.
   - `match.keyPrefix` matches the **normalized** session key (lowercased, with any
-    leading `agent:<id>:` stripped). Example: `discord:channel:`.
   - `match.rawKeyPrefix` matches the **raw** session key (lowercased), including
-    `agent:<id>:`. Example: `agent:main:discord:`.
   - Legacy: `match.keyPrefix: "agent:..."` is still treated as a raw-key prefix,
     but prefer `rawKeyPrefix` for clarity.
 - When `scope` denies a search, Symi logs a warning with the derived
@@ -238,9 +236,7 @@ memory: {
       rules: [
         { action: "allow", match: { chatType: "direct" } },
         // Normalized session-key prefix (strips `agent:<id>:`).
-        { action: "deny", match: { keyPrefix: "discord:channel:" } },
         // Raw session-key prefix (includes `agent:<id>:`).
-        { action: "deny", match: { rawKeyPrefix: "agent:main:discord:" } },
       ]
     },
     paths: [

package/docs/concepts/messages.md

@@ -52,7 +52,6 @@ Config (global default + per-channel overrides):
       byChannel: {
         whatsapp: 5000,
         slack: 1500,
-        discord: 1500,
       },
     },
   },

package/docs/concepts/models.md

@@ -104,7 +104,6 @@ You can switch models for the current session without restarting:
 Notes:
 
 - `/model` (and `/model list`) is a compact, numbered picker (model family + available providers).
-- On Discord, `/model` and `/models` open an interactive picker with provider and model dropdowns plus a Submit step.
 - `/model <#>` selects from that picker.
 - `/model status` is the detailed view (auth candidates and, when configured, provider endpoint `baseUrl` + `api` mode).
 - Model refs are parsed by splitting on the **first** `/`. Use `provider/model` when typing `/model <ref>`.