chore(sync): mirror docs from openclaw/openclaw@c87c9742ed

.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"
 }

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>`

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>