From cd65183f240b83fe492e2bf2a5315fe0e721dbc1 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Mon, 12 Jan 2026 01:28:52 +0000 Subject: [PATCH] docs: define E.164 in WhatsApp routing --- docs/concepts/multi-agent.md | 2 +- docs/providers/whatsapp.md | 2 +- docs/start/faq.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/concepts/multi-agent.md b/docs/concepts/multi-agent.md index 4e5ae7da2..d94674132 100644 --- a/docs/concepts/multi-agent.md +++ b/docs/concepts/multi-agent.md @@ -72,7 +72,7 @@ This lets **multiple people** share one Gateway server while keeping their AI ## One WhatsApp number, multiple people (DM split) -You can route **different WhatsApp DMs** to different agents while staying on **one WhatsApp account**. Match on sender E.164 with `peer.kind: "dm"`. Replies still come from the same WhatsApp number (no per‑agent sender identity). +You can route **different WhatsApp DMs** to different agents while staying on **one WhatsApp account**. Match on sender E.164 (like `+15551234567`) with `peer.kind: "dm"`. Replies still come from the same WhatsApp number (no per‑agent sender identity). Important detail: direct chats collapse to the agent’s **main session key**, so true isolation requires **one agent per person**. diff --git a/docs/providers/whatsapp.md b/docs/providers/whatsapp.md index 877a0c6ab..0ed5e4218 100644 --- a/docs/providers/whatsapp.md +++ b/docs/providers/whatsapp.md @@ -136,7 +136,7 @@ Pairing is a DM gate for unknown senders: - Codes expire after 1 hour; pending requests are capped at 3 per provider. **Can multiple people use different Clawdbots on one WhatsApp number?** -Yes, by routing each sender to a different agent via `bindings` (peer `kind: "dm"`, sender E.164). Replies still come from the **same WhatsApp account**, and direct chats collapse to each agent’s main session, so use **one agent per person**. DM access control (`dmPolicy`/`allowFrom`) is global per WhatsApp account. See [Multi-Agent Routing](/concepts/multi-agent). +Yes, by routing each sender to a different agent via `bindings` (peer `kind: "dm"`, sender E.164 like `+15551234567`). Replies still come from the **same WhatsApp account**, and direct chats collapse to each agent’s main session, so use **one agent per person**. DM access control (`dmPolicy`/`allowFrom`) is global per WhatsApp account. See [Multi-Agent Routing](/concepts/multi-agent). **Why do you ask for my phone number in the wizard?** The wizard uses it to set your **allowlist/owner** so your own DMs are permitted. It’s not used for auto-sending. If you run on your personal WhatsApp number, use that same number and enable `whatsapp.selfChatMode`. diff --git a/docs/start/faq.md b/docs/start/faq.md index 7be2acce4..b7856367a 100644 --- a/docs/start/faq.md +++ b/docs/start/faq.md @@ -114,7 +114,7 @@ Bun is supported for faster TypeScript execution, but **WhatsApp requires Node** ### Can multiple people use one WhatsApp number with different Clawdbots? -Yes, via **multi‑agent routing**. Bind each sender’s WhatsApp **DM** (peer `kind: "dm"`, sender E.164) to a different `agentId`, so each person gets their own workspace and session store. Replies still come from the **same WhatsApp account**, and DM access control (`whatsapp.dmPolicy` / `whatsapp.allowFrom`) is global per WhatsApp account. See [Multi-Agent Routing](/concepts/multi-agent) and [WhatsApp](/providers/whatsapp). +Yes, via **multi‑agent routing**. Bind each sender’s WhatsApp **DM** (peer `kind: "dm"`, sender E.164 like `+15551234567`) to a different `agentId`, so each person gets their own workspace and session store. Replies still come from the **same WhatsApp account**, and DM access control (`whatsapp.dmPolicy` / `whatsapp.allowFrom`) is global per WhatsApp account. See [Multi-Agent Routing](/concepts/multi-agent) and [WhatsApp](/providers/whatsapp). ### Does Homebrew work on Linux?