let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: fix provider session key examples

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-11 02:31:45 +00:00
parent 57e6a9a762
commit 473f7df658
3 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/providers/discord.md
View File

@@ -53,7 +53,7 @@ Minimal config:
12. Reactions: the agent can trigger reactions via the `discord` tool (gated by `discord.actions.*`). 12. Reactions: the agent can trigger reactions via the `discord` tool (gated by `discord.actions.*`).
- Reaction removal semantics: see [/tools/reactions](/tools/reactions). - Reaction removal semantics: see [/tools/reactions](/tools/reactions).
- The `discord` tool is only exposed when the current provider is Discord. - The `discord` tool is only exposed when the current provider is Discord.
13. Native commands use isolated session keys (`discord:slash:${userId}`) rather than the shared `main` session. 13. Native commands use isolated session keys (`agent:<agentId>:discord:slash:<userId>`) rather than the shared `main` session.
Note: Discord does not provide a simple username → id lookup without extra guild context, so prefer ids or `<@id>` mentions for DM delivery targets. Note: Discord does not provide a simple username → id lookup without extra guild context, so prefer ids or `<@id>` mentions for DM delivery targets.
Note: Slugs are lowercase with spaces replaced by `-`. Channel names are slugged without the leading `#`. Note: Slugs are lowercase with spaces replaced by `-`. Channel names are slugged without the leading `#`.

2
docs/providers/imessage.md
View File

@@ -122,7 +122,7 @@ Groups:
Some iMessage threads can have multiple participants but still arrive with `is_group=false` depending on how Messages stores the chat identifier. Some iMessage threads can have multiple participants but still arrive with `is_group=false` depending on how Messages stores the chat identifier.
If you explicitly configure a `chat_id` under `imessage.groups`, Clawdbot treats that thread as a “group” for: If you explicitly configure a `chat_id` under `imessage.groups`, Clawdbot treats that thread as a “group” for:
- session isolation (separate `imessage:group:<chat_id>` session key) - session isolation (separate `agent:<agentId>:imessage:group:<chat_id>` session key)
- group allowlisting / mention gating behavior - group allowlisting / mention gating behavior
Example: Example:

9
docs/providers/msteams.md
View File

@@ -332,10 +332,11 @@ Key settings (see `/gateway/configuration` for shared provider patterns):
- `msteams.teams.<teamId>.channels.<conversationId>.requireMention`: per-channel override. - `msteams.teams.<teamId>.channels.<conversationId>.requireMention`: per-channel override.
## Routing & Sessions ## Routing & Sessions
- Direct messages use session key: `msteams:<userId>` (shared main session). - Session keys follow the standard agent format (see [/concepts/session](/concepts/session)):
- Channel/group messages use session keys based on conversation id: - Direct messages: `agent:<agentId>:msteams:dm:<userId>` (shared main session).
- `msteams:channel:<conversationId>` - Channel/group messages use conversation id:
- `msteams:group:<conversationId>` - `agent:<agentId>:msteams:channel:<conversationId>`
- `agent:<agentId>:msteams:group:<conversationId>`
## Reply Style: Threads vs Posts ## Reply Style: Threads vs Posts