openclaw - 💡(How to fix) Fix suppressToolErrors does not work for mutating tools (message/exec) [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#73268Fetched 2026-04-29 06:21:43
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
Participants
Timeline (top)
cross-referenced ×1

Error Message

Every failed message tool call pushes a ⚠️ warning to the user via the channel, even if the agent handles the error gracefully. When retry logic causes 3+ failures, the user sees 3+ warnings. Skill-level error recovery (feishu-message-error-recovery) that switches methods after 1 failure instead of retrying.

Fix Action

Fix / Workaround

Current Workaround

Skill-level error recovery (feishu-message-error-recovery) that switches methods after 1 failure instead of retrying.

RAW_BUFFERClick to expand / collapse

Problem

agents.defaults.messages.suppressToolErrors has no effect on mutating tools like message. Source: pi-embedded-runner-BFOhIiuh.js:980 hardcodes that mutating tools always show warnings.

Impact

Every failed message tool call pushes a ⚠️ warning to the user via the channel, even if the agent handles the error gracefully. When retry logic causes 3+ failures, the user sees 3+ warnings.

Current Workaround

Skill-level error recovery (feishu-message-error-recovery) that switches methods after 1 failure instead of retrying.

Suggested Fix

Allow suppressToolErrors to work for message/mutating tools, or add a per-agent agents.<id>.directives.suppressMutatingWarnings flag.

extent analysis

TL;DR

Implementing a flag like agents.<id>.directives.suppressMutatingWarnings could help suppress warnings for mutating tools.

Guidance

  • Review the code at pi-embedded-runner-BFOhIiuh.js:980 to understand why suppressToolErrors is not working for mutating tools like message.
  • Consider adding a per-agent flag to control warning behavior for mutating tools, as suggested in the issue.
  • Evaluate the current workaround (feishu-message-error-recovery) and assess whether it can be improved or replaced with a more robust solution.
  • Investigate how suppressToolErrors is currently implemented and why it does not apply to mutating tools, to inform the design of a new flag or fix.

Example

No code example is provided due to lack of specific implementation details in the issue.

Notes

The suggested fix implies a need for a more fine-grained control over warning behavior, particularly for mutating tools. The current workaround may not be ideal, as it involves switching methods after a single failure.

Recommendation

Apply workaround: Implement a per-agent flag like agents.<id>.directives.suppressMutatingWarnings to control warning behavior for mutating tools, as this seems to be a targeted solution to the problem described.

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 suppressToolErrors does not work for mutating tools (message/exec) [1 participants]