Skip to content

Feature request: config option to suppress transient tool error warnings #39406

Description

@neoclaw-latrobe

Summary

When a tool fails transiently (e.g., an edit with mismatched content) but the agent retries and succeeds, the tool error warning is still delivered to the user's channel as a visible message:

⚠️ 📝 Edit: in ~/IDENTITY.md (521 chars) failed

This creates a confusing UX where the user sees:

  1. "Job done!" (success message from agent)
  2. "⚠️ Edit failed" (transient error bubble)

The agent self-corrected and succeeded, but the user sees an error.

Current behavior

  • Tool failure summaries are always visible in normal mode (per docs: "Tool failure summaries remain visible in normal mode")
  • suppressToolErrorWarnings exists but only applies to heartbeat runs
  • /verbose off only hides detail suffixes, not the warning itself

Requested feature

A config option to suppress tool error warnings when the agent's final reply indicates success:

{
  agents: {
    defaults: {
      toolErrorDelivery: "final", // "all" (default) | "final" | "off"
    },
  },
}
  • all: current behavior (show all tool errors immediately)
  • final: only show tool errors if the final reply doesn't indicate success
  • off: never show tool error warnings to users

Alternatively, extend suppressToolErrorWarnings to apply globally (not just heartbeats).

Use case

Hosted/managed OpenClaw deployments where non-technical users are confused by transient errors that the agent successfully recovered from.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.impact:ux-frictionUser-facing flow adds avoidable confusion or support burden without fully blocking progress.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions