Phase 6 / Ep 30: Multi-frequency Path Routing Strategy —— Cross-platform Management of a Single Agent

🎯 Learning Objective: Design a routing architecture for multi-platform access.

1. Routing Modes

Mode A: One Agent Connected to Multiple Channels

graph TD
    TG["📱 Telegram"] --> Agent["🤖 Personal Agent"]
    DC["💬 Discord"] --> Agent
    CLI["💻 CLI"] --> Agent

Applicable Scenarios: Personal use, where the Agent centrally manages all entry points.

Mode B: Multiple Agents Connected to Dedicated Channels

graph TD
    TG["📱 Telegram"] --> PA["🧑‍💼 Personal"]
    DC_dev["💬 Discord #dev"] --> CA["💻 Code Agent"]
    DC_ops["💬 Discord #ops"] --> OA["🔧 Ops Agent"]
    CLI["💻 CLI"] --> CA

Applicable Scenarios: Team/Multiple scenarios, where different Agents specialize in different tasks.

2. Routing Rule Configuration

{
  "routing": {
    "rules": [
      {
        "channel": "telegram:private",
        "agent": "personal"
      },
      {
        "channel": "discord:dev",
        "agent": "code-agent"
      },
      {
        "channel": "discord:ops",
        "agent": "ops-agent"
      },
      {
        "channel": "cli",
        "agent": "code-agent"
      }
    ],
    "default": "personal"
  }
}

3. Message Deduplication

When operating on the same task across channels, duplicate messages may occur. OpenClaw uses a combination of Message ID + Channel ID for deduplication.

4. Failover

If the Telegram channel becomes unreachable:

• The Agent can still be accessed via CLI and Discord.
• The Gateway automatically detects and logs the event.
• Automatically reconnects upon recovery.

Next Episode Preview: Ep 31, Security Governance for Message Channels – Anti-abuse, Anti-leakage, Audit Tracking.