@symerian/symi 3.0.16 → 3.0.17

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.

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`