openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@6b41ef311f

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-23 00:40:54 +00:00
parent b26c9cd923
commit a08c8fe3bb
3 changed files with 6 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

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

10
docs/channels/channel-routing.md
View File

@ -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:

7
docs/channels/telegram.md
View File

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