From 882b079581b298b51331a99fbb40106a27c2edfc Mon Sep 17 00:00:00 2001
From: "openclaw-docs-sync[bot]"
 <openclaw-docs-sync[bot]@users.noreply.github.com>
Date: Wed, 22 Apr 2026 22:47:34 +0000
Subject: [PATCH] chore(sync): mirror docs from
 openclaw/openclaw@c87c9742eddf7a432d6a1b18fbc957280626bff0

---
 .openclaw-sync/source.json       | 4 ++--
 docs/channels/channel-routing.md | 8 +++++++-
 docs/channels/telegram.md        | 7 +++++++
 3 files changed, 16 insertions(+), 3 deletions(-)

diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 93c9b33d9..b829fc1e6 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "46fba1d8145e145ec82e79c779c10476d129ba92",
-  "syncedAt": "2026-04-22T22:45:53.029Z"
+  "sha": "c87c9742eddf7a432d6a1b18fbc957280626bff0",
+  "syncedAt": "2026-04-22T22:47:34.225Z"
 }
diff --git a/docs/channels/channel-routing.md b/docs/channels/channel-routing.md
index 05dfe5c54..117850216 100644
--- a/docs/channels/channel-routing.md
+++ b/docs/channels/channel-routing.md
@@ -23,10 +23,16 @@ host configuration.
 
 ## Session key shapes (examples)
 
-Direct messages collapse to the agent’s **main** session:
+Most direct messages collapse to the agent’s **main** session:
 
 - `agent:<agentId>:<mainKey>` (default: `agent:main:main`)
 
+Telegram bot direct messages are isolated per bot account and sender even when
+`session.dmScope` is `main`, so sandbox and tool policy decisions can distinguish
+channel-originated DMs from the agent main session:
+
+- `agent:<agentId>:telegram:<accountId>:direct:<senderId>`
+
 Groups and channels remain isolated per channel:
 
 - Groups: `agent:<agentId>:<channel>:group:<id>`
diff --git a/docs/channels/telegram.md b/docs/channels/telegram.md
index 37fab1f16..335c77f33 100644
--- a/docs/channels/telegram.md
+++ b/docs/channels/telegram.md
@@ -72,6 +72,13 @@ openclaw pairing approve telegram <CODE>
 Token resolution order is account-aware. In practice, config values win over env fallback, and `TELEGRAM_BOT_TOKEN` only applies to the default account.
 </Note>
 
+## Session isolation
+
+Telegram bot DMs use per-account sender session keys, for example
+`agent:main:telegram:default:direct:814912386`. This keeps Telegram-originated
+tool and sandbox policy distinct from the agent main session even when the
+global `session.dmScope` setting is `main`.
+
 ## Telegram side settings
 
 <AccordionGroup>