@symerian/symi 3.0.16 → 3.0.17

package/docs/experiments/plans/cron-add-hardening.md

@@ -44,7 +44,6 @@ Recent gateway logs show repeated `cron.add` failures with invalid parameters (m
 
 - **Normalization:** wrapped `data`/`job` payloads are unwrapped; `schedule.kind` and `payload.kind` are inferred when safe.
 - **Defaults:** safe defaults are applied for `wakeMode` and `sessionTarget` when missing.
-- **Providers:** Discord/Slack/Signal/iMessage are now consistently surfaced across CLI/UI.
 
 See [Cron jobs](/automation/cron-jobs) for the normalized shape and examples.
 

package/docs/experiments/plans/session-binding-channel-agnostic.md

@@ -16,7 +16,6 @@ Goal:
 
 - make subagent bound session routing a core capability
 - keep channel specific behavior in adapters
-- avoid regressions in normal Discord behavior
 
 ## Why this exists
 
@@ -24,7 +23,6 @@ Current behavior mixes:
 
 - completion content policy
 - destination routing policy
-- Discord specific details
 
 This caused edge cases such as:
 
@@ -114,10 +112,6 @@ For this iteration:
 - only `task_completion` is routed through this new path
 - existing paths for other event kinds remain as-is
 
-### 3. Keep Discord as adapter
-
-Discord remains the first adapter implementation.
-
 Adapter responsibilities:
 
 - create/reuse thread conversations
@@ -130,7 +124,6 @@ Adapter responsibilities:
 Required in this iteration:
 
 - refresh token usage when reusing existing thread binding manager
-- record outbound activity for webhook based Discord sends
 - stop implicit main channel fallback when a bound thread destination is selected for session mode completion
 
 ### 5. Preserve current runtime safety defaults
@@ -139,11 +132,8 @@ No behavior change for users with thread bound spawn disabled.
 
 Defaults stay:
 
-- `channels.discord.threadBindings.spawnSubagentSessions = false`
-
 Result:
 
-- normal Discord users stay on current behavior
 - new core path affects only bound session completion routing where enabled
 
 ## Not in iteration 1
@@ -151,7 +141,6 @@ Result:
 Explicitly deferred:
 
 - ACP binding targets (`targetKind: "acp"`)
-- new channel adapters beyond Discord
 - global replacement of all delivery paths (`spawn_ack`, future `subagent_message`)
 - protocol level changes
 - store migration/versioning redesign for all binding persistence
@@ -175,14 +164,12 @@ These invariants are mandatory for iteration 1.
 Compatibility target:
 
 - no regression for users with thread bound spawning off
-- no change to non-Discord channels in this iteration
 
 Rollout:
 
 1. Land interfaces and router behind current feature gates.
-2. Route Discord completion mode bound deliveries through router.
-3. Keep legacy path for non-bound flows.
-4. Verify with targeted tests and canary runtime logs.
+2. Keep legacy path for non-bound flows.
+3. Verify with targeted tests and canary runtime logs.
 
 ## Tests required in iteration 1
 
@@ -202,16 +189,8 @@ Core:
 - `src/infra/outbound/bound-delivery-router.ts` (new)
 - `src/agents/subagent-announce.ts` (completion destination resolution integration)
 
-Discord adapter and runtime:
-
-- `src/discord/monitor/thread-bindings.manager.ts`
-- `src/discord/monitor/reply-delivery.ts`
-- `src/discord/send.outbound.ts`
-
 Tests:
 
-- `src/discord/monitor/provider*.test.ts`
-- `src/discord/monitor/reply-delivery.test.ts`
 - `src/agents/subagent-announce.format.e2e.test.ts`
 
 ## Done criteria for iteration 1

package/docs/experiments/plans/thread-bound-subagents.md

@@ -1,5 +1,4 @@
 ---
-summary: "Discord thread bound subagent sessions with plugin lifecycle hooks, routing, and config kill switches"
 owner: "onutc"
 status: "implemented"
 last_updated: "2026-02-21"
@@ -10,12 +9,8 @@ title: "Thread Bound Subagents"
 
 ## Overview
 
-This feature lets users interact with spawned subagents directly inside Discord threads.
-
 Instead of only waiting for a completion summary in the parent session, users can move into a dedicated thread that routes messages to the spawned subagent session. Replies are sent in-thread with a thread bound persona.
 
-The implementation is split between channel agnostic core lifecycle hooks and Discord specific extension behavior.
-
 ## Goals
 
 - Allow direct thread conversation with a spawned subagent session.
@@ -27,26 +22,21 @@ The implementation is split between channel agnostic core lifecycle hooks and Di
 ## Out of scope
 
 - New ACP protocol features.
-- Non Discord thread binding implementations in this document.
-- New bot accounts or app level Discord identity changes.
 
 ## What shipped
 
 - `sessions_spawn` supports `thread: true` and `mode: "run" | "session"`.
 - Spawn flow supports persistent thread bound sessions.
-- Discord thread binding manager supports bind, unbind, TTL sweep, and persistence.
 - Plugin hook lifecycle for subagents:
   - `subagent_spawning`
   - `subagent_spawned`
   - `subagent_delivery_target`
   - `subagent_ended`
-- Discord extension implements thread auto bind, delivery target override, and unbind on end.
 - Text commands for manual control:
   - `/focus`
   - `/unfocus`
   - `/agents`
   - `/session ttl`
-- Global and Discord scoped enablement and TTL controls, including a global kill switch.
 
 ## Core concepts
 
@@ -91,12 +81,8 @@ The manager is responsible for:
 
 ### Core and extension boundary
 
-Core (`src/agents/*`) does not directly depend on Discord routing internals.
-
 Core emits lifecycle intent through plugin hooks.
 
-Discord extension (`extensions/discord/src/subagent-hooks.ts`) implements Discord specific behavior:
-
 - pre spawn thread bind preparation
 - completion delivery target override to bound thread
 - unbind on subagent end
@@ -111,7 +97,6 @@ Discord extension (`extensions/discord/src/subagent-hooks.ts`) implements Discor
    - post run registration event
 3. `subagent_delivery_target`
    - completion routing override hook
-   - can redirect completion delivery to bound Discord thread origin
 4. `subagent_ended`
    - cleanup and unbind signal
 
@@ -147,8 +132,6 @@ Migration guardrails:
 
 Binding state path:
 
-- `${stateDir}/discord/thread-bindings.json`
-
 Record shape contains:
 
 - account, channel, thread
@@ -163,32 +146,22 @@ State is stored on `globalThis` to keep one shared registry across ESM and Jiti
 
 ### Effective precedence
 
-For Discord thread binding options, account override wins, then channel, then global session default, then built in fallback.
-
-- account: `channels.discord.accounts.<id>.threadBindings.<key>`
-- channel: `channels.discord.threadBindings.<key>`
 - global: `session.threadBindings.<key>`
 
 ### Keys
 
-| Key                                                     | Scope           | Default         | Notes                                     |
-| ------------------------------------------------------- | --------------- | --------------- | ----------------------------------------- |
-| `session.threadBindings.enabled`                        | global          | `true`          | master default kill switch                |
-| `session.threadBindings.ttlHours`                       | global          | `24`            | default auto unfocus TTL                  |
-| `channels.discord.threadBindings.enabled`               | channel/account | inherits global | Discord override kill switch              |
-| `channels.discord.threadBindings.ttlHours`              | channel/account | inherits global | Discord TTL override                      |
-| `channels.discord.threadBindings.spawnSubagentSessions` | channel/account | `false`         | opt in for `thread: true` spawn auto bind |
+| Key                               | Scope  | Default | Notes                      |
+| --------------------------------- | ------ | ------- | -------------------------- |
+| `session.threadBindings.enabled`  | global | `true`  | master default kill switch |
+| `session.threadBindings.ttlHours` | global | `24`    | default auto unfocus TTL   |
 
 ### Runtime effect of enable switch
 
-When effective `enabled` is false for a Discord account:
-
 - provider creates a noop thread binding manager for runtime wiring
 - no real manager is registered for lookup by account id
 - inbound bound thread routing is effectively disabled
 - completion routing overrides do not resolve bound thread origins
 - `/focus`, `/unfocus`, and thread binding specific operations report unavailable
-- `thread: true` spawn path returns actionable error from Discord hook layer
 
 ## Flow and behavior
 
@@ -196,30 +169,26 @@ When effective `enabled` is false for a Discord account:
 
 1. Spawn validates mode and permissions.
 2. `subagent_spawning` hook runs.
-3. Discord extension checks effective flags:
    - thread bindings enabled
    - `spawnSubagentSessions` enabled
-4. Extension attempts auto bind and thread creation.
-5. If bind fails:
+3. Extension attempts auto bind and thread creation.
+4. If bind fails:
    - spawn returns error
    - provisional child session is deleted
-6. If bind succeeds:
+5. If bind succeeds:
    - child run starts
    - run is registered with spawn mode
 
 ### Manual focus and unfocus
 
 - `/focus <target>`
-  - Discord only
   - resolves subagent or session target
   - binds current or created thread to target session
 - `/unfocus`
-  - Discord thread only
   - unbinds current thread
 
 ### Inbound routing
 
-- Discord preflight checks current thread id against thread binding manager.
 - If bound, effective session routing uses bound target session key.
 - If not bound, normal routing path is used.
 
@@ -232,7 +201,6 @@ When effective `enabled` is false for a Discord account:
 ### Completion routing
 
 - Core completion flow calls `subagent_delivery_target`.
-- Discord extension returns bound thread origin when it can resolve one.
 - Core merges hook origin with requester origin and delivers completion.
 
 ### Cleanup
@@ -260,7 +228,6 @@ Cleanup behavior includes unbind and optional farewell messaging.
 
 Notes:
 
-- `/session ttl` is currently Discord thread focused behavior.
 - Thread intro and farewell text are generated by thread binding message helpers.
 
 ## Failure handling and safety
@@ -281,27 +248,14 @@ Notes:
 - `src/agents/subagent-registry-cleanup.ts`
 - `src/agents/subagent-registry-completion.ts`
 
-### Discord runtime
-
-- `src/discord/monitor/provider.ts`
-- `src/discord/monitor/thread-bindings.manager.ts`
-- `src/discord/monitor/thread-bindings.state.ts`
-- `src/discord/monitor/thread-bindings.lifecycle.ts`
-- `src/discord/monitor/thread-bindings.messages.ts`
-- `src/discord/monitor/message-handler.preflight.ts`
-- `src/discord/monitor/message-handler.process.ts`
-- `src/discord/monitor/reply-delivery.ts`
-
 ### Plugin hooks and extension
 
 - `src/plugins/types.ts`
 - `src/plugins/hooks.ts`
-- `extensions/discord/src/subagent-hooks.ts`
 
 ### Config and schema
 
 - `src/config/types.base.ts`
-- `src/config/types.discord.ts`
 - `src/config/zod-schema.session.ts`
 - `src/config/zod-schema.providers-core.ts`
 - `src/config/schema.help.ts`
@@ -309,12 +263,6 @@ Notes:
 
 ## Test coverage highlights
 
-- `extensions/discord/src/subagent-hooks.test.ts`
-- `src/discord/monitor/thread-bindings.ttl.test.ts`
-- `src/discord/monitor/thread-bindings.shared-state.test.ts`
-- `src/discord/monitor/reply-delivery.test.ts`
-- `src/discord/monitor/message-handler.preflight.test.ts`
-- `src/discord/monitor/message-handler.process.test.ts`
 - `src/auto-reply/reply/commands-subagents-focus.test.ts`
 - `src/auto-reply/reply/commands-session-ttl.test.ts`
 - `src/agents/subagent-registry.steer-restart.test.ts`
@@ -323,16 +271,11 @@ Notes:
 ## Operational summary
 
 - Use `session.threadBindings.enabled` as the global kill switch default.
-- Use `channels.discord.threadBindings.enabled` and account overrides for selective enablement.
 - Keep `spawnSubagentSessions` opt in for thread auto spawn behavior.
 - Use TTL settings for automatic unfocus policy control.
 
-This model keeps subagent lifecycle orchestration generic while giving Discord a full thread bound interaction path.
-
 ## Related plan
 
 For channel agnostic SessionBinding architecture and scoped iteration planning, see:
 
 - `docs/experiments/plans/session-binding-channel-agnostic.md`
-
-ACP remains a next step in that plan and is intentionally not implemented in this shipped Discord thread-bound flow.

package/docs/gateway/configuration-examples.md

@@ -121,7 +121,6 @@ Save to `~/.symi/symi.json` and you can DM the bot from that number.
       byChannel: {
         whatsapp: "collect",
         telegram: "collect",
-        discord: "collect",
         slack: "collect",
         signal: "collect",
         imessage: "collect",
@@ -160,7 +159,6 @@ Save to `~/.symi/symi.json` and you can DM the bot from that number.
       idleMinutes: 60,
     },
     resetByChannel: {
-      discord: { mode: "idle", idleMinutes: 10080 },
     },
     resetTriggers: ["/new", "/reset"],
     store: "~/.symi/agents/default/sessions/sessions.json",
@@ -173,7 +171,6 @@ Save to `~/.symi/symi.json` and you can DM the bot from that number.
     typingIntervalSeconds: 5,
     sendPolicy: {
       default: "allow",
-      rules: [{ action: "deny", match: { channel: "discord", chatType: "group" } }],
     },
   },
 
@@ -196,9 +193,7 @@ Save to `~/.symi/symi.json` and you can DM the bot from that number.
       groups: { "*": { requireMention: true } },
     },
 
-    discord: {
       enabled: true,
-      token: "YOUR_DISCORD_BOT_TOKEN",
       dm: { enabled: true, allowFrom: ["steipete"] },
       guilds: {
         "123456789012345678": {
@@ -314,7 +309,6 @@ Save to `~/.symi/symi.json` and you can DM the bot from that number.
       allowFrom: {
         whatsapp: ["+15555550123"],
         telegram: ["123456789"],
-        discord: ["steipete"],
         slack: ["U123"],
         signal: ["+15555550123"],
         imessage: ["user@example.com"],
@@ -451,7 +445,6 @@ Save to `~/.symi/symi.json` and you can DM the bot from that number.
       botToken: "YOUR_TOKEN",
       allowFrom: ["123456789"],
     },
-    discord: {
       enabled: true,
       token: "YOUR_TOKEN",
       dm: { allowFrom: ["yourname"] },
@@ -476,10 +469,7 @@ If more than one person can DM your bot (multiple entries in `allowFrom`, pairin
       allowFrom: ["+15555550123", "+15555550124"],
     },
 
-    // Example: Discord multi-user inbox
-    discord: {
       enabled: true,
-      token: "YOUR_DISCORD_BOT_TOKEN",
       dm: { enabled: true, allowFrom: ["alice", "bob"] },
     },
   },

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