openclaw - 💡(How to fix) Fix Feature request: per-agent directive to disable [[reply_to_current]] tag [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#73272Fetched 2026-04-29 06:21:37
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

Fix Action

Fix / Workaround

Current Workaround

AGENTS.md 'never use [[reply_to_current]]' rule + hourly tripwire script that detects usage.

RAW_BUFFERClick to expand / collapse

Problem

The [[reply_to_current]] tag is automatically processed by the runtime and results in replies that don't render correctly in some channels (e.g., Feishu DM doesn't show quote blocks). Agents use message thread-reply instead, but sometimes accidentally output [[reply_to_current]] in their text.

Impact

Feishu DM users see standalone messages without quote context. The agent has to rely on skill-level rules to avoid using the tag.

Current Workaround

AGENTS.md 'never use [[reply_to_current]]' rule + hourly tripwire script that detects usage.

Suggested Fix

Add agents.<id>.directives.replyToCurrent=disabled to physically prevent the runtime from processing this tag for specific agents.

extent analysis

TL;DR

Disable the [[reply_to_current]] tag processing for specific agents by adding a directive to prevent incorrect rendering in certain channels.

Guidance

  • Identify the agents that are accidentally outputting [[reply_to_current]] and add the agents.<id>.directives.replyToCurrent=disabled directive to their configuration.
  • Verify that the directive is correctly applied by checking the agent's configuration and testing the reply functionality in Feishu DM.
  • Consider updating the AGENTS.md documentation to reflect the new directive and its purpose.
  • Review the hourly tripwire script to ensure it is still necessary after implementing the directive.

Example

No code snippet is provided as it is not necessary for this solution.

Notes

This solution assumes that the agents.<id>.directives.replyToCurrent=disabled directive is a valid configuration option and that it will effectively prevent the runtime from processing the [[reply_to_current]] tag.

Recommendation

Apply workaround: Add the agents.<id>.directives.replyToCurrent=disabled directive to prevent incorrect rendering in certain channels, as it provides a targeted solution to the problem without requiring a broader change.

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 Feature request: per-agent directive to disable [[reply_to_current]] tag [1 participants]