Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: <<<BEGIN_OPENCLAW_INTERNAL_CONTEXT>>>子代理报告的内容没了 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#72668•Fetched 2026-04-28 06:33:35
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
slzszyt-uxslzszyt-ux
Participants
slzszyt-uxslzszyt-uxsteipetesteipete
Timeline (top)
labeled ×2closed ×1commented ×1

升级到[email protected]之后的版本后，在主会话中子代理的回执报告不再展示了<<<BEGIN_OPENCLAW_INTERNAL_CONTEXT>>>的部分丢失，不知道是出于功能考虑还是其它，但是它确实是有用的。希望有配置控制而不是一刀砍，我的以下功能依赖于此。

折叠状态： <img width="847" height="528" alt="Image" src="https://github.com/user-attachments/assets/68acebf7-ce7c-4f0e-bbcb-375418243f0e" /> 展开状态： <img width="1128" height="477" alt="Image" src="https://github.com/user-attachments/assets/c1a8d056-9bdb-4872-aeed-e89098798784" />

让用户更方便的比较结果。现在它空了，因为<<<BEGIN_OPENCLAW_INTERNAL_CONTEXT>>>不再有内容。

Root Cause

升级到[email protected]之后的版本后，在主会话中子代理的回执报告不再展示了<<<BEGIN_OPENCLAW_INTERNAL_CONTEXT>>>的部分丢失，不知道是出于功能考虑还是其它，但是它确实是有用的。希望有配置控制而不是一刀砍，我的以下功能依赖于此。

折叠状态： <img width="847" height="528" alt="Image" src="https://github.com/user-attachments/assets/68acebf7-ce7c-4f0e-bbcb-375418243f0e" /> 展开状态： <img width="1128" height="477" alt="Image" src="https://github.com/user-attachments/assets/c1a8d056-9bdb-4872-aeed-e89098798784" />

让用户更方便的比较结果。现在它空了，因为<<<BEGIN_OPENCLAW_INTERNAL_CONTEXT>>>不再有内容。

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

升级到[email protected]之后的版本后，在主会话中子代理的回执报告不再展示了<<<BEGIN_OPENCLAW_INTERNAL_CONTEXT>>>的部分丢失，不知道是出于功能考虑还是其它，但是它确实是有用的。希望有配置控制而不是一刀砍，我的以下功能依赖于此。

折叠状态： <img width="847" height="528" alt="Image" src="https://github.com/user-attachments/assets/68acebf7-ce7c-4f0e-bbcb-375418243f0e" /> 展开状态： <img width="1128" height="477" alt="Image" src="https://github.com/user-attachments/assets/c1a8d056-9bdb-4872-aeed-e89098798784" />

让用户更方便的比较结果。现在它空了，因为<<<BEGIN_OPENCLAW_INTERNAL_CONTEXT>>>不再有内容。

Steps to reproduce

[email protected]中正常 [email protected]直到2026.4.25-beta.4 测试都没有回复内容。 分析了 OpenClaw 升级后的变化，发现内部上下文标记（<<<BEGIN_OPENCLAW_INTERNAL_CONTEXT>>>）在以下路径被清除： 流式传输 (agent → chat 事件)：通过 normalizeLiveAssistantEventText 清除 文本存储 (sanitizeSessionText)：写入会话文件前清除 投影显示 (projectChatDisplayMessage)：显示给客户端前再次清除

Expected behavior

<img width="728" height="346" alt="Image" src="https://github.com/user-attachments/assets/d32b9ca9-7895-4ea3-83cb-04e63b46bc02" />

<<<BEGIN_OPENCLAW_INTERNAL_CONTE XT>>>
...包含回执内容 <<<END_OPENCLAW_INTERNAL_CONTEXT >>>

Actual behavior

<img width="458" height="160" alt="Image" src="https://github.com/user-attachments/assets/59183e4e-60f1-4f25-a3fb-b32c3b4ef9bd" />

没有内容

OpenClaw version

2026.4.25-beta.4

Operating system

macOS 15.7.4

Install method

npm -g

Model

qwen3.6plus

Provider / routing chain

openclaw/qwen/qwen3.6plus

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be fixed by configuring OpenClaw to preserve the internal context marker (<<<BEGIN_OPENCLAW_INTERNAL_CONTEXT>>>) in the chat event text.

Guidance

  • Review the changes made in OpenClaw version 2026.4.24 and later to understand why the internal context marker is being cleared.
  • Check the normalizeLiveAssistantEventText, sanitizeSessionText, and projectChatDisplayMessage functions to see if there are any configuration options to preserve the internal context marker.
  • Consider adding a custom processing step to restore the internal context marker before displaying the chat event text to the user.
  • Verify that the issue is not specific to the qwen3.6plus model or the openclaw/qwen/qwen3.6plus provider routing chain.

Example

No code example is provided as the issue does not contain sufficient information about the specific code changes required.

Notes

The issue may be specific to the 2026.4.25-beta.4 version of OpenClaw, and the fix may not be applicable to other versions.

Recommendation

Apply a workaround to preserve the internal context marker, as the issue is likely due to a change in the OpenClaw library and not a configuration option.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

<img width="728" height="346" alt="Image" src="https://github.com/user-attachments/assets/d32b9ca9-7895-4ea3-83cb-04e63b46bc02" />

<<<BEGIN_OPENCLAW_INTERNAL_CONTE XT>>>
...包含回执内容 <<<END_OPENCLAW_INTERNAL_CONTEXT >>>

#agent setup#task chaining#parallel task#integration issue#index setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING