From e986aa175f48ef9582c976abe62a97d7fc04b7dc Mon Sep 17 00:00:00 2001
From: Jealous <CooLanfei@163.com>
Date: Fri, 13 Mar 2026 01:58:33 -0700
Subject: [PATCH] =?UTF-8?q?docs:=20fix=20session=20key=20:dm:=20=E2=86=92?=
 =?UTF-8?q?=20:direct=20(#26506)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/channels/googlechat.md   | 2 +-
 docs/cli/sessions.md          | 2 +-
 docs/concepts/session.md      | 6 +++---
 docs/gateway/configuration.md | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/channels/googlechat.md b/docs/channels/googlechat.md
index 09693589af7..bc9d435f4de 100644
--- a/docs/channels/googlechat.md
+++ b/docs/channels/googlechat.md
@@ -145,7 +145,7 @@ Configure your tunnel's ingress rules to only route the webhook path:
    - `audienceType: "app-url"` → audience is your HTTPS webhook URL.
    - `audienceType: "project-number"` → audience is the Cloud project number.
 3. Messages are routed by space:
-   - DMs use session key `agent:<agentId>:googlechat:dm:<spaceId>`.
+   - DMs use session key `agent:<agentId>:googlechat:direct:<spaceId>`.
    - Spaces use session key `agent:<agentId>:googlechat:group:<spaceId>`.
 4. DM access is pairing by default. Unknown senders receive a pairing code; approve with:
    - `openclaw pairing approve googlechat <code>`
diff --git a/docs/cli/sessions.md b/docs/cli/sessions.md
index b8c1ebfac6f..6ea2df094f0 100644
--- a/docs/cli/sessions.md
+++ b/docs/cli/sessions.md
@@ -60,7 +60,7 @@ openclaw sessions cleanup --dry-run
 openclaw sessions cleanup --agent work --dry-run
 openclaw sessions cleanup --all-agents --dry-run
 openclaw sessions cleanup --enforce
-openclaw sessions cleanup --enforce --active-key "agent:main:telegram:dm:123"
+openclaw sessions cleanup --enforce --active-key "agent:main:telegram:direct:123"
 openclaw sessions cleanup --json
 ```
 
diff --git a/docs/concepts/session.md b/docs/concepts/session.md
index 5c60655858e..2a58c15cb4d 100644
--- a/docs/concepts/session.md
+++ b/docs/concepts/session.md
@@ -191,9 +191,9 @@ the workspace is writable. See [Memory](/concepts/memory) and
 - Direct chats follow `session.dmScope` (default `main`).
   - `main`: `agent:<agentId>:<mainKey>` (continuity across devices/channels).
     - Multiple phone numbers and channels can map to the same agent main key; they act as transports into one conversation.
-  - `per-peer`: `agent:<agentId>:dm:<peerId>`.
-  - `per-channel-peer`: `agent:<agentId>:<channel>:dm:<peerId>`.
-  - `per-account-channel-peer`: `agent:<agentId>:<channel>:<accountId>:dm:<peerId>` (accountId defaults to `default`).
+  - `per-peer`: `agent:<agentId>:direct:<peerId>`.
+  - `per-channel-peer`: `agent:<agentId>:<channel>:direct:<peerId>`.
+  - `per-account-channel-peer`: `agent:<agentId>:<channel>:<accountId>:direct:<peerId>` (accountId defaults to `default`).
   - If `session.identityLinks` matches a provider-prefixed peer id (for example `telegram:123`), the canonical key replaces `<peerId>` so the same person shares a session across channels.
 - Group chats isolate state: `agent:<agentId>:<channel>:group:<id>` (rooms/channels use `agent:<agentId>:<channel>:channel:<id>`).
   - Telegram forum topics append `:topic:<threadId>` to the group id for isolation.
diff --git a/docs/gateway/configuration.md b/docs/gateway/configuration.md
index d7e5f5c25d3..0f1dd65cbbc 100644
--- a/docs/gateway/configuration.md
+++ b/docs/gateway/configuration.md
@@ -472,7 +472,7 @@ Control-plane write RPCs (`config.apply`, `config.patch`, `update.run`) are rate
     openclaw gateway call config.apply --params '{
       "raw": "{ agents: { defaults: { workspace: \"~/.openclaw/workspace\" } } }",
       "baseHash": "<hash>",
-      "sessionKey": "agent:main:whatsapp:dm:+15555550123"
+      "sessionKey": "agent:main:whatsapp:direct:+15555550123"
     }'
     ```