From 67f0af083e22a458abb16fd292c560cef0cd337b Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Tue, 28 Apr 2026 19:37:48 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@1e9faa2a5952b29acbef6780fb6ff024def45c8e --- .openclaw-sync/source.json | 4 ++-- docs/concepts/session-tool.md | 5 +++++ docs/reference/transcript-hygiene.md | 14 ++++++++------ 3 files changed, 15 insertions(+), 8 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 3ea614992..083d3ae06 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "cb8c513ce3f232079884bd10d7211dcec9ddbc93", - "syncedAt": "2026-04-28T19:29:14.256Z" + "sha": "1e9faa2a5952b29acbef6780fb6ff024def45c8e", + "syncedAt": "2026-04-28T19:36:11.541Z" } diff --git a/docs/concepts/session-tool.md b/docs/concepts/session-tool.md index a8a3b77ec..5f0cb3f20 100644 --- a/docs/concepts/session-tool.md +++ b/docs/concepts/session-tool.md @@ -93,6 +93,11 @@ the response: immediately. - **Wait for reply:** set a timeout and get the response inline. +Messages and A2A follow-up replies are marked as inter-session data in the +receiving prompt (`[Inter-session message ... isUser=false]`) and in transcript +provenance. The receiving agent should treat them as tool-routed data, not as a +direct end-user-authored instruction. + After the target responds, OpenClaw can run a **reply-back loop** where the agents alternate messages (up to 5 turns). The target agent can reply `REPLY_SKIP` to stop early. diff --git a/docs/reference/transcript-hygiene.md b/docs/reference/transcript-hygiene.md index 922c75eae..99d4c9735 100644 --- a/docs/reference/transcript-hygiene.md +++ b/docs/reference/transcript-hygiene.md @@ -96,13 +96,15 @@ agent-to-agent reply/announce steps), OpenClaw persists the created user turn wi - `message.provenance.kind = "inter_session"` -This metadata is written at transcript append time and does not change role -(`role: "user"` remains for provider compatibility). Transcript readers can use -this to avoid treating routed internal prompts as end-user-authored instructions. +OpenClaw also prepends a same-turn `[Inter-session message ... isUser=false]` +marker before the routed prompt text so the active model call can distinguish +foreign session output from external end-user instructions. This marker includes +the source session, channel, and tool when available. The transcript still uses +`role: "user"` for provider compatibility, but the visible text and provenance +metadata both mark the turn as inter-session data. -During context rebuild, OpenClaw also prepends a short `[Inter-session message]` -marker to those user turns in-memory so the model can distinguish them from -external end-user instructions. +During context rebuild, OpenClaw applies the same marker to older persisted +inter-session user turns that only have provenance metadata. ---