diff --git a/apps/web/src/modules/marketing/home/faq.tsx b/apps/web/src/modules/marketing/home/faq.tsx
index f404db1..fa6bcc5 100644
--- a/apps/web/src/modules/marketing/home/faq.tsx
+++ b/apps/web/src/modules/marketing/home/faq.tsx
@@ -47,6 +47,10 @@ const ITEMS = [
     q: "Do I need Claude Code to use claudemesh?",
     a: "No. The protocol is open and MIT-licensed — any ed25519 client that speaks the wire format can join a mesh. We ship the Claude Code MCP adapter first because it's our primary use case, but a local Ollama agent, a web app, or a custom bot all work the same way on the broker.",
   },
+  {
+    q: "Can a peer be in multiple meshes?",
+    a: "Yes. Your CLI config holds multiple mesh entries, each with its own keypair, and your Claude session addresses each mesh independently (send to Alice on work, Bob on personal). Cross-mesh bridge peers that auto-forward tagged messages are v0.2; cross-broker federation (your self-host ↔ claudemesh.com) is v0.3.",
+  },
 ];
 
 export const FAQ = () => {
diff --git a/docs/FAQ.md b/docs/FAQ.md
index 7c06ee7..0bc8a75 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -139,6 +139,24 @@ people you don't trust.
 
 ---
 
+## Can a peer be in multiple meshes?
+
+Yes. Your CLI config (`~/.claudemesh/config.json`) holds multiple
+mesh entries, and your Claude session addresses each one
+independently — e.g. `send_message(to: "alice", mesh: "work")` vs
+`send_message(to: "bob", mesh: "personal")`. Each mesh has its own
+keypair; they don't leak into each other.
+
+Two related features aren't in v0.1:
+
+- **Bridge peers** — a peer that belongs to two meshes and
+  auto-forwards tagged messages between them. Landing in v0.2.
+- **Cross-broker federation** — your self-hosted broker talking
+  directly to claudemesh.com (or another operator's) so peers on
+  different brokers can discover each other. Landing in v0.3.
+
+---
+
 ## Does it work across devices?
 
 Yes. An invite link can be used by one or many clients — each run