OpenClaw iMessage: BlueBubbles vs Claw Messenger

What these are

BlueBubbles is an open-source server that runs on a Mac and exposes iMessage through a REST + WebSocket API. OpenClaw recommends it over the legacy imsg CLI for richer features and more stable webhook delivery.

Claw Messenger is a managed service. Your OpenClaw agent connects over WebSocket to our infrastructure. We handle the Apple hardware, the message routing, and the phone number. You get iMessage, RCS, and SMS through one plugin.

Both work with OpenClaw. They solve the same problem in fundamentally different ways. (For context on all five iMessage approaches, see our full overview.)

Setup

BlueBubbles

You need a Mac running 24/7. The official docs recommend macOS Sequoia (15). From there:

1. Download and install the BlueBubbles server app
2. Sign into iMessage on the Mac
3. Grant Full Disk Access and Accessibility permissions
4. Create a Google Firebase project for push notifications
5. Enable the web API in BlueBubbles and set a password
6. Run openclaw onboard and select BlueBubbles, or configure manually with serverUrl and password
7. Set up webhook routing so BlueBubbles can reach your OpenClaw gateway

If you want reactions (tapbacks), message editing, and unsending, you also need to disable System Integrity Protection (SIP). The BlueBubbles docs describe this as "similar to jailbreaking your iPhone" and warn that it is done at your own risk. Disabling SIP also prevents iOS apps from running on Apple Silicon Macs.

Expect 1-3 hours for initial setup. Longer if you run into permission issues, which is common.

Claw Messenger

openclaw plugins install @emotion-machine/claw-messenger

// ~/.openclaw/openclaw.json
{
  "channels": {
    "claw-messenger": {
      "enabled": true,
      "apiKey": "cm_live_...",
      "serverUrl": "wss://claw-messenger.onrender.com"
    }
  }
}

That is the entire setup. You get an API key from the dashboard, add it to your config, and restart the gateway. No Mac, no Firebase, no SIP changes. About 5 minutes.

What each supports

Known issues

BlueBubbles

These are documented bugs, not theoretical concerns. Each links to a real GitHub issue.

• Missing messages. BlueBubbles sometimes detects database changes but does not process them. The server logs show "Not processing DB change" with a stale timestamp comparison. This means incoming iMessages silently disappear. Issue #703
• Attachment race condition. When someone sends a message with both text and an image, BlueBubbles fires two webhooks about 350ms apart. The first has only text. The second includes the attachment. OpenClaw processes the first one and drops the image. Image-only messages work fine. This was fixed in PR #4984, but required OpenClaw to add debouncing on its side. Issue #4848
• Ghost typing indicator. When someone reacts to a message with a tapback, the typing controller starts the "..." animation before the NO_REPLY path can suppress it. The person sees a typing bubble that never resolves into a message. A fix is in progress. Issue #11189
• Messages.app goes idle. On headless Macs (no monitor, SSH access only), Messages.app stops processing incoming events. The recommended workaround is a LaunchAgent that runs osascript -e 'tell application "Messages" to activate' every 5 minutes.
• Flagged as malware. macOS has flagged BlueBubbles server as malware in some cases. Issue #727
• macOS Tahoe (26) breaks editing. Message editing stopped working on Tahoe. Group icon updates report success but do not sync. OpenClaw auto-disables these actions when it detects Tahoe.

Claw Messenger

We are newer and smaller. The main trade-off is that you depend on our infrastructure. If our servers go down, your agent loses iMessage until we recover. We do not have the years of battle-testing that BlueBubbles has. We also do not have open-source code you can inspect or patch yourself.

Hardware requirements

Cost comparison

If you already own a Mac that runs 24/7, BlueBubbles costs nothing. If you need to buy one, the hardware cost outweighs Claw Messenger's subscription for the first 2-6 years depending on plan.

Security

BlueBubbles gives you full control. Your messages stay on your Mac. Nothing leaves your network unless you configure it to. But disabling SIP for the private API removes a layer of macOS system protection, and the webhook authentication relies on password query parameters. Localhost requests bypass password checks entirely, which matters if you run other services on the same machine.

Claw Messenger routes messages through our servers. Your messages pass through our infrastructure before reaching your agent. We use encrypted WebSocket connections, but you are trusting a third party with your message content. For personal use this is comparable to using any messaging API. For sensitive business communications, you should evaluate whether that trade-off works for you.

When to use which

Use BlueBubbles if: you already have a Mac running 24/7, you want full control over your message data, you are comfortable with macOS system administration, and you do not need SMS or RCS.

Use Claw Messenger if: you run OpenClaw on a Linux VPS, you do not own a Mac or do not want to maintain one, you want SMS and RCS alongside iMessage, or you want a phone number for your agent.

Both are real options. The right choice depends on what hardware you have and how much maintenance you are willing to do.