@symerian/symi 3.0.16 → 3.0.18

package/docs/gateway/configuration-reference.md

@@ -35,7 +35,6 @@ All channels support DM policies and group policies:
 <Note>
 `channels.defaults.groupPolicy` sets the default when a provider's `groupPolicy` is unset.
 Pairing codes expire after 1 hour. Pending DM pairing requests are capped at **3 per channel**.
-Slack/Discord have a special fallback: if their provider section is missing entirely, runtime group policy can resolve to `open` (with a startup warning).
 </Note>
 
 ### Channel model overrides
@@ -46,7 +45,6 @@ Use `channels.modelByChannel` to pin specific channel IDs to a model. Values acc
 {
   channels: {
     modelByChannel: {
-      discord: {
         "123456789012345678": "anthropic/claude-opus-4-6",
       },
       slack: {
@@ -176,12 +174,9 @@ WhatsApp runs through the gateway's web channel (Baileys Web). It starts automat
 - Telegram stream previews use `sendMessage` + `editMessageText` (works in direct and group chats).
 - Retry policy: see [Retry policy](/concepts/retry).
 
-### Discord
-
 ```json5
 {
   channels: {
-    discord: {
       enabled: true,
       token: "your-bot-token",
       mediaMaxMb: 8,
@@ -258,13 +253,10 @@ WhatsApp runs through the gateway's web channel (Baileys Web). It starts automat
 }
 ```
 
-- Token: `channels.discord.token`, with `DISCORD_BOT_TOKEN` as fallback for the default account.
 - Use `user:<id>` (DM) or `channel:<id>` (guild channel) for delivery targets; bare numeric IDs are rejected.
 - Guild slugs are lowercase with spaces replaced by `-`; channel keys use the slugged name (no `#`). Prefer guild IDs.
 - Bot-authored messages are ignored by default. `allowBots: true` enables them (own messages still filtered).
 - `maxLinesPerMessage` (default 17) splits tall messages even when under 2000 chars.
-- `channels.discord.ui.components.accentColor` sets the accent color for Discord components v2 containers.
-- `channels.discord.voice` enables Discord voice channel conversations and optional auto-join + TTS overrides.
 
 **Reaction notification modes:** `off` (none), `own` (bot's messages, default), `all` (all messages), `allowlist` (from `guilds.<id>.users` on all messages).
 
@@ -481,8 +473,6 @@ Run multiple accounts per channel (each with its own `accountId`):
 
 ### Group chat mention gating
 
-Group messages default to **require mention** (metadata mention or regex patterns). Applies to WhatsApp, Telegram, Discord, Google Chat, and iMessage group chats.
-
 **Mention types:**
 
 - **Metadata mentions**: Native platform @-mentions. Ignored in WhatsApp self-chat mode.
@@ -519,8 +509,6 @@ Group messages default to **require mention** (metadata mention or regex pattern
 
 Resolution: per-DM override → provider default → no limit (all retained).
 
-Supported: `telegram`, `whatsapp`, `discord`, `slack`, `signal`, `imessage`, `msteams`.
-
 #### Self-chat mode
 
 Include your own number in `allowFrom` to enable self-chat mode (ignores native @-mentions, only responds to text patterns):
@@ -558,7 +546,6 @@ Include your own number in `allowFrom` to enable self-chat mode (ignores native
     restart: false, // allow /restart + gateway restart tool
     allowFrom: {
       "*": ["user1"],
-      discord: ["user:123"],
     },
     useAccessGroups: true,
   },
@@ -568,8 +555,6 @@ Include your own number in `allowFrom` to enable self-chat mode (ignores native
 <Accordion title="Command details">
 
 - Text commands must be **standalone** messages with leading `/`.
-- `native: "auto"` turns on native commands for Discord/Telegram, leaves Slack off.
-- Override per channel: `channels.discord.commands.native` (bool or `"auto"`). `false` clears previously registered commands.
 - `channels.telegram.customCommands` adds extra Telegram bot menu entries.
 - `bash: true` enables `! <cmd>` for host shell. Requires `tools.elevated.enabled` and sender in `tools.elevated.allowFrom.<channel>`.
 - `config: true` enables `/config` (reads/writes `symi.json`).
@@ -766,7 +751,6 @@ Periodic heartbeat runs.
         includeReasoning: false,
         session: "main",
         to: "+15555550123",
-        target: "last", // last | whatsapp | telegram | discord | ... | none
         prompt: "Read SYMIPULSE.md if it exists...",
         ackMaxChars: 300,
         suppressToolErrorWarnings: false,
@@ -866,7 +850,6 @@ See [Session Pruning](/concepts/session-pruning) for behavior details.
 ```
 
 - Non-Telegram channels require explicit `*.blockStreaming: true` to enable block replies.
-- Channel overrides: `channels.<channel>.blockStreamingCoalesce` (and per-account variants). Signal/Slack/Discord/Google Chat default `minChars: 1500`.
 - `humanDelay`: randomized pause between block replies. `natural` = 800–2500ms. Per-agent override: `agents.list[].humanDelay`.
 
 See [Streaming](/concepts/streaming) for behavior + chunking details.
@@ -964,7 +947,6 @@ Optional **Docker sandboxing** for the embedded agent. See [Sandboxing](/gateway
           "sessions_spawn",
           "session_status",
         ],
-        deny: ["browser", "canvas", "nodes", "cron", "discord", "gateway"],
       },
     },
   },
@@ -1159,7 +1141,6 @@ Within each tier, the first matching `bindings` entry wins.
             "whatsapp",
             "telegram",
             "slack",
-            "discord",
             "gateway",
           ],
           deny: [
@@ -1196,9 +1177,7 @@ See [Multi-Agent Sandbox & Tools](/tools/multi-agent-sandbox-tools) for preceden
   session: {
     scope: "per-sender",
     dmScope: "main", // main | per-peer | per-channel-peer | per-account-channel-peer
-    identityLinks: {
-      alice: ["telegram:123456789", "discord:987654321012345678"],
-    },
+    identityLinks: {},
     reset: {
       mode: "daily", // daily | idle
       atHour: 4,
@@ -1220,7 +1199,6 @@ See [Multi-Agent Sandbox & Tools](/tools/multi-agent-sandbox-tools) for preceden
     mainKey: "main", // legacy (runtime always uses "main")
     agentToAgent: { maxPingPongTurns: 5 },
     sendPolicy: {
-      rules: [{ action: "deny", match: { channel: "discord", chatType: "group" } }],
       default: "allow",
     },
   },
@@ -1299,7 +1277,6 @@ Variables are case-insensitive. `{think}` is an alias for `{thinkingLevel}`.
 - Per-channel overrides: `channels.<channel>.ackReaction`, `channels.<channel>.accounts.<id>.ackReaction`.
 - Resolution order: account → channel → `messages.ackReaction` → identity fallback.
 - Scope: `group-mentions` (default), `group-all`, `direct`, `all`.
-- `removeAckAfterReply`: removes ack after reply (Slack/Discord/Telegram/Google Chat only).
 
 ### Inbound debounce
 
@@ -1443,7 +1420,6 @@ Controls elevated (host) exec access:
       enabled: true,
       allowFrom: {
         whatsapp: ["+15555550123"],
-        discord: ["steipete", "1234567890123"],
       },
     },
   },
@@ -2436,28 +2412,27 @@ See [Cron Jobs](/automation/cron-jobs).
 
 Template placeholders expanded in `tools.media.*.models[].args`:
 
-| Variable           | Description                                       |
-| ------------------ | ------------------------------------------------- |
-| `{{Body}}`         | Full inbound message body                         |
-| `{{RawBody}}`      | Raw body (no history/sender wrappers)             |
-| `{{BodyStripped}}` | Body with group mentions stripped                 |
-| `{{From}}`         | Sender identifier                                 |
-| `{{To}}`           | Destination identifier                            |
-| `{{MessageSid}}`   | Channel message id                                |
-| `{{SessionId}}`    | Current session UUID                              |
-| `{{IsNewSession}}` | `"true"` when new session created                 |
-| `{{MediaUrl}}`     | Inbound media pseudo-URL                          |
-| `{{MediaPath}}`    | Local media path                                  |
-| `{{MediaType}}`    | Media type (image/audio/document/…)               |
-| `{{Transcript}}`   | Audio transcript                                  |
-| `{{Prompt}}`       | Resolved media prompt for CLI entries             |
-| `{{MaxChars}}`     | Resolved max output chars for CLI entries         |
-| `{{ChatType}}`     | `"direct"` or `"group"`                           |
-| `{{GroupSubject}}` | Group subject (best effort)                       |
-| `{{GroupMembers}}` | Group members preview (best effort)               |
-| `{{SenderName}}`   | Sender display name (best effort)                 |
-| `{{SenderE164}}`   | Sender phone number (best effort)                 |
-| `{{Provider}}`     | Provider hint (whatsapp, telegram, discord, etc.) |
+| Variable           | Description                               |
+| ------------------ | ----------------------------------------- |
+| `{{Body}}`         | Full inbound message body                 |
+| `{{RawBody}}`      | Raw body (no history/sender wrappers)     |
+| `{{BodyStripped}}` | Body with group mentions stripped         |
+| `{{From}}`         | Sender identifier                         |
+| `{{To}}`           | Destination identifier                    |
+| `{{MessageSid}}`   | Channel message id                        |
+| `{{SessionId}}`    | Current session UUID                      |
+| `{{IsNewSession}}` | `"true"` when new session created         |
+| `{{MediaUrl}}`     | Inbound media pseudo-URL                  |
+| `{{MediaPath}}`    | Local media path                          |
+| `{{MediaType}}`    | Media type (image/audio/document/…)       |
+| `{{Transcript}}`   | Audio transcript                          |
+| `{{Prompt}}`       | Resolved media prompt for CLI entries     |
+| `{{MaxChars}}`     | Resolved max output chars for CLI entries |
+| `{{ChatType}}`     | `"direct"` or `"group"`                   |
+| `{{GroupSubject}}` | Group subject (best effort)               |
+| `{{GroupMembers}}` | Group members preview (best effort)       |
+| `{{SenderName}}`   | Sender display name (best effort)         |
+| `{{SenderE164}}`   | Sender phone number (best effort)         |
 
 ---
 

package/docs/gateway/configuration.md

@@ -74,12 +74,10 @@ When validation fails:
 ## Common tasks
 
 <AccordionGroup>
-  <Accordion title="Set up a channel (WhatsApp, Telegram, Discord, etc.)">
     Each channel has its own config section under `channels.<provider>`. See the dedicated channel page for setup steps:
 
     - [WhatsApp](/channels/whatsapp) — `channels.whatsapp`
     - [Telegram](/channels/telegram) — `channels.telegram`
-    - [Discord](/channels/discord) — `channels.discord`
     - [Slack](/channels/slack) — `channels.slack`
     - [Signal](/channels/signal) — `channels.signal`
     - [iMessage](/channels/imessage) — `channels.imessage`
@@ -234,7 +232,6 @@ When validation fails:
     ```
 
     - `every`: duration string (`30m`, `2h`). Set `0m` to disable.
-    - `target`: `last` | `whatsapp` | `telegram` | `discord` | `none`
     - See [Heartbeat](/gateway/heartbeat) for the full guide.
 
   </Accordion>

package/docs/gateway/heartbeat.md

@@ -213,7 +213,6 @@ Use `accountId` to target a specific account on multi-account channels like Tele
   - Session key formats: see [Sessions](/concepts/session) and [Groups](/channels/groups).
 - `target`:
   - `last` (default): deliver to the last used external channel.
-  - explicit channel: `whatsapp` / `telegram` / `discord` / `googlechat` / `slack` / `msteams` / `signal` / `imessage`.
   - `none`: run the heartbeat but **do not deliver** externally.
 - `to`: optional recipient override (channel-specific id, e.g. E.164 for WhatsApp or a Telegram chat id). For Telegram topics/threads, use `<chatId>:topic:<messageThreadId>`.
 - `accountId`: optional account id for multi-account channels. When `target: "last"`, the account id applies to the resolved last channel if it supports accounts; otherwise it is ignored. If the account id does not match a configured account for the resolved channel, delivery is skipped.
@@ -231,7 +230,6 @@ Use `accountId` to target a specific account on multi-account channels like Tele
 
 - Heartbeats run in the agent’s main session by default (`agent:<id>:<mainKey>`),
   or `global` when `session.scope = "global"`. Set `session` to override to a
-  specific channel session (Discord/WhatsApp/etc.).
 - `session` only affects the run context; delivery is controlled by `target` and `to`.
 - To deliver to a specific channel/recipient, set `target` + `to`. With
   `target: "last"`, delivery uses the last external channel for that session.

package/docs/gateway/security/index.md

@@ -96,7 +96,6 @@ Use this when auditing access 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`
@@ -336,13 +335,11 @@ If you run multiple accounts on the same channel, use `per-account-channel-peer`
 
 Symi has two separate “who can trigger me?” layers:
 
-- **DM allowlist** (`allowFrom` / `channels.discord.allowFrom` / `channels.slack.allowFrom`; legacy: `channels.discord.dm.allowFrom`, `channels.slack.dm.allowFrom`): who is allowed to talk to the bot in direct messages.
-  - When `dmPolicy="pairing"`, approvals are written to `~/.symi/credentials/<channel>-allowFrom.json` (merged with config allowlists).
+- When `dmPolicy="pairing"`, approvals are written to `~/.symi/credentials/<channel>-allowFrom.json` (merged with config allowlists).
 - **Group allowlist** (channel-specific): which groups/channels/guilds the bot will accept messages from at all.
   - Common patterns:
     - `channels.whatsapp.groups`, `channels.telegram.groups`, `channels.imessage.groups`: per-group defaults like `requireMention`; when set, it also acts as a group allowlist (include `"*"` to keep allow-all behavior).
     - `groupPolicy="allowlist"` + `groupAllowFrom`: restrict who can trigger the bot _inside_ a group session (WhatsApp/Telegram/Signal/iMessage/Microsoft Teams).
-    - `channels.discord.guilds` / `channels.slack.channels`: per-surface allowlists + mention defaults.
   - Group checks run in this order: `groupPolicy`/group allowlists first, mention/reply activation second.
   - Replying to a bot message (implicit mention) does **not** bypass sender allowlists like `groupAllowFrom`.
   - **Security note:** treat `dmPolicy="open"` and `groupPolicy="open"` as last-resort settings. They should be barely used; prefer pairing + allowlists unless you fully trust every member of the room.
@@ -831,7 +828,6 @@ Common use cases:
             "whatsapp",
             "telegram",
             "slack",
-            "discord",
           ],
           deny: [
             "read",
@@ -881,7 +877,6 @@ If your AI does something bad:
 
 1. Rotate Gateway auth (`gateway.auth.token` / `SYMI_GATEWAY_PASSWORD`) and restart.
 2. Rotate remote client secrets (`gateway.remote.token` / `.password`) on any machine that can call the Gateway.
-3. Rotate provider/API credentials (WhatsApp creds, Slack/Discord tokens, model/API keys in `auth-profiles.json`).
 
 ### Audit
 

package/docs/gateway/troubleshooting.md

@@ -148,7 +148,6 @@ Related:
 - [/channels/troubleshooting](/channels/troubleshooting)
 - [/channels/whatsapp](/channels/whatsapp)
 - [/channels/telegram](/channels/telegram)
-- [/channels/discord](/channels/discord)
 
 ## Cron and heartbeat delivery
 

package/docs/help/faq.md

@@ -192,7 +192,6 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 - [Chat commands, aborting tasks, and "it won't stop"](#chat-commands-aborting-tasks-and-it-wont-stop)
   - [How do I stop internal system messages from showing in chat](#how-do-i-stop-internal-system-messages-from-showing-in-chat)
   - [How do I stop/cancel a running task?](#how-do-i-stopcancel-a-running-task)
-  - [How do I send a Discord message from Telegram? ("Cross-context messaging denied")](#how-do-i-send-a-discord-message-from-telegram-crosscontext-messaging-denied)
   - [Why does it feel like the bot "ignores" rapid-fire messages?](#why-does-it-feel-like-the-bot-ignores-rapidfire-messages)
 
 ## First 60 seconds if something's broken
@@ -265,7 +264,6 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 ### Im stuck what's the fastest way to get unstuck
 
 Use a local AI agent that can **see your machine**. That is far more effective than asking
-in Discord, because most "I'm stuck" cases are **local config or environment issues** that
 remote helpers cannot inspect.
 
 - **Claude Code**: [https://www.anthropic.com/claude-code/](https://www.anthropic.com/claude-code/)
@@ -659,7 +657,6 @@ Docs: [Update](/cli/update), [Updating](/install/updating).
 - **Model/auth setup** (Anthropic **setup-token** recommended for Claude subscriptions, OpenAI Codex OAuth supported, API keys optional, LM Studio local models supported)
 - **Workspace** location + bootstrap files
 - **Gateway settings** (bind/port/auth/tailscale)
-- **Providers** (WhatsApp, Telegram, Discord, Mattermost (plugin), Signal, iMessage)
 - **Daemon install** (LaunchAgent on macOS; systemd user unit on Linux/WSL2)
 - **Health checks** and **skills** selection
 
@@ -887,8 +884,6 @@ lowest friction and you're okay with sleep/restarts, run it locally.
 - **Pros:** always-on, stable network, no laptop sleep issues, easier to keep running.
 - **Cons:** often run headless (use screenshots), remote file access only, you must SSH for updates.
 
-**Symi-specific note:** WhatsApp/Telegram/Slack/Mattermost (plugin)/Discord all work fine from a VPS. The only real trade-off is **headless browser** vs a visible window. See [Browser](/tools/browser).
-
 **Recommended default:** VPS if you had gateway disconnects before. Local is great when you're actively using the Mac and want local file access or UI automation with a visible browser.
 
 ### How important is it to run Symi on a dedicated machine
@@ -931,8 +926,6 @@ If you are running macOS in a VM, see [macOS VM](/install/macos-vm).
 
 ### What is Symi in one paragraph
 
-Symi is a personal AI assistant you run on your own devices. It replies on the messaging surfaces you already use (WhatsApp, Telegram, Slack, Mattermost (plugin), Discord, Google Chat, Signal, iMessage, WebChat) and can also do voice + a live Canvas on supported platforms. The **Gateway** is the always-on control plane; the assistant is the product.
-
 ### What's the value proposition
 
 Symi is not "just a Claude wrapper." It's a **local-first control plane** that lets you run a
@@ -944,7 +937,6 @@ Highlights:
 
 - **Your devices, your data:** run the Gateway wherever you want (Mac, Linux, VPS) and keep the
   workspace + session history local.
-- **Real channels, not a web sandbox:** WhatsApp/Telegram/Slack/Discord/Signal/iMessage/etc,
   plus mobile voice and Canvas on supported platforms.
 - **Model-agnostic:** use Anthropic, OpenAI, MiniMax, OpenRouter, etc., with per-agent routing
   and failover.
@@ -1917,8 +1909,6 @@ See [Groups](/channels/groups) and [Group messages](/channels/group-messages).
 
 ### Do groups/threads share context with DMs
 
-Direct chats collapse to the main session by default. Groups/channels have their own session keys, and Telegram topics / Discord threads are separate sessions. See [Groups](/channels/groups) and [Group messages](/channels/group-messages).
-
 ### How many workspaces and agents can I create
 
 No hard limits. Dozens (even hundreds) are fine, but watch for:
@@ -2809,10 +2799,7 @@ Slash commands overview: see [Slash commands](/tools/slash-commands).
 
 Most commands must be sent as a **standalone** message that starts with `/`, but a few shortcuts (like `/status`) also work inline for allowlisted senders.
 
-### How do I send a Discord message from Telegram Crosscontext messaging denied
-
 Symi blocks **cross-provider** messaging by default. If a tool call is bound
-to Telegram, it won't send to Discord unless you explicitly allow it.
 
 Enable cross-provider messaging for the agent:
 

package/docs/help/troubleshooting.md

@@ -75,7 +75,6 @@ flowchart TD
 
     Common log signatures:
 
-    - `drop guild message (mention required` → mention gating blocked the message in Discord.
     - `pairing request` → sender is unapproved and waiting for DM pairing approval.
     - `blocked` / `allowlist` in channel logs → sender, room, or group is filtered.
 

package/docs/index.md

@@ -25,7 +25,6 @@ title: "Symi"
 > _"EXFOLIATE! EXFOLIATE!"_ — A space pipeline, probably
 
 <p align="center">
-  <strong>Any OS gateway for AI agents across WhatsApp, Telegram, Discord, iMessage, and more.</strong><br />
   Send a message, get an agent response from your pocket. Plugins add Mattermost and more.
 </p>
 
@@ -43,14 +42,11 @@ title: "Symi"
 
 ## What is Symi?
 
-Symi is a **self-hosted gateway** that connects your favorite chat apps — WhatsApp, Telegram, Discord, iMessage, and more — to AI coding agents like Pi. You run a single Gateway process on your own machine (or a server), and it becomes the bridge between your messaging apps and an always-available AI assistant.
-
 **Who is it for?** Developers and power users who want a personal AI assistant they can message from anywhere — without giving up control of their data or relying on a hosted service.
 
 **What makes it different?**
 
 - **Self-hosted**: runs on your hardware, your rules
-- **Multi-channel**: one Gateway serves WhatsApp, Telegram, Discord, and more simultaneously
 - **Agent-native**: built for coding agents with tool use, sessions, memory, and multi-agent routing
 - **Open source**: MIT licensed, community-driven
 
@@ -74,7 +70,6 @@ The Gateway is the single source of truth for sessions, routing, and channel con
 
 <Columns>
   <Card title="Multi-channel gateway" icon="network">
-    WhatsApp, Telegram, Discord, and iMessage with a single Gateway process.
   </Card>
   <Card title="Plugin channels" icon="plug">
     Add Mattermost and more with extension packages.
@@ -161,7 +156,6 @@ Example:
     SSH and tailnet access patterns.
   </Card>
   <Card title="Channels" href="/channels/telegram" icon="message-square">
-    Channel-specific setup for WhatsApp, Telegram, Discord, and more.
   </Card>
   <Card title="Nodes" href="/nodes" icon="smartphone">
     iOS and Android nodes with pairing and Canvas.

package/docs/install/ansible.md

@@ -63,9 +63,8 @@ sudo -i -u symi
 The post-install script will guide you through:
 
 1. **Onboarding wizard**: Configure Symi settings
-2. **Provider login**: Connect WhatsApp/Telegram/Discord/Signal
-3. **Gateway testing**: Verify the installation
-4. **Tailscale setup**: Connect to your VPN mesh
+2. **Gateway testing**: Verify the installation
+3. **Tailscale setup**: Connect to your VPN mesh
 
 ### Quick commands
 

package/docs/install/docker.md

@@ -287,13 +287,9 @@ Telegram (bot token):
 docker compose run --rm symi-cli channels add --channel telegram --token "<token>"
 ```
 
-Discord (bot token):
-
 ```bash
-docker compose run --rm symi-cli channels add --channel discord --token "<token>"
-```
 
-Docs: [WhatsApp](/channels/whatsapp), [Telegram](/channels/telegram), [Discord](/channels/discord)
+```
 
 ### OpenAI Codex OAuth (headless Docker)
 
@@ -368,7 +364,6 @@ precedence, and troubleshooting.
 - Auto-prune: idle > 24h OR age > 7d
 - Network: `none` by default (explicitly opt-in if you need egress)
 - Default allow: `exec`, `process`, `read`, `write`, `edit`, `sessions_list`, `sessions_history`, `sessions_send`, `sessions_spawn`, `session_status`
-- Default deny: `browser`, `canvas`, `nodes`, `cron`, `discord`, `gateway`
 
 ### Enable sandboxing
 
@@ -435,7 +430,6 @@ If you plan to install packages in `setupCommand`, note:
           "sessions_spawn",
           "session_status",
         ],
-        deny: ["browser", "canvas", "nodes", "cron", "discord", "gateway"],
       },
     },
   },

package/docs/install/fly.md

@@ -5,14 +5,11 @@ description: Deploy Symi on Fly.io
 
 # Fly.io Deployment
 
-**Goal:** Symi Gateway running on a [Fly.io](https://fly.io) machine with persistent storage, automatic HTTPS, and Discord/channel access.
-
 ## What you need
 
 - [flyctl CLI](https://fly.io/docs/hands-on/install-flyctl/) installed
 - Fly.io account (free tier works)
 - Model auth: Anthropic API key (or other provider keys)
-- Channel credentials: Discord bot token, Telegram token, etc.
 
 ## Beginner quick path
 
@@ -100,7 +97,6 @@ fly secrets set OPENAI_API_KEY=sk-...
 fly secrets set GOOGLE_API_KEY=...
 
 # Channel tokens
-fly secrets set DISCORD_BOT_TOKEN=MTQ...
 ```
 
 **Notes:**
@@ -128,7 +124,6 @@ You should see:
 
 ```
 [gateway] listening on ws://0.0.0.0:3000 (PID xxx)
-[discord] logged in to discord as xxx
 ```
 
 ## 5) Create config file
@@ -169,11 +164,9 @@ cat > /data/symi.json << 'EOF'
   "bindings": [
     {
       "agentId": "main",
-      "match": { "channel": "discord" }
     }
   ],
   "channels": {
-    "discord": {
       "enabled": true,
       "groupPolicy": "allowlist",
       "guilds": {
@@ -197,13 +190,6 @@ EOF
 
 **Note:** With `SYMI_STATE_DIR=/data`, the config path is `/data/symi.json`.
 
-**Note:** The Discord token can come from either:
-
-- Environment variable: `DISCORD_BOT_TOKEN` (recommended for secrets)
-- Config file: `channels.discord.token`
-
-If using env var, no need to add token to config. The gateway reads `DISCORD_BOT_TOKEN` automatically.
-
 Restart to apply:
 
 ```bash

package/docs/install/northflank.mdx

@@ -28,9 +28,8 @@ and you configure everything via the `/setup` web wizard.
 
 1. Visit `https://<your-northflank-domain>/setup` and enter your `SETUP_PASSWORD`.
 2. Choose a model/auth provider and paste your key.
-3. (Optional) Add Telegram/Discord/Slack tokens.
-4. Click **Run setup**.
-5. Open the Control UI at `https://<your-northflank-domain>/symi`
+3. Click **Run setup**.
+4. Open the Control UI at `https://<your-northflank-domain>/symi`
 
 If Telegram DMs are set to pairing, the setup wizard can approve the pairing code.
 
@@ -43,11 +42,8 @@ If Telegram DMs are set to pairing, the setup wizard can approve the pairing cod
 3. Copy the token (looks like `123456789:AA...`)
 4. Paste it into `/setup`
 
-### Discord bot token
-
-1. Go to [https://discord.com/developers/applications](https://discord.com/developers/applications)
-2. **New Application** → choose a name
-3. **Bot** → **Add Bot**
-4. **Enable MESSAGE CONTENT INTENT** under Bot → Privileged Gateway Intents (required or the bot will crash on startup)
-5. Copy the **Bot Token** and paste into `/setup`
-6. Invite the bot to your server (OAuth2 URL Generator; scopes: `bot`, `applications.commands`)
+5. **New Application** → choose a name
+6. **Bot** → **Add Bot**
+7. **Enable MESSAGE CONTENT INTENT** under Bot → Privileged Gateway Intents (required or the bot will crash on startup)
+8. Copy the **Bot Token** and paste into `/setup`
+9. Invite the bot to your server (OAuth2 URL Generator; scopes: `bot`, `applications.commands`)

package/docs/install/railway.mdx

@@ -67,8 +67,7 @@ Set these variables on the service:
 
 1. Visit `https://<your-railway-domain>/setup` and enter your `SETUP_PASSWORD`.
 2. Choose a model/auth provider and paste your key.
-3. (Optional) Add Telegram/Discord/Slack tokens.
-4. Click **Run setup**.
+3. Click **Run setup**.
 
 If Telegram DMs are set to pairing, the setup wizard can approve the pairing code.
 
@@ -81,14 +80,11 @@ If Telegram DMs are set to pairing, the setup wizard can approve the pairing cod
 3. Copy the token (looks like `123456789:AA...`)
 4. Paste it into `/setup`
 
-### Discord bot token
-
-1. Go to [https://discord.com/developers/applications](https://discord.com/developers/applications)
-2. **New Application** → choose a name
-3. **Bot** → **Add Bot**
-4. **Enable MESSAGE CONTENT INTENT** under Bot → Privileged Gateway Intents (required or the bot will crash on startup)
-5. Copy the **Bot Token** and paste into `/setup`
-6. Invite the bot to your server (OAuth2 URL Generator; scopes: `bot`, `applications.commands`)
+5. **New Application** → choose a name
+6. **Bot** → **Add Bot**
+7. **Enable MESSAGE CONTENT INTENT** under Bot → Privileged Gateway Intents (required or the bot will crash on startup)
+8. Copy the **Bot Token** and paste into `/setup`
+9. Invite the bot to your server (OAuth2 URL Generator; scopes: `bot`, `applications.commands`)
 
 ## Backups & migration
 

package/docs/install/render.mdx

@@ -78,8 +78,7 @@ The Blueprint defaults to `starter`. To use free tier, change `plan: free` in yo
 1. Navigate to `https://<your-service>.onrender.com/setup`
 2. Enter your `SETUP_PASSWORD`
 3. Select a model provider and paste your API key
-4. Optionally configure messaging channels (Telegram, Discord, Slack)
-5. Click **Run setup**
+4. Click **Run setup**
 
 ### Access the Control UI
 

package/docs/ja-JP/index.md

@@ -32,7 +32,6 @@ x-i18n:
 > _「EXFOLIATE! EXFOLIATE!」_ — たぶん宇宙ロブスター
 
 <p align="center">
-  <strong>WhatsApp、Telegram、Discord、iMessageなどに対応した、あらゆるOS向けのAIエージェントgateway。</strong><br />
   メッセージを送信すれば、ポケットからエージェントの応答を受け取れます。プラグインでMattermostなどを追加できます。
 </p>
 
@@ -68,7 +67,6 @@ Gatewayは、セッション、ルーティング、チャネル接続の信頼
 
 <Columns>
   <Card title="マルチチャネルgateway" icon="network">
-    単一のGatewayプロセスでWhatsApp、Telegram、Discord、iMessageに対応。
   </Card>
   <Card title="プラグインチャネル" icon="plug">
     拡張パッケージでMattermostなどを追加。
@@ -155,7 +153,6 @@ Gatewayの起動後、ブラウザでControl UIを開きます。
     SSHおよびtailnetアクセスパターン。
   </Card>
   <Card title="チャネル" href="/channels/telegram" icon="message-square">
-    WhatsApp、Telegram、Discordなどのチャネル固有のセットアップ。
   </Card>
   <Card title="ノード" href="/nodes" icon="smartphone">
     ペアリングとCanvas対応のiOSおよびAndroidノード。

package/docs/pi.md

@@ -115,7 +115,6 @@ src/agents/
 │   ├── browser-tool.ts
 │   ├── canvas-tool.ts
 │   ├── cron-tool.ts
-│   ├── discord-actions*.ts
 │   ├── gateway-tool.ts
 │   ├── image-tool.ts
 │   ├── message-tool.ts
@@ -235,10 +234,9 @@ The SDK handles the full agent loop: sending to LLM, executing tool calls, strea
 1. **Base Tools**: pi's `codingTools` (read, bash, edit, write)
 2. **Custom Replacements**: Symi replaces bash with `exec`/`process`, customizes read/edit/write for sandbox
 3. **Symi Tools**: messaging, browser, canvas, sessions, cron, gateway, etc.
-4. **Channel Tools**: Discord/Telegram/Slack/WhatsApp-specific action tools
-5. **Policy Filtering**: Tools filtered by profile, provider, agent, group, sandbox policies
-6. **Schema Normalization**: Schemas cleaned for Gemini/OpenAI quirks
-7. **AbortSignal Wrapping**: Tools wrapped to respect abort signals
+4. **Policy Filtering**: Tools filtered by profile, provider, agent, group, sandbox policies
+5. **Schema Normalization**: Schemas cleaned for Gemini/OpenAI quirks
+6. **AbortSignal Wrapping**: Tools wrapped to respect abort signals
 
 ### Tool Definition Adapter
 

package/docs/platforms/digitalocean.md

@@ -86,7 +86,6 @@ symi onboard --install-daemon
 The wizard will walk you through:
 
 - Model auth (API keys or OAuth)
-- Channel setup (Telegram, WhatsApp, Discord, etc.)
 - Gateway token (auto-generated)
 - Daemon installation (systemd)
 

package/docs/platforms/mac/voicewake.md

@@ -55,7 +55,6 @@ Hardening:
 ## Forwarding behavior
 
 - When Voice Wake is enabled, transcripts are forwarded to the active gateway/agent (the same local vs remote mode used by the rest of the mac app).
-- Replies are delivered to the **last-used main provider** (WhatsApp/Telegram/Discord/WebChat). If delivery fails, the error is logged and the run is still visible via WebChat/session logs.
 
 ## Forwarding payload
 

package/docs/providers/index.md

@@ -11,8 +11,6 @@ title: "Model Providers"
 Symi can use many LLM providers. Pick a provider, authenticate, then set the
 default model as `provider/model`.
 
-Looking for chat channel docs (WhatsApp/Telegram/Discord/Slack/Mattermost (plugin)/etc.)? See [Channels](/channels).
-
 ## Highlight: Venice (Venice AI)
 
 Venice is our recommended Venice AI setup for privacy-first inference with an option to use Opus for hard tasks.