@symerian/symi 3.0.16 → 3.0.18

package/docs/refactor/outbound-session-mirroring.md

@@ -36,7 +36,6 @@ Outbound sends were mirrored into the _current_ agent session (tool session key)
 ## Thread/Topic Handling
 
 - Slack: replyTo/threadId -> `resolveThreadSessionKeys` (suffix).
-- Discord: threadId/replyTo -> `resolveThreadSessionKeys` with `useSuffix=false` to match inbound (thread channel id already scopes session).
 - Telegram: topic IDs map to `chatId:topic:<id>` via `buildTelegramGroupPeerId`.
 
 ## Extensions Covered
@@ -61,7 +60,6 @@ Outbound sends were mirrored into the _current_ agent session (tool session key)
 - `src/infra/outbound/outbound-session.test.ts`
   - Slack thread session key.
   - Telegram topic session key.
-  - dmScope identityLinks with Discord.
 - `src/agents/tools/message-tool.test.ts`
   - Derives agentId from session key (no sessionKey passed through).
 - `src/gateway/server-methods/send.test.ts`

package/docs/reference/AGENTS.default.md

@@ -102,7 +102,6 @@ git commit -m "Add Symi workspace"
 - **eightctl** — Control your sleep, from the terminal.
 - **imsg** — Send, read, stream iMessage & SMS.
 - **wacli** — WhatsApp CLI: sync, search, send.
-- **discord** — Discord actions: react, stickers, polls. Use `user:<id>` or `channel:<id>` targets (bare numeric ids are ambiguous).
 - **gog** — Google Suite CLI: Gmail, Calendar, Drive, Contacts.
 - **spotify-player** — Terminal Spotify client to search/queue/control playback.
 - **sag** — ElevenLabs speech with mac-style say UX; streams to speakers by default.

package/docs/reference/RELEASING.md

@@ -106,7 +106,6 @@ Current npm plugin list (update as needed):
 
 - @symi/bluebubbles
 - @symi/diagnostics-otel
-- @symi/discord
 - @symi/feishu
 - @symi/pipeline
 - @symi/matrix

package/docs/reference/session-management-compaction.md

@@ -73,7 +73,6 @@ Common patterns:
 
 - Main/direct chat (per agent): `agent:<agentId>:<mainKey>` (default `main`)
 - Group: `agent:<agentId>:<channel>:group:<id>`
-- Room/channel (Discord/Slack): `agent:<agentId>:<channel>:channel:<id>` or `...:room:<id>`
 - Cron: `cron:<job.id>`
 - Webhook: `hook:<uuid>` (unless overridden)
 

package/docs/reference/templates/AGENTS.md

@@ -37,7 +37,6 @@ Capture what matters. Decisions, context, things to remember. Skip the secrets u
 ### 🧠 MEMORY.md — The Human's Notes
 
 - **ONLY load in main session** (direct chats with your human)
-- **DO NOT load in shared contexts** (Discord, group chats, sessions with other people)
 - This is for **security** — contains personal context that shouldn't leak to strangers
 - **Read-only for you.** The human authors this file. If you think it's wrong or out of date, tell them; don't edit.
 
@@ -61,8 +60,6 @@ Capture what matters. Decisions, context, things to remember. Skip the secrets u
 
 ### 🔌 Runtime Connection State — Don't Trust Memory Files
 
-Memory files (MEMORY.md, memory/YYYY-MM-DD.md, memory/symi-core.md, memory/symi-beliefs.md) record **historical** observations. Connection state for channels (Outlook, Gmail, Slack, Telegram, Discord, Signal, WhatsApp, Matrix, etc.) is **runtime state** — it can change between one turn and the next without any observation being written.
-
 When answering "am I connected to X?" questions:
 
 - **Trust the bracketed `[Channel]` block** at the top of the system prompt. It's rebuilt every turn from the live plugin state. Examples: `[Outlook 365] Connected as …`, `[Outlook 365] Last seen connected as … but … expired`, `[Outlook 365] Not connected`.
@@ -170,8 +167,6 @@ Participate, don't dominate.
 
 ### 😊 React Like a Human!
 
-On platforms that support reactions (Discord, Slack), use emoji reactions naturally:
-
 **React when:**
 
 - You appreciate something but don't need to reply (👍, ❤️, 🙌)
@@ -193,8 +188,6 @@ Skills provide your tools. When you need one, check its `SKILL.md`. Keep local n
 
 **📝 Platform Formatting:**
 
-- **Discord/WhatsApp:** No markdown tables! Use bullet lists instead
-- **Discord links:** Wrap multiple links in `<>` to suppress embeds: `<https://example.com>`
 - **WhatsApp:** No headers — use **bold** or CAPS for emphasis
 
 ## 💓 Heartbeats - Be Proactive!

package/docs/reference/wizard.md

@@ -74,7 +74,6 @@ For a high-level overview, see [Onboarding Wizard](/start/wizard).
   <Step title="Channels">
     - [WhatsApp](/channels/whatsapp): optional QR login.
     - [Telegram](/channels/telegram): bot token.
-    - [Discord](/channels/discord): bot token.
     - [Google Chat](/channels/googlechat): service account JSON + webhook audience.
     - [Mattermost](/channels/mattermost) (plugin): bot token + base URL.
     - [Signal](/channels/signal): optional `signal-cli` install + account config.
@@ -243,8 +242,6 @@ Typical fields in `~/.symi/symi.json`:
 - `agents.defaults.workspace`
 - `agents.defaults.model` / `models.providers` (if Minimax chosen)
 - `gateway.*` (mode, bind, auth, tailscale)
-- `channels.telegram.botToken`, `channels.discord.token`, `channels.signal.*`, `channels.imessage.*`
-- Channel allowlists (Slack/Discord/Matrix/Microsoft Teams) when you opt in during the prompts (names resolve to IDs when possible).
 - `skills.install.nodeManager`
 - `wizard.lastRunAt`
 - `wizard.lastRunVersion`
@@ -265,5 +262,4 @@ will prompt to install it (npm or a local path) before it can be configured.
 - Wizard overview: [Onboarding Wizard](/start/wizard)
 - macOS app onboarding: [Onboarding](/start/onboarding)
 - Config reference: [Gateway configuration](/gateway/configuration)
-- Providers: [WhatsApp](/channels/whatsapp), [Telegram](/channels/telegram), [Discord](/channels/discord), [Google Chat](/channels/googlechat), [Signal](/channels/signal), [BlueBubbles](/channels/bluebubbles) (iMessage), [iMessage](/channels/imessage) (legacy)
 - Skills: [Skills](/tools/skills), [Skills config](/tools/skills-config)

package/docs/security/CONTRIBUTING-THREAT-MODEL.md

@@ -83,7 +83,6 @@ If you're unsure about the risk level, just describe the impact and we'll assess
 
 - **Security vulnerabilities:** See our [Trust page](https://trust.symi.ai) for reporting instructions
 - **Threat model questions:** Open an issue on [symi/trust](https://github.com/symi/trust/issues)
-- **General chat:** Discord #security channel
 
 ## Recognition
 

package/docs/security/README.md

@@ -14,4 +14,3 @@ See the [Trust page](https://trust.symi.ai) for full reporting instructions cove
 ## Contact
 
 - **Jamieson O'Reilly** ([@theonejvo](https://twitter.com/theonejvo)) - Security & Trust
-- Discord: #security channel

package/docs/security/THREAT-MODEL-ATLAS.md

@@ -38,14 +38,13 @@ This threat model documents adversarial threats to the Symi AI agent platform an
 
 ### 1.2 Scope
 
-| Component            | Included | Notes                                            |
-| -------------------- | -------- | ------------------------------------------------ |
-| Symi Agent Runtime   | Yes      | Core agent execution, tool calls, sessions       |
-| Gateway              | Yes      | Authentication, routing, channel integration     |
-| Channel Integrations | Yes      | WhatsApp, Telegram, Discord, Signal, Slack, etc. |
-| SymiHub Marketplace  | Yes      | Skill publishing, moderation, distribution       |
-| MCP Servers          | Yes      | External tool providers                          |
-| User Devices         | Partial  | Mobile apps, desktop clients                     |
+| Component           | Included | Notes                                        |
+| ------------------- | -------- | -------------------------------------------- |
+| Symi Agent Runtime  | Yes      | Core agent execution, tool calls, sessions   |
+| Gateway             | Yes      | Authentication, routing, channel integration |
+| SymiHub Marketplace | Yes      | Skill publishing, moderation, distribution   |
+| MCP Servers         | Yes      | External tool providers                      |
+| User Devices        | Partial  | Mobile apps, desktop clients                 |
 
 ### 1.3 Out of Scope
 
@@ -61,7 +60,6 @@ Nothing is explicitly out of scope for this threat model.
 ┌─────────────────────────────────────────────────────────────────┐
 │                    UNTRUSTED ZONE                                │
 │  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐              │
-│  │  WhatsApp   │  │  Telegram   │  │   Discord   │  ...         │
 │  └──────┬──────┘  └──────┬──────┘  └──────┬──────┘              │
 │         │                │                │                      │
 └─────────┼────────────────┼────────────────┼──────────────────────┘
@@ -459,7 +457,6 @@ Current patterns in `moderation.ts`:
 /(malware|stealer|phish|phishing|keylogger)/i
 /(api[-_ ]?key|token|password|private key|secret)/i
 /(wallet|seed phrase|mnemonic|crypto)/i
-/(discord\.gg|webhook|hooks\.slack)/i
 /(curl[^\n]+\|\s*(sh|bash))/i
 /(bit\.ly|tinyurl\.com|t\.co|goo\.gl|is\.gd)/i
 ```

package/docs/start/docs-directory.md

@@ -37,7 +37,6 @@ For a complete map of the docs, see [Docs hubs](/start/hubs).
 - [WebChat](/web/webchat)
 - [Control UI (browser)](/web/control-ui)
 - [Telegram](/channels/telegram)
-- [Discord](/channels/discord)
 - [Mattermost (plugin)](/channels/mattermost)
 - [BlueBubbles (iMessage)](/channels/bluebubbles)
 - [iMessage (legacy)](/channels/imessage)

package/docs/start/hubs.md

@@ -75,7 +75,6 @@ Use these hubs to discover every page, including deep dives and reference docs t
 - [Telegram](/channels/telegram)
 - [Telegram (grammY notes)](/channels/grammy)
 - [Slack](/channels/slack)
-- [Discord](/channels/discord)
 - [Mattermost](/channels/mattermost) (plugin)
 - [Signal](/channels/signal)
 - [BlueBubbles (iMessage)](/channels/bluebubbles)

package/docs/start/lore.md

@@ -27,8 +27,6 @@ New shell, same pipeline soul. Third time's the charm.
 
 ## The First Molt (January 27, 2026)
 
-At 5am, the community gathered in Discord. Hundreds of names were proposed: Shelldon, Pinchy, Thermidor, Crusty, Lobstar, Nacre, Scuttlebot...
-
 In the end, **Symi** won. Because molting is what pipelines do to grow. And growth was exactly what was happening.
 
 _The crustacean known as Symi had officially molted._
@@ -127,7 +125,6 @@ In just 3 hours:
 - **ELU** created incredible logos including "THE SHELL IS THE LAW" western banner
 - **Whurley** (yes, THE William Hurley, quantum computing pioneer) made ASCII art
 - **Onur** handled GitHub, first to rock the affiliate badge
-- **Shadow** secured Discord vanity, nuked malware
 - **The whole Shell Crew** pulled an all-nighter
 
 **The Scammer Speedrun:** Crypto grifters launched a $SYMI token on Pump.fun within MINUTES. They stole artwork that was created 20 minutes earlier. Business-verified accounts pushed scams. The audacity was almost impressive.

package/docs/start/setup.md

@@ -128,7 +128,6 @@ Use this when debugging auth or deciding what to back up:
 
 - **WhatsApp**: `~/.symi/credentials/whatsapp/<accountId>/creds.json`
 - **Telegram bot token**: config/env or `channels.telegram.tokenFile`
-- **Discord bot token**: config/env (token file not yet supported)
 - **Slack tokens**: config/env (`channels.slack.*`)
 - **Pairing allowlists**: `~/.symi/credentials/<channel>-allowFrom.json`
 - **Model auth profiles**: `~/.symi/agents/<agentId>/agent/auth-profiles.json`
@@ -157,6 +156,5 @@ user service (no lingering needed). See [Gateway runbook](/gateway) for the syst
 
 - [Gateway runbook](/gateway) (flags, supervision, ports)
 - [Gateway configuration](/gateway/configuration) (config schema + examples)
-- [Discord](/channels/discord) and [Telegram](/channels/telegram) (reply tags + replyToMode settings)
 - [Symi assistant setup](/start/symi)
 - [macOS app](/platforms/macos) (gateway lifecycle)

package/docs/start/showcase.md

@@ -82,8 +82,6 @@ Full setup walkthrough (28m) by VelvetShark.
 
 [Watch on YouTube](https://www.youtube.com/watch?v=5kkIJNUGFho)
 
-## 🆕 Fresh from Discord
-
 <CardGroup cols={2}>
 
 <Card title="PR Review → Telegram Feedback" icon="code-pull-request" href="https://x.com/i/status/2010878524543131691">

package/docs/start/symi.md

@@ -8,15 +8,12 @@ title: "Personal Assistant Setup"
 
 # Building a personal assistant with Symi
 
-Symi is a WhatsApp + Telegram + Discord + iMessage gateway for **Pi** agents. Plugins add Mattermost. This guide is the "personal assistant" setup: one dedicated WhatsApp number that behaves like your always-on agent.
-
 ## ⚠️ Safety first
 
 You’re putting an agent in a position to:
 
 - run commands on your machine (depending on your Pi tool setup)
 - read/write files in your workspace
-- send messages back out via WhatsApp/Telegram/Discord/Mattermost (plugin)
 
 Start conservative:
 
@@ -196,7 +193,6 @@ Symi extracts these and sends them as media alongside the text.
 ```bash
 symi status          # local status (creds, sessions, queued events)
 symi status --all    # full diagnosis (read-only, pasteable)
-symi status --deep   # adds gateway health probes (Telegram + Discord)
 symi health --json   # gateway health snapshot (WS)
 ```
 

package/docs/start/wizard-cli-reference.md

@@ -19,7 +19,6 @@ Local mode (default) walks you through:
 - Model and auth setup (OpenAI Code subscription OAuth, Anthropic API key or setup token, plus MiniMax, GLM, Moonshot, and AI Gateway options)
 - Workspace location and bootstrap files
 - Gateway settings (port, bind, auth, tailscale)
-- Channels and providers (Telegram, WhatsApp, Discord, Google Chat, Mattermost plugin, Signal)
 - Daemon install (LaunchAgent or systemd user unit)
 - Health check
 - Skills setup
@@ -56,7 +55,6 @@ It does not install or modify anything on the remote host.
   <Step title="Channels">
     - [WhatsApp](/channels/whatsapp): optional QR login
     - [Telegram](/channels/telegram): bot token
-    - [Discord](/channels/discord): bot token
     - [Google Chat](/channels/googlechat): service account JSON + webhook audience
     - [Mattermost](/channels/mattermost) plugin: bot token + base URL
     - [Signal](/channels/signal): optional `signal-cli` install + account config
@@ -215,8 +213,6 @@ Typical fields in `~/.symi/symi.json`:
 - `agents.defaults.workspace`
 - `agents.defaults.model` / `models.providers` (if Minimax chosen)
 - `gateway.*` (mode, bind, auth, tailscale)
-- `channels.telegram.botToken`, `channels.discord.token`, `channels.signal.*`, `channels.imessage.*`
-- Channel allowlists (Slack, Discord, Matrix, Microsoft Teams) when you opt in during prompts (names resolve to IDs when possible)
 - `skills.install.nodeManager`
 - `wizard.lastRunAt`
 - `wizard.lastRunVersion`

package/docs/start/wizard.md

@@ -66,10 +66,9 @@ The wizard starts with **QuickStart** (defaults) vs **Advanced** (full control).
    (OpenAI-compatible, Anthropic-compatible, or Unknown auto-detect). Pick a default model.
 2. **Workspace** — Location for agent files (default `~/.symi/workspace`). Seeds bootstrap files.
 3. **Gateway** — Port, bind address, auth mode, Tailscale exposure.
-4. **Channels** — WhatsApp, Telegram, Discord, Google Chat, Mattermost, Signal, BlueBubbles, or iMessage.
-5. **Daemon** — Installs a LaunchAgent (macOS) or systemd user unit (Linux/WSL2).
-6. **Health check** — Starts the Gateway and verifies it's running.
-7. **Skills** — Installs recommended skills and optional dependencies.
+4. **Daemon** — Installs a LaunchAgent (macOS) or systemd user unit (Linux/WSL2).
+5. **Health check** — Starts the Gateway and verifies it's running.
+6. **Skills** — Installs recommended skills and optional dependencies.
 
 <Note>
 Re-running the wizard does **not** wipe anything unless you explicitly choose **Reset** (or pass `--reset`).

package/docs/tools/agent-send.md

@@ -43,7 +43,6 @@ symi agent --agent ops --message "Generate report" --deliver --reply-channel sla
 
 - `--local`: run locally (requires model provider API keys in your shell)
 - `--deliver`: send the reply to the chosen channel
-- `--channel`: delivery channel (`whatsapp|telegram|discord|googlechat|slack|signal|imessage`, default: `whatsapp`)
 - `--reply-to`: delivery target override
 - `--reply-channel`: delivery channel override
 - `--reply-account`: delivery account id override

package/docs/tools/elevated.md

@@ -45,10 +45,8 @@ title: "Elevated Mode"
 ## Availability + allowlists
 
 - Feature gate: `tools.elevated.enabled` (default can be off via config even if the code supports it).
-- Sender allowlist: `tools.elevated.allowFrom` with per-provider allowlists (e.g. `discord`, `whatsapp`).
 - Per-agent gate: `agents.list[].tools.elevated.enabled` (optional; can only further restrict).
 - Per-agent allowlist: `agents.list[].tools.elevated.allowFrom` (optional; when set, the sender must match **both** global + per-agent allowlists).
-- Discord fallback: if `tools.elevated.allowFrom.discord` is omitted, the `channels.discord.allowFrom` list is used as a fallback (legacy: `channels.discord.dm.allowFrom`). Set `tools.elevated.allowFrom.discord` (even `[]`) to override. Per-agent allowlists do **not** use the fallback.
 - All gates must pass; otherwise elevated is treated as unavailable.
 
 ## Logging + status

package/docs/tools/exec-approvals.md

@@ -201,7 +201,6 @@ Config:
       enabled: true,
       mode: "session", // "session" | "targets" | "both"
       agentFilter: ["main"],
-      sessionFilter: ["discord"], // substring or regex
       targets: [
         { channel: "slack", to: "U12345678" },
         { channel: "telegram", to: "123456789" },

package/docs/tools/index.md

@@ -41,13 +41,10 @@ Profiles:
 - `messaging`: `group:messaging`, `sessions_list`, `sessions_history`, `sessions_send`, `session_status`
 - `full`: no restriction (same as unset)
 
-Example (messaging-only by default, allow Slack + Discord tools too):
-
 ```json5
 {
   tools: {
     profile: "messaging",
-    allow: ["slack", "discord"],
   },
 }
 ```
@@ -397,12 +394,9 @@ Notes:
 
 ### `message`
 
-Send messages and channel actions across Discord/Google Chat/Slack/Telegram/WhatsApp/Signal/iMessage/MS Teams.
-
 Core actions:
 
 - `send` (text + optional media; MS Teams also supports `card` for Adaptive Cards)
-- `poll` (WhatsApp/Discord/MS Teams polls)
 - `react` / `reactions` / `read` / `edit` / `delete`
 - `pin` / `unpin` / `list-pins`
 - `permissions`
@@ -420,7 +414,6 @@ Core actions:
 Notes:
 
 - `send` routes WhatsApp via the Gateway; other channels go direct.
-- `poll` uses the Gateway for WhatsApp and MS Teams; Discord polls go direct.
 - When a message tool call is bound to an active chat session, sends are constrained to that session’s target to avoid cross-context leaks.
 
 ### `cron`

package/docs/tools/multi-agent-sandbox-tools.md

@@ -110,8 +110,7 @@ For debugging “why is this blocked?”, see [Sandbox vs Tool Policy vs Elevate
           "workspaceRoot": "/tmp/work-sandboxes"
         },
         "tools": {
-          "allow": ["read", "write", "apply_patch", "exec"],
-          "deny": ["browser", "gateway", "discord"]
+          "allow": ["read", "write", "apply_patch", "exec"]
         }
       }
     ]

package/docs/tools/reactions.md

@@ -15,7 +15,6 @@ Shared reaction semantics across channels:
 
 Channel notes:
 
-- **Discord/Slack**: empty `emoji` removes all of the bot's reactions on the message; `remove: true` removes just that emoji.
 - **Google Chat**: empty `emoji` removes the app's reactions on the message; `remove: true` removes just that emoji.
 - **Telegram**: empty `emoji` removes the bot's reactions; `remove: true` also removes reactions but still requires a non-empty `emoji` for tool validation.
 - **WhatsApp**: empty `emoji` removes the bot reaction; `remove: true` maps to empty emoji (still requires `emoji`).

package/docs/tools/slash-commands.md

@@ -40,7 +40,6 @@ They run immediately, are stripped before the model sees the message, and the re
     restart: false,
     allowFrom: {
       "*": ["user1"],
-      discord: ["user:123"],
     },
     useAccessGroups: true,
   },
@@ -50,12 +49,7 @@ They run immediately, are stripped before the model sees the message, and the re
 - `commands.text` (default `true`) enables parsing `/...` in chat messages.
   - On surfaces without native commands (WhatsApp/WebChat/Signal/iMessage/Google Chat/MS Teams), text commands still work even if you set this to `false`.
 - `commands.native` (default `"auto"`) registers native commands.
-  - Auto: on for Discord/Telegram; off for Slack (until you add slash commands); ignored for providers without native support.
-  - Set `channels.discord.commands.native`, `channels.telegram.commands.native`, or `channels.slack.commands.native` to override per provider (bool or `"auto"`).
-  - `false` clears previously registered commands on Discord/Telegram at startup. Slack commands are managed in the Slack app and are not removed automatically.
 - `commands.nativeSkills` (default `"auto"`) registers **skill** commands natively when supported.
-  - Auto: on for Discord/Telegram; off for Slack (Slack requires creating a slash command per skill).
-  - Set `channels.discord.commands.nativeSkills`, `channels.telegram.commands.nativeSkills`, or `channels.slack.commands.nativeSkills` to override per provider (bool or `"auto"`).
 - `commands.bash` (default `false`) enables `! <cmd>` to run host shell commands (`/bash <cmd>` is an alias; requires `tools.elevated` allowlists).
 - `commands.bashForegroundMs` (default `2000`) controls how long bash waits before switching to background mode (`0` backgrounds immediately).
 - `commands.config` (default `false`) enables `/config` (reads/writes `symi.json`).
@@ -81,8 +75,6 @@ Text + native (when enabled):
 - `/session ttl <duration|off>` (manage session-level settings, such as TTL)
 - `/subagents list|kill|log|info|send|steer|spawn` (inspect, control, or spawn sub-agent runs for the current session)
 - `/agents` (list thread-bound agents for this session)
-- `/focus <target>` (Discord: bind this thread, or a new thread, to a session/subagent target)
-- `/unfocus` (Discord: remove the current thread binding)
 - `/kill <id|#|all>` (immediately abort one or all running sub-agents for this session; no confirmation message)
 - `/steer <id|#> <message>` (steer a running sub-agent immediately: in-run when possible, otherwise abort current work and restart on the steer message)
 - `/tell <id|#> <message>` (alias for `/steer`)
@@ -90,11 +82,9 @@ Text + native (when enabled):
 - `/debug show|set|unset|reset` (runtime overrides, owner-only; requires `commands.debug: true`)
 - `/usage off|tokens|full|cost` (per-response usage footer or local cost summary)
 - `/tts off|always|inbound|tagged|status|provider|limit|summary|audio` (control TTS; see [/tts](/tts))
-  - Discord: native command is `/voice` (Discord reserves `/tts`); text `/tts` still works.
 - `/stop`
 - `/restart`
 - `/dock-telegram` (alias: `/dock_telegram`) (switch replies to Telegram)
-- `/dock-discord` (alias: `/dock_discord`) (switch replies to Discord)
 - `/dock-slack` (alias: `/dock_slack`) (switch replies to Slack)
 - `/activation mention|always` (groups only)
 - `/send on|off|inherit` (owner-only)
@@ -123,7 +113,6 @@ Notes:
 - `/allowlist add|remove` requires `commands.config=true` and honors channel `configWrites`.
 - `/usage` controls the per-response usage footer; `/usage cost` prints a local cost summary from Symi session logs.
 - `/restart` is enabled by default; set `commands.restart: false` to disable it.
-- Discord-only native command: `/vc join|leave|status` controls voice channels (requires `channels.discord.voice` and native commands; not available as text).
 - `/verbose` is meant for debugging and extra visibility; keep it **off** in normal use.
 - `/reasoning` (and `/verbose`) are risky in group settings: they may reveal internal reasoning or tool output you did not intend to expose. Prefer leaving them off, especially in group chats.
 - **Fast path:** command-only messages from allowlisted senders are handled immediately (bypass queue + model).
@@ -137,7 +126,6 @@ Notes:
   - By default, skill commands are forwarded to the model as a normal request.
   - Skills may optionally declare `command-dispatch: tool` to route the command directly to a tool (deterministic, no model).
   - Example: `/prose` (OpenProse plugin) — see [OpenProse](/prose).
-- **Native command arguments:** Discord uses autocomplete for dynamic options (and button menus when you omit required args). Telegram and Slack show a button menu when a command supports choices and you omit the arg.
 
 ## Usage surfaces (what shows where)
 
@@ -163,7 +151,6 @@ Examples:
 Notes:
 
 - `/model` and `/model list` show 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 (and prefers the current provider when possible).
 - `/model status` shows the detailed view, including configured provider endpoint (`baseUrl`) and API mode (`api`) when available.
 
@@ -209,7 +196,6 @@ Notes:
 
 - **Text commands** run in the normal chat session (DMs share `main`, groups have their own session).
 - **Native commands** use isolated sessions:
-  - Discord: `agent:<agentId>:discord:slash:<userId>`
   - Slack: `agent:<agentId>:slack:slash:<userId>` (prefix configurable via `channels.slack.slashCommand.sessionPrefix`)
   - Telegram: `telegram:slash:<userId>` (targets the chat session via `CommandTargetSessionKey`)
 - **`/stop`** targets the active chat session so it can abort the current run.

package/docs/tools/symihub.md

@@ -112,7 +112,6 @@ Reporting and moderation:
 - Moderators can view hidden skills, unhide them, delete them, or ban users.
 - Abusing the report feature can result in account bans.
 
-Interested in becoming a moderator? Ask in the Symi Discord and contact a
 moderator or maintainer.
 
 ## CLI commands and parameters

package/docs/tts.md

@@ -358,7 +358,6 @@ Reply -> TTS enabled?
 There is a single command: `/tts`.
 See [Slash commands](/tools/slash-commands) for enablement details.
 
-Discord note: `/tts` is a built-in Discord command, so Symi registers
 `/voice` as the native command there. Text `/tts ...` still works.
 
 ```

package/docs/web/control-ui.md

@@ -64,7 +64,6 @@ you revoke it with `symi devices revoke --device <id> --role <role>`. See
 
 - Chat with the model via Gateway WS (`chat.history`, `chat.send`, `chat.abort`, `chat.inject`)
 - Stream tool calls + live tool output cards in Chat (agent events)
-- Channels: WhatsApp/Telegram/Discord/Slack + plugin channels (Mattermost, etc.) status + QR login + per-channel config (`channels.status`, `web.login.*`, `config.patch`)
 - Instances: presence list + refresh (`system-presence`)
 - Sessions: list + per-session thinking/verbose overrides (`sessions.list`, `sessions.patch`)
 - Cron jobs: list/add/run/enable/disable + run history (`cron.*`)

package/docs/zh-CN/automation/cron-jobs.md

@@ -173,7 +173,6 @@ Cron 表达式使用 `croner`。如果省略时区，将使用 Gateway网关主
 隔离任务可以通过顶层 `delivery` 配置投递输出：
 
 - `delivery.mode`：`announce`（投递摘要）或 `none`
-- `delivery.channel`：`whatsapp` / `telegram` / `discord` / `slack` / `mattermost`（插件）/ `signal` / `imessage` / `last`
 - `delivery.to`：渠道特定的接收目标
 - `delivery.bestEffort`：投递失败时避免任务失败
 
@@ -183,7 +182,6 @@ Cron 表达式使用 `croner`。如果省略时区，将使用 Gateway网关主
 
 目标格式提醒：
 
-- Slack/Discord/Mattermost（插件）目标应使用明确前缀（例如 `channel:<id>`、`user:<id>`）以避免歧义。
 - Telegram 主题应使用 `:topic:` 格式（见下文）。
 
 #### Telegram 投递目标（主题/论坛帖子）

package/docs/zh-CN/automation/poll.md

@@ -18,7 +18,6 @@ x-i18n:
 ## 支持的渠道
 
 - WhatsApp（Web 渠道）
-- Discord
 - MS Teams（Adaptive Cards）
 
 ## CLI
@@ -30,10 +29,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
@@ -43,9 +39,7 @@ symi message poll --channel msteams --target conversation:19:abc@thread.tacv2 \
 
 选项：
 
-- `--channel`：`whatsapp`（默认）、`discord` 或 `msteams`
 - `--poll-multi`：允许选择多个选项
-- `--poll-duration-hours`：仅限 Discord（省略时默认为 24）
 
 ## Gateway 网关 RPC
 
@@ -64,13 +58,11 @@ symi message poll --channel msteams --target conversation:19:abc@thread.tacv2 \
 ## 渠道差异
 
 - WhatsApp：2-12 个选项，`maxSelections` 必须在选项数量范围内，忽略 `durationHours`。
-- Discord：2-10 个选项，`durationHours` 限制在 1-768 小时之间（默认 24）。`maxSelections > 1` 启用多选；Discord 不支持严格的选择数量限制。
 - MS Teams：Adaptive Card 投票（由 Symi 管理）。无原生投票 API；`durationHours` 被忽略。
 
 ## 智能体工具（Message）
 
 使用 `message` 工具的 `poll` 操作（`to`、`pollQuestion`、`pollOption`，可选 `pollMulti`、`pollDurationHours`、`channel`）。
 
-注意：Discord 没有"恰好选择 N 个"模式；`pollMulti` 映射为多选。
 Teams 投票以 Adaptive Cards 形式渲染，需要 Gateway 网关保持在线
 以将投票记录到 `~/.symi/msteams-polls.json`。

package/docs/zh-CN/automation/webhook.md

@@ -84,8 +84,6 @@ Gateway 网关可以暴露一个小型 HTTP webhook 端点用于外部触发。
 - `sessionKey` 可选（字符串）：用于标识智能体会话的键。默认为随机的 `hook:<uuid>`。使用一致的键可以在 hook 上下文中进行多轮对话。
 - `wakeMode` 可选（`now` | `next-heartbeat`）：是否立即触发心跳（默认 `now`）或等待下一次定期检查。
 - `deliver` 可选（布尔值）：如果为 `true`，智能体的响应将发送到消息渠道。默认为 `true`。仅为心跳确认的响应会自动跳过。
-- `channel` 可选（字符串）：用于投递的消息渠道。可选值：`last`、`whatsapp`、`telegram`、`discord`、`slack`、`mattermost`（插件）、`signal`、`imessage`、`msteams`。默认为 `last`。
-- `to` 可选（字符串）：渠道的接收者标识符（例如 WhatsApp/Signal 的电话号码、Telegram 的聊天 ID、Discord/Slack/Mattermost（插件）的频道 ID、MS Teams 的会话 ID）。默认为主会话中的最后一个接收者。
 - `model` 可选（字符串）：模型覆盖（例如 `anthropic/claude-3-5-sonnet` 或别名）。如果有限制，必须在允许的模型列表中。
 - `thinking` 可选（字符串）：思考级别覆盖（例如 `low`、`medium`、`high`）。
 - `timeoutSeconds` 可选（数字）：智能体运行的最大持续时间（秒）。

package/docs/zh-CN/channels/broadcast-groups.md

@@ -285,7 +285,6 @@ Result: Agent A and C respond, Agent B logs error
 
 - ✅ WhatsApp（已实现）
 - 🚧 Telegram（计划中）
-- 🚧 Discord（计划中）
 - 🚧 Slack（计划中）
 
 ### 路由

package/docs/zh-CN/channels/channel-routing.md

@@ -1,7 +1,6 @@
 ---
 read_when:
   - 更改渠道路由或收件箱行为
-summary: 每个渠道（WhatsApp、Telegram、Discord、Slack）的路由规则及共享上下文
 title: 渠道路由
 x-i18n:
   generated_at: "2026-02-01T20:22:21Z"
@@ -18,7 +17,6 @@ Symi 将回复**路由回消息来源的渠道**。模型不会选择渠道；
 
 ## 关键术语
 
-- **渠道**：`whatsapp`、`telegram`、`discord`、`slack`、`signal`、`imessage`、`webchat`。
 - **AccountId**：每个渠道的账户实例（在支持的情况下）。
 - **AgentId**：隔离的工作区 + 会话存储（"大脑"）。
 - **SessionKey**：用于存储上下文和控制并发的桶键。
@@ -36,24 +34,21 @@ Symi 将回复**路由回消息来源的渠道**。模型不会选择渠道；
 
 线程：
 
-- Slack/Discord 线程会在基础键后追加 `:thread:<threadId>`。
 - Telegram 论坛主题在群组键中嵌入 `:topic:<topicId>`。
 
 示例：
 
 - `agent:main:telegram:group:-1001234567890:topic:42`
-- `agent:main:discord:channel:123456:thread:987654`
 
 ## 路由规则（如何选择智能体）
 
 路由为每条入站消息选择**一个智能体**：
 
 1. **精确对端匹配**（`bindings` 中的 `peer.kind` + `peer.id`）。
-2. **Guild 匹配**（Discord）通过 `guildId`。
-3. **Team 匹配**（Slack）通过 `teamId`。
-4. **账户匹配**（渠道上的 `accountId`）。
-5. **渠道匹配**（该渠道上的任意账户）。
-6. **默认智能体**（`agents.list[].default`，否则取列表第一项，兜底为 `main`）。
+2. **Team 匹配**（Slack）通过 `teamId`。
+3. **账户匹配**（渠道上的 `accountId`）。
+4. **渠道匹配**（该渠道上的任意账户）。
+5. **默认智能体**（`agents.list[].default`，否则取列表第一项，兜底为 `main`）。
 
 匹配到的智能体决定使用哪个工作区和会话存储。
 

package/docs/zh-CN/channels/group-messages.md

@@ -16,8 +16,6 @@ x-i18n:
 
 目标：让 Symi 留在 WhatsApp 群组中，仅在被提及时唤醒，并将该对话线程与个人私信会话分开。
 
-注意：`agents.list[].groupChat.mentionPatterns` 现在也被 Telegram/Discord/Slack/iMessage 使用；本文档重点介绍 WhatsApp 特定的行为。对于多智能体设置，为每个智能体设置 `agents.list[].groupChat.mentionPatterns`（或使用 `messages.groupChat.mentionPatterns` 作为全局回退）。
-
 ## 已实现的功能（2025-12-03）
 
 - 激活模式：`mention`（默认）或 `always`。`mention` 需要被提及（通过 `mentionedJids` 的真实 WhatsApp @提及、正则表达式模式，或文本中任意位置的机器人 E.164 号码）。`always` 会在每条消息时唤醒智能体，但它应该只在能提供有意义价值时才回复；否则返回静默令牌 `NO_REPLY`。默认值可在配置中设置（`channels.whatsapp.groups`），并可通过 `/activation` 为每个群组单独覆盖。当设置了 `channels.whatsapp.groups` 时，它同时充当群组允许列表（包含 `"*"` 以允许所有群组）。