diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 3a86f0a31..7e1768feb 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "67f09ea87af6f40c123424efa040d55719521651",
-  "syncedAt": "2026-04-23T00:39:05.540Z"
+  "sha": "6b41ef311f31de6d2e6693652377aaa9bbb3e472",
+  "syncedAt": "2026-04-23T00:40:53.637Z"
 }
diff --git a/docs/channels/channel-routing.md b/docs/channels/channel-routing.md
index 117850216..1b71e87d0 100644
--- a/docs/channels/channel-routing.md
+++ b/docs/channels/channel-routing.md
@@ -23,15 +23,13 @@ host configuration.
 
 ## Session key shapes (examples)
 
-Most direct messages collapse to the agent’s **main** session:
+Direct messages collapse to the agent’s **main** session by default:
 
 - `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>`
+Even when direct-message conversation history is shared with main, sandbox and
+tool policy use a derived per-account direct-chat runtime key for external DMs
+so channel-originated messages are not treated like local main-session runs.
 
 Groups and channels remain isolated per channel:
 
diff --git a/docs/channels/telegram.md b/docs/channels/telegram.md
index 335c77f33..37fab1f16 100644
--- a/docs/channels/telegram.md
+++ b/docs/channels/telegram.md
@@ -72,13 +72,6 @@ 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>