From 285906e5468efb2e55fb4b611b29be9616d69cac Mon Sep 17 00:00:00 2001
From: Peter Steinberger <steipete@gmail.com>
Date: Mon, 12 Jan 2026 05:59:32 +0000
Subject: [PATCH] docs: move model-split example to multi-agent

---
 docs/concepts/multi-agent.md | 33 +++++++++++++++++++++++++++++++++
 docs/start/faq.md            | 33 +--------------------------------
 2 files changed, 34 insertions(+), 32 deletions(-)

diff --git a/docs/concepts/multi-agent.md b/docs/concepts/multi-agent.md
index e1ec74e64..354e87b42 100644
--- a/docs/concepts/multi-agent.md
+++ b/docs/concepts/multi-agent.md
@@ -188,6 +188,39 @@ multiple phone numbers without mixing sessions.
 }
 ```
 
+## Example: WhatsApp daily chat + Telegram deep work
+
+Split by provider: route WhatsApp to a fast everyday agent and Telegram to an Opus agent.
+
+```json5
+{
+  agents: {
+    list: [
+      {
+        id: "chat",
+        name: "Everyday",
+        workspace: "~/clawd-chat",
+        model: "anthropic/claude-sonnet-4-5"
+      },
+      {
+        id: "opus",
+        name: "Deep Work",
+        workspace: "~/clawd-opus",
+        model: "anthropic/claude-opus-4-5"
+      }
+    ]
+  },
+  bindings: [
+    { agentId: "chat", match: { provider: "whatsapp" } },
+    { agentId: "opus", match: { provider: "telegram" } }
+  ]
+}
+```
+
+Notes:
+- If you have multiple accounts for a provider, add `accountId` to the binding (for example `{ provider: "whatsapp", accountId: "personal" }`).
+- To route a single DM/group to Opus while keeping the rest on chat, add a `match.peer` binding for that peer; peer matches always win over provider-wide rules.
+
 ## Per-Agent Sandbox and Tool Configuration
 
 Starting with v2026.1.6, each agent can have its own sandbox and tool restrictions:
diff --git a/docs/start/faq.md b/docs/start/faq.md
index 9d431d054..93500055f 100644
--- a/docs/start/faq.md
+++ b/docs/start/faq.md
@@ -126,38 +126,7 @@ Yes, via **multi‑agent routing**. Bind each sender’s WhatsApp **DM** (peer `
 
 ### Can I run a "fast chat" agent and an "Opus for coding" agent?
 
-Yes. Create two agents with different default models, then bind inbound routes to each agent (by provider account or by specific peers). Example: WhatsApp routes to a fast daily chat agent, Telegram routes to an Opus coding agent:
-
-```json5
-{
-  agents: {
-    list: [
-      {
-        id: "chat",
-        name: "Everyday",
-        workspace: "~/clawd-chat",
-        model: "anthropic/claude-sonnet-4-5"
-      },
-      {
-        id: "opus",
-        name: "Deep Work",
-        workspace: "~/clawd-opus",
-        model: "anthropic/claude-opus-4-5"
-      }
-    ]
-  },
-  bindings: [
-    { agentId: "chat", match: { provider: "whatsapp", accountId: "personal" } },
-    { agentId: "opus", match: { provider: "telegram", accountId: "primary" } }
-  ]
-}
-```
-
-Notes:
-- If you only have one account for a provider, you can omit `accountId`.
-- For the same provider, route a specific DM or group to the Opus agent using `match.peer`, and leave the provider-level binding pointing at the chat agent.
-
-See [Multi-Agent Routing](/concepts/multi-agent), [Models](/concepts/models), and [Configuration](/gateway/configuration).
+Yes. Use multi‑agent routing: give each agent its own default model, then bind inbound routes (provider account or specific peers) to each agent. Example config lives in [Multi-Agent Routing](/concepts/multi-agent). See also [Models](/concepts/models) and [Configuration](/gateway/configuration).
 
 ### Does Homebrew work on Linux?