@symerian/symi 3.0.16 → 3.0.17

package/docs/channels/troubleshooting.md

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

package/docs/cli/channels.md

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

package/docs/cli/configure.md

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

package/docs/cli/directory.md

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

package/docs/cli/index.md

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

package/docs/cli/message.md

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

package/docs/cli/status.md

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

package/docs/concepts/architecture.md

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

package/docs/concepts/features.md

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

package/docs/concepts/markdown-formatting.md

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

package/docs/concepts/memory.md

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

package/docs/concepts/messages.md

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

package/docs/concepts/models.md

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

package/docs/concepts/multi-agent.md

@@ -90,7 +90,6 @@ Each agent gets its own workspace with `SYMICORE.md`, `AGENTS.md`, and optional
 
 Create one account per agent on your preferred channels:
 
-- Discord: one bot per agent, enable Message Content Intent, copy each token.
 - Telegram: one bot per agent via BotFather, copy each token.
 - WhatsApp: link each phone number per account.
 
@@ -98,8 +97,6 @@ Create one account per agent on your preferred channels:
 symi channels login --channel whatsapp --account work
 ```
 
-See channel guides: [Discord](/channels/discord), [Telegram](/channels/telegram), [WhatsApp](/channels/whatsapp).
-
   </Step>
 
   <Step title="Add agents, accounts, and bindings">
@@ -175,12 +172,10 @@ Bindings are **deterministic** and **most-specific wins**:
 
 1. `peer` match (exact DM/group/channel id)
 2. `parentPeer` match (thread inheritance)
-3. `guildId + roles` (Discord role routing)
-4. `guildId` (Discord)
-5. `teamId` (Slack)
-6. `accountId` match for a channel
-7. channel-level match (`accountId: "*"`)
-8. fallback to default agent (`agents.list[].default`, else first list entry, default: `main`)
+3. `teamId` (Slack)
+4. `accountId` match for a channel
+5. channel-level match (`accountId: "*"`)
+6. fallback to default agent (`agents.list[].default`, else first list entry, default: `main`)
 
 If multiple bindings match in the same tier, the first one in config order wins.
 If a binding sets multiple match fields (for example `peer` + `guildId`), all specified fields are required (`AND` semantics).
@@ -200,10 +195,6 @@ multiple phone numbers without mixing sessions.
 
 ## Platform examples
 
-### Discord bots per agent
-
-Each Discord bot account maps to a unique `accountId`. Bind each account to an agent and keep allowlists per bot.
-
 ```json5
 {
   agents: {
@@ -213,15 +204,11 @@ Each Discord bot account maps to a unique `accountId`. Bind each account to an a
     ],
   },
   bindings: [
-    { agentId: "main", match: { channel: "discord", accountId: "default" } },
-    { agentId: "coding", match: { channel: "discord", accountId: "coding" } },
   ],
   channels: {
-    discord: {
       groupPolicy: "allowlist",
       accounts: {
         default: {
-          token: "DISCORD_BOT_TOKEN_MAIN",
           guilds: {
             "123456789012345678": {
               channels: {
@@ -231,7 +218,6 @@ Each Discord bot account maps to a unique `accountId`. Bind each account to an a
           },
         },
         coding: {
-          token: "DISCORD_BOT_TOKEN_CODING",
           guilds: {
             "123456789012345678": {
               channels: {
@@ -249,7 +235,6 @@ Each Discord bot account maps to a unique `accountId`. Bind each account to an a
 Notes:
 
 - Invite each bot to the guild and enable Message Content Intent.
-- Tokens live in `channels.discord.accounts.<id>.token` (default account can use `DISCORD_BOT_TOKEN`).
 
 ### Telegram bots per agent
 

package/docs/concepts/queue.md

@@ -36,7 +36,6 @@ Inbound messages can steer the current run, wait for a followup turn, or do both
 Steer-backlog means you can get a followup response after the steered run, so
 streaming surfaces can look like duplicates. Prefer `collect`/`steer` if you want
 one response per inbound message.
-Send `/queue collect` as a standalone command (per-session) or set `messages.queue.byChannel.discord: "collect"`.
 
 Defaults (when unset in config):
 
@@ -52,7 +51,6 @@ Configure globally or per channel via `messages.queue`:
       debounceMs: 1000,
       cap: 20,
       drop: "summarize",
-      byChannel: { discord: "collect" },
     },
   },
 }
@@ -77,7 +75,6 @@ Defaults: `debounceMs: 1000`, `cap: 20`, `drop: summarize`.
 
 ## Scope and guarantees
 
-- Applies to auto-reply agent runs across all inbound channels that use the gateway reply pipeline (WhatsApp web, Telegram, Slack, Discord, Signal, iMessage, webchat, etc.).
 - Default lane (`main`) is process-wide for inbound + main heartbeats; set `agents.defaults.maxConcurrent` to allow multiple sessions in parallel.
 - Additional lanes may exist (e.g. `cron`, `subagent`) so background jobs can run in parallel without blocking inbound replies.
 - Per-session lanes guarantee that only one agent run touches a given session at a time.

package/docs/concepts/retry.md

@@ -21,14 +21,10 @@ title: "Retry Policy"
 - Jitter: 0.1 (10 percent)
 - Provider defaults:
   - Telegram min delay: 400 ms
-  - Discord min delay: 500 ms
 
 ## Behavior
 
-### Discord
-
 - Retries only on rate-limit errors (HTTP 429).
-- Uses Discord `retry_after` when available, otherwise exponential backoff.
 
 ### Telegram
 
@@ -51,7 +47,6 @@ Set retry policy per provider in `~/.symi/symi.json`:
         jitter: 0.1,
       },
     },
-    discord: {
       retry: {
         attempts: 3,
         minDelayMs: 500,

package/docs/concepts/session-tool.md

@@ -47,7 +47,6 @@ Row shape (JSON):
 
 - `key`: session key (string)
 - `kind`: `main | group | cron | hook | node | other`
-- `channel`: `whatsapp | telegram | discord | signal | imessage | webchat | internal | unknown`
 - `displayName` (group display label if available)
 - `updatedAt` (ms)
 - `sessionId`
@@ -121,7 +120,6 @@ Policy-based blocking by channel/chat type (not per session id).
     "sendPolicy": {
       "rules": [
         {
-          "match": { "channel": "discord", "chatType": "group" },
           "action": "deny"
         }
       ],

package/docs/concepts/session.md

@@ -106,7 +106,6 @@ the workspace is writable. See [Memory](/concepts/memory) and
 - Daily reset: defaults to **4:00 AM local time on the gateway host**. A session is stale once its last update is earlier than the most recent daily reset time.
 - Idle reset (optional): `idleMinutes` adds a sliding idle window. When both daily and idle resets are configured, **whichever expires first** forces a new session.
 - Legacy idle-only: if you set `session.idleMinutes` without any `session.reset`/`resetByType` config, Symi stays in idle-only mode for backward compatibility.
-- Per-type overrides (optional): `resetByType` lets you override the policy for `direct`, `group`, and `thread` sessions (thread = Slack/Discord threads, Telegram topics, Matrix threads when provided by the connector).
 - Per-channel overrides (optional): `resetByChannel` overrides the reset policy for a channel (applies to all session types for that channel and takes precedence over `reset`/`resetByType`).
 - Reset triggers: exact `/new` or `/reset` (plus any extras in `resetTriggers`) start a fresh session id and pass the remainder of the message through. `/new <model>` accepts a model alias, `provider/model`, or provider name (fuzzy match) to set the new session model. If `/new` or `/reset` is sent alone, Symi runs a short “hello” greeting turn to confirm the reset.
 - Manual reset: delete specific keys from the store or remove the JSONL transcript; the next message recreates them.
@@ -121,10 +120,8 @@ Block delivery for specific session types without listing individual ids.
   session: {
     sendPolicy: {
       rules: [
-        { action: "deny", match: { channel: "discord", chatType: "group" } },
         { action: "deny", match: { keyPrefix: "cron:" } },
         // Match the raw session key (including the `agent:<id>:` prefix).
-        { action: "deny", match: { rawKeyPrefix: "agent:main:discord:" } },
       ],
       default: "allow",
     },
@@ -147,9 +144,7 @@ Runtime override (owner only):
   session: {
     scope: "per-sender", // keep group keys separate
     dmScope: "main", // DM continuity (set per-channel-peer/per-account-channel-peer for shared inboxes)
-    identityLinks: {
-      alice: ["telegram:123456789", "discord:987654321012345678"],
-    },
+    identityLinks: {},
     reset: {
       // Defaults: mode=daily, atHour=4 (gateway host local time).
       // If you also set idleMinutes, whichever expires first wins.
@@ -162,9 +157,7 @@ Runtime override (owner only):
       direct: { mode: "idle", idleMinutes: 240 },
       group: { mode: "idle", idleMinutes: 120 },
     },
-    resetByChannel: {
-      discord: { mode: "idle", idleMinutes: 10080 },
-    },
+    resetByChannel: {},
     resetTriggers: ["/new", "/reset"],
     store: "~/.symi/agents/{agentId}/sessions/sessions.json",
     mainKey: "main",

package/docs/concepts/streaming.md

@@ -45,7 +45,6 @@ Legend:
 - `agents.defaults.blockStreamingCoalesce`: `{ minChars?, maxChars?, idleMs? }` (merge streamed blocks before send).
 - Channel hard cap: `*.textChunkLimit` (e.g., `channels.whatsapp.textChunkLimit`).
 - Channel chunk mode: `*.chunkMode` (`length` default, `newline` splits on blank lines (paragraph boundaries) before length chunking).
-- Discord soft cap: `channels.discord.maxLinesPerMessage` (default 17) splits tall replies to avoid UI clipping.
 
 **Boundary semantics:**
 
@@ -78,7 +77,6 @@ progressive output.
 - Joiner is derived from `blockStreamingChunk.breakPreference`
   (`paragraph` → `\n\n`, `newline` → `\n`, `sentence` → space).
 - Channel overrides are available via `*.blockStreamingCoalesce` (including per-account configs).
-- Default coalesce `minChars` is bumped to 1500 for Signal/Slack/Discord unless overridden.
 
 ## Human-like pacing between blocks
 

package/docs/concepts/system-prompt.md

@@ -123,7 +123,6 @@ This keeps the base prompt small while still enabling targeted skill usage.
 
 When available, the system prompt includes a **Documentation** section that points to the
 local Symi docs directory (either `docs/` in the repo workspace or the bundled npm
-package docs) and also notes the public mirror, source repo, community Discord, and
 SymiHub ([https://symihub.com](https://symihub.com)) for skills discovery. The prompt instructs the model to consult local docs first
 for Symi behavior, commands, configuration, or architecture, and to run
 `symi status` itself when possible (asking the user only when it lacks access).

package/docs/concepts/timezone.md

@@ -62,7 +62,6 @@ You can override this with:
 
 ## Tool payloads (raw provider data + normalized fields)
 
-Tool calls (`channels.discord.readMessages`, `channels.slack.readMessages`, etc.) return **raw provider timestamps**.
 We also attach normalized fields for consistency:
 
 - `timestampMs` (UTC epoch milliseconds)

package/docs/date-time.md

@@ -116,7 +116,6 @@ Channel tools return **provider-native timestamps** and add normalized fields fo
 Raw provider fields are preserved so nothing is lost.
 
 - Slack: epoch-like strings from the API
-- Discord: UTC ISO timestamps
 - Telegram/WhatsApp: provider-specific numeric/ISO timestamps
 
 If you need local time, convert it downstream using the known timezone.

package/docs/docs.json

@@ -1,7 +1,6 @@
 {
   "$schema": "https://mintlify.com/docs.json",
   "name": "Symi",
-  "description": "Self-hosted gateway that connects WhatsApp, Telegram, Discord, iMessage, and more to AI coding agents. Run a single Gateway process on your own machine and message your AI assistant from anywhere.",
   "theme": "mint",
   "icons": {
     "library": "lucide"
@@ -123,10 +122,7 @@
       "source": "/message",
       "destination": "/cli/message"
     },
-    {
-      "source": "/providers/discord",
-      "destination": "/channels/discord"
-    },
+    {},
     {
       "source": "/providers/googlechat",
       "destination": "/channels/googlechat"
@@ -307,10 +303,7 @@
       "source": "/device-models",
       "destination": "/reference/device-models"
     },
-    {
-      "source": "/discord",
-      "destination": "/channels/discord"
-    },
+    {},
     {
       "source": "/discovery",
       "destination": "/gateway/discovery"
@@ -883,7 +876,6 @@
                 "pages": [
                   "channels/whatsapp",
                   "channels/telegram",
-                  "channels/discord",
                   "channels/irc",
                   "channels/slack",
                   "channels/feishu",
@@ -1397,7 +1389,6 @@
                 "pages": [
                   "zh-CN/channels/whatsapp",
                   "zh-CN/channels/telegram",
-                  "zh-CN/channels/discord",
                   "zh-CN/channels/slack",
                   "zh-CN/channels/feishu",
                   "zh-CN/channels/googlechat",