openclaw - 💡(How to fix) Fix BlueBubbles: add config option to suppress outbound message-id receipt system events [1 comments, 2 participants]

Summary

The BlueBubbles plugin currently enqueues a system event for every outbound message:

System: [timestamp] Assistant sent "preview..." [message_id:X]

This happens in two places in monitor-processing-*.js:

1. Path A (~line 1769, maybeEnqueueOutboundMessageId): fired synchronously after send when a real messageId is returned
2. Path B (~line 1359, fromMe webhook handler): fallback fired when the sync response didn't return a usable id

These events are designed to give the agent a stable [message_id:X] reference for later reactions/edits/threaded replies. That's genuinely useful in some setups. But for deployments that don't use those features, the events appear as visible System: message bubbles in the user's iMessage thread (they get formatted by drainFormattedSystemEvents and injected into the next user turn, which then gets delivered to the channel).

Requested change

Add a BlueBubbles channel config option — e.g. channels.bluebubbles.outboundMessageIdEvents: false — that suppresses the two core.system.enqueueSystemEvent() calls when disabled.

The reply-context cache population (rememberBlueBubblesReplyCache) and pending-outbound buffer management (forgetPendingOutboundMessageId) should still run regardless of the flag, so the cache stays warm for deployments that re-enable later.

Workaround

Commenting out both enqueueSystemEvent calls in the plugin dist file stops the behavior but is wiped on every plugin upgrade.

Environment

• OpenClaw: 2026.5.7
• @openclaw/bluebubbles: 2026.5.6
• macOS Tahoe 26.3
• Private API: disabled (fallback path active, both paths confirmed)