Troubleshooting
imsg not found or RPC unsupported
imsg not found or RPC unsupported
Validate the binary and RPC support:If the probe reports RPC unsupported, update
imsg. If private API actions are unavailable, run imsg launch in the logged-in macOS user session and probe again. If the Gateway is not running on macOS, use the Remote Mac over SSH setup instead of the default local imsg path.Messages send but inbound iMessages do not arrive
Messages send but inbound iMessages do not arrive
First prove whether the message reached the local Mac. If If phone-sent messages create no new rows, repair the macOS Messages and Apple Push layer before changing OpenClaw config. A one-shot service refresh is often enough:Send a fresh iMessage from the phone and confirm a new
chat.db does not change, OpenClaw cannot receive the message even when imsg status --json reports a healthy bridge.chat.db row or imsg watch event before debugging OpenClaw sessions. Do not run this as a periodic bridge-relaunch loop; repeated imsg launch plus gateway restarts during active work can interrupt deliveries and strand in-flight channel runs.Gateway is not running on macOS
Gateway is not running on macOS
The default Then run:
cliPath: "imsg" must run on the Mac signed into Messages. On Linux or Windows, set channels.imessage.cliPath to a wrapper script that SSHes to that Mac and runs imsg "$@".DMs are ignored
DMs are ignored
Check:
channels.imessage.dmPolicychannels.imessage.allowFrom- pairing approvals (
openclaw pairing list imessage)
Group messages are ignored
Group messages are ignored
Check:
channels.imessage.groupPolicychannels.imessage.groupAllowFromchannels.imessage.groupsallowlist behavior- mention gating: explicit patterns or the routed agent’s identity name/emoji; set
requireMention: falsefor the chat in the effective root or accountgroupsmap to process all messages from allowed senders
Remote attachments fail
Remote attachments fail
Check:
channels.imessage.remoteHostchannels.imessage.remoteAttachmentRoots- SSH/SCP key auth from the gateway host
- host key exists in
~/.ssh/known_hostson the gateway host - remote path readability on the Mac running Messages
macOS permission prompts were missed
macOS permission prompts were missed
Re-run in an interactive GUI terminal in the same user/session context and approve prompts:Confirm Full Disk Access + Automation are granted for the process context that runs OpenClaw/
imsg.Configuration reference pointers
Related
- Channels Overview — all supported channels
- BlueBubbles removal and the imsg iMessage path — announcement and migration summary
- Coming from BlueBubbles — config translation table and step-by-step cutover
- Pairing — DM authentication and pairing flow
- Groups — group chat behavior and mention gating
- Channel routing — session routing for messages
- Security — access model and hardening