openclaw - 💡(How to fix) Fix Assistant text output is auto-sent to channel even when tool calls follow [1 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#73269Fetched 2026-04-29 06:21:41
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

Fix Action

Fix / Workaround

Current Workaround

Skill-level rule (one-reply-per-question + AGENTS.md 'output only NO_REPLY or message tool') that forbids any text output between tool calls.

RAW_BUFFERClick to expand / collapse

Problem

When an assistant response contains both text and tool calls, the text portion is automatically sent to the channel (e.g., Feishu) as an independent message. This causes 'narration leak' — internal thinking notes appear as standalone messages to the user.

Impact

Users see fragmented messages like 'Let me check...' or '验证一下' as separate channel messages without context.

Current Workaround

Skill-level rule (one-reply-per-question + AGENTS.md 'output only NO_REPLY or message tool') that forbids any text output between tool calls.

Suggested Fix

Add agents.<id>.directives.autoReply=false to suppress automatic text-to-channel delivery, or only send the final assistant text after all tool calls complete.

extent analysis

TL;DR

Setting agents.<id>.directives.autoReply=false may prevent automatic text-to-channel delivery and mitigate the 'narration leak' issue.

Guidance

  • Verify the current behavior by checking if text portions of assistant responses are being sent as independent messages to the channel.
  • Test the suggested fix by adding agents.<id>.directives.autoReply=false to the configuration and observing if the issue is resolved.
  • Consider implementing a mechanism to send the final assistant text only after all tool calls are complete, as an alternative solution.
  • Review the skill-level rule and AGENTS.md documentation to ensure consistency with the proposed fix.

Example

No code snippet is provided as the issue does not contain specific code references.

Notes

The effectiveness of the suggested fix may depend on the specific implementation and version of the system, which is not specified in the issue.

Recommendation

Apply workaround: Setting agents.<id>.directives.autoReply=false is a straightforward and targeted solution to prevent automatic text-to-channel delivery and address the 'narration leak' issue.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Assistant text output is auto-sent to channel even when tool calls follow [1 participants]