docs: fix provider session key examples

docs/providers/discord.md

@@ -53,7 +53,7 @@ Minimal config:
 12. Reactions: the agent can trigger reactions via the `discord` tool (gated by `discord.actions.*`).
     - Reaction removal semantics: see [/tools/reactions](/tools/reactions).
     - 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: Slugs are lowercase with spaces replaced by `-`. Channel names are slugged without the leading `#`.

docs/providers/imessage.md

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

docs/providers/msteams.md

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