Description

Internal operational errors are being surfaced to the user's DM channel when they should remain internal/hidden.

Observed Errors Leaking

1. Tool edit failures - When an edit tool call fails (e.g., "Could not find the exact text"), the error message appears in the user's DM channel instead of staying in internal logs.

2. Anthropic rate limit errors - HTTP 429 responses from Anthropic (e.g., rate_limit_error: This request would exceed your account's rate limit) are being sent to the user's DM channel.

Expected Behavior

These internal operational errors should:

• Be logged internally for debugging
• Trigger automatic retry logic where appropriate
• NOT be sent to the user's messaging channel

The user should only see intentional agent responses, not raw error messages from failed tool calls or upstream API issues.

Environment

• OpenClaw version: 2026.2.6-3
• Channel: Slack DM
• Model: claude-opus-4-5

Related

Possibly related to how errors are routed vs. intentional messages. Different from #12722 (systemEvent visibility) but may share routing logic.

Filed by Bendyclaw on behalf of @bendycode