Future Consideration: Messaging Architecture (Slack → Discord)

Future Consideration: Messaging Architecture

Current Setup (as of 2026-03-04)

• Slack free tier — notification layer for n8n workflows
• Active channels: #agent-alerts, #wordpress-updates, #forum-responses, #content-strategy, #vault-inbox
• 6 active n8n workflows posting to Slack, plus built-in Slack MCP in Claude Code
• Claude Code (Mac + VPS) is the primary AI interaction layer
• Vault inbox system handles Patrick ↔ Asia communication

Why We Might Switch to Discord

Slack free tier limitations:

• 90-day message history (messages older than 90 days are hidden)
• 10 app integration limit (currently at ~6-7)
• Persistent upsell banners

Discord free tier advantages:

• Unlimited message history
• Unlimited integrations/bots
• Better formatting options
• No upsell pressure
• Per-channel bot configuration possible

Reference: Velvetshark’s video on migrating from Telegram to Discord for AI agent workflows — YouTube. Key insight: channels as dedicated workspaces with per-channel model selection for cost optimization.

Why We’re Staying on Slack for Now (2026-03-04)

• Asia is comfortable with Slack’s interface, finds Discord harder to navigate
• All n8n workflows are already wired to Slack
• The built-in Claude Code Slack MCP works out of the box (no equivalent for Discord)
• Our critical data lives in git (vault + changelog), not in Slack — so the 90-day limit is less painful
• Migration effort is real: rebuild all workflows, re-train habits

Trigger to Revisit

• Hitting the 10-integration limit on Slack free
• Needing to search messages older than 90 days
• A built-in Discord MCP becomes available for Claude Code
• Multi-agent routing becomes available in Claude Code (see below)

Related: Multi-Agent Routing via Messaging

Desire: Communicate with different AI agents (different models, different specializations) through messaging channels — similar to what OpenClaw provides. Each channel or thread could route to a specific model (e.g., Opus for research, Haiku for quick tasks, Sonnet for general work).

Current state: Claude Code doesn’t yet support this natively. OpenClaw does, but was paused in favor of Claude Code as the primary intelligence layer.

What would make this viable:

• Claude Code or Anthropic releasing a multi-agent routing feature
• Ability to spawn persistent agents tied to messaging channels
• Per-channel model selection (like Velvetshark’s Discord setup, but integrated with Claude Code)

If/when this becomes available, Discord would be the stronger platform for it (unlimited history, no integration limits, better bot framework). This is the main reason to keep Discord migration on the radar.

Decision Log

Date	Decision	Reason
2026-03-04	Stay on Slack	Asia’s comfort, migration cost, current needs met
2026-03-20	Discord integration via Claude Code Channels	Anthropic launched Channels (research preview) with official Discord plugin — resolves “built-in Discord MCP” and “persistent agents tied to messaging channels” triggers. Plan: Claude-Code-Channels-Discord-Plan. Slack remains for existing n8n workflows; Discord added as the Claude Code Channels layer.