All Things OpenClawAll Things OpenClaw
IMESSAGE • OpenClaw quick fix
Featured: @OmarShahine

BlueBubbles gone? Move OpenClaw iMessage to `imsg` first.

OpenClaw's docs now say the BlueBubbles channel is no longer the supported iMessage path. The replacement is the bundled `imessage` plugin running `imsg` locally on a Mac with Messages.app signed in, or through an SSH wrapper from another host. Treat this like an integration cutover, not a casual update: install and permission `imsg`, translate config, smoke-test direct and group messages, then retire the old BlueBubbles server only after the new path works.

In simple words: Make a safe copy if the step could change your setup, try the smallest check, then confirm OpenClaw is back to normal before doing more. The source link and commands stay below for people who want the technical detail.

Checklist
Before updating or deleting anything, snapshot your OpenClaw config and write down the old `channels.bluebubbles` settings you rely on.
Install `imsg` on the Mac that is signed in to Messages.app, then verify it can see recent chats before wiring it into OpenClaw.
Install and verify `imsg` on the Messages Mac
brew install steipete/tap/imsg
imsg --version
imsg chats --limit 3
imsg rpc --help
Grant Full Disk Access and Automation permissions to the terminal/app context that will run both `imsg` and OpenClaw; most false starts are permissions, not bad config.
Translate `channels.bluebubbles` to `channels.imessage`: copy allowlists, group rules, attachment behavior, and any ACP binding from `channel: "bluebubbles"` to `channel: "imessage"`.
Minimal config shape to review, not paste blindly
{
  channels: {
    imessage: {
      enabled: true,
      cliPath: "/opt/homebrew/bin/imsg",
      dmPolicy: "pairing",
      allowFrom: ["+1-EXAMPLE-OPERATOR"],
      groupPolicy: "allowlist",
      groupAllowFrom: ["+1-EXAMPLE-OPERATOR"],
      groups: { "*": { requireMention: true } },
      includeAttachments: true
    }
  }
}
Restart using your normal supervisor, run `openclaw channels status --probe`, then test a direct message, a group message, attachments if used, and any advanced action before removing BlueBubbles.
Post-cutover smoke test
openclaw channels status --probe
# Then send/receive one low-risk direct message and one allowed group message.
# Keep BlueBubbles available until the new path passes your real workflow.
If OpenClaw runs on Linux or a VPS, point `channels.imessage.cliPath` at an SSH wrapper that runs `imsg` on the signed-in Mac; Linux `imsg` builds are read-only previews and cannot send messages by themselves.
Success looks like
• `imsg` works from the same macOS context that OpenClaw will use, with Messages.app access and permissions confirmed.
• The new `channels.imessage` config preserves the old safety gates: allowlists, group policy, attachment choices, and ACP bindings.
• BlueBubbles is disabled only after direct, group, attachment, and advanced actions you actually use pass a smoke test.

Source: OpenClaw docs + imsg docs · link