openclaw - 💡(How to fix) Fix Feature request: Suppress error messages in group chats [1 participants]

When the agent encounters an API error (e.g., Anthropic streaming error like Unexpected event order, got message_start before receiving "message_stop"), the error message is sent to the current conversation, including group chats. This exposes technical error details to all group members, which is not ideal. Add a configuration option to control error message behavior in group chats:

Fix Plan

To address the issue, we will implement the proposed solution by adding a configuration option to control error message behavior in group chats.

Step-by-Step Solution

• Add the errorReplyPolicy configuration option to the agents section in the configuration file:

{
  "agents": {
    "defaults": {
      "errorReplyPolicy": {
        "groups": "suppress"
      }
    }
  }
}

• Alternatively, create a message:before_send hook event to intercept and modify/suppress outbound messages:

// Example hook function
module.exports = async function(message) {
  if (message.error && message.channel.type === 'group') {
    // Suppress error message in group chat
    return null;
  }
  return message;
};

• Update the agent code to check the errorReplyPolicy configuration option before sending error messages:

if (errorReplyPolicy.groups === 'suppress' && channel.type === 'group') {
  // Suppress error message in group chat
  return;
}

Verification

To verify that the fix worked, test the agent in a group chat and trigger an API error. The error message should not be sent to the group chat if the errorReplyPolicy is set to suppress.

Extra Tips

• Make sure to update the documentation to reflect the new configuration option and hook event.
• Consider adding additional logging to track suppressed error messages for debugging purposes.