Where does your OpenClaw iMessage delivery fail?
Set up native imsg on the signed-in Messages Mac, then trace synthetic IDs from phone send to gateway receipt to phone reply. Compare Sendblue on its assigned number using the same timing and carrier controls.
Measure inbound and outbound as separate legs
OpenClaw’s native integration starts imsg as a child process and communicates over standard input and output. On the signed-in Messages Mac, install the iMessage plugin, set up imsg for the user running the gateway, and grant the documented Full Disk Access and Automation permissions to the appropriate process. With a remote gateway, keep the imsg side in the Messages user’s context through the wrapper. Check channel status and then send three numbered plain-text probes from a test contact. Record send time, gateway observation time, and receipt of the corresponding reply on the phone. Use synchronized observation clocks or measure all events with a shared clock. A healthy-looking channel with no gateway observations shifts attention to the inbound path. Gateway observations without phone replies isolate the next investigation to processing or return delivery.
iMessage - OpenClawVerify the carrier on the alternate number
The OpenClaw Sendblue plugin advertises iMessage and SMS, and its setup describes an assigned phone number and contact verification. If a separate number is acceptable, use it as a second route in the exact same probe series. Match probe text, timeout, sender, and time window where possible. Record the observed transport for each outbound reply, using the test handset or verified delivery evidence. If the operator can establish only that the text arrived, mark the transport unknown. A fast SMS reply misses an iMessage-only requirement, while an SMS-capable support line can legitimately count both transports. Keep separate records for native and Sendblue trials, including the destination used for each, so a reply through a previously tested number cannot accidentally satisfy the current probe.
GitHub - njerschow/openclaw-sendblue: Sendblue channel plugin for OpenClaw - iMessage/SMS via Sendblue API · GitHubProve the local text path
Sign into Messages on the Mac, install the OpenClaw iMessage plugin, and use OpenClaw setup to install or update imsg when offered. For manual setup, install imsg under the account that will run the Gateway. Point the channel at that installation and grant the macOS permissions specified by the setup guide. The Gateway launches imsg rpc and communicates over standard input and output.
Send a unique plain-text message from a phone you control. Complete any access approval shown during the exchange, then send a fresh test message. The test passes when the expected agent response arrives in the original conversation and refers to the fresh message. Record that result before adding attachments, moving the Gateway, or changing the Mac's security settings.
iMessage - OpenClawTest the Mac separately from the remote Gateway
If the Gateway already runs remotely, use the documented SSH-wrapper topology with imsg installed in the Mac user context that the wrapper actually uses. First confirm that Messages on the Mac receives a fresh test message. Then repeat the agent round trip with the remote Gateway and a different test message. That order gives you a way to distinguish a Messages delivery problem from a bridge problem.
In an illustrative setup, a remote Linux Gateway connects to a Mac signed into a dedicated Messages account. The test phone sends BRIDGE-17 and the expected response is ACK BRIDGE-17. If the Mac displays the text but the agent stays silent, check the wrapper's login account, binary path, and permissions before changing anything on the phone. Repeat after a Gateway restart to check that the deployment works beyond the initial session.
iMessage - OpenClawSet a threshold for Private API mode
Separate a plain-text response from a native Messages action such as a tapback, poll, or attachment reply. OpenClaw documents a successful Private API check as a requirement for those native actions, and its setup describes disabling System Integrity Protection on the Mac. Keep the plain-text configuration when it meets the workflow. If a native action is essential, decide whether the Mac can be dedicated to that role and whether the security change is acceptable.
Define the acceptance test around the specific action. For a tapback, check that the reaction appears on the intended message on the receiving phone. A plain-text acknowledgment establishes that the bridge can respond. The successful Private API check and the visible reaction establish that the native action works.
iMessage - OpenClawTrial Sendblue against the same task
Sendblue is a separate OpenClaw channel option for iMessage and SMS. Its plugin setup calls for an API key, an API secret, and a phone number. Compare it with the native imsg bridge on sender identity, credential ownership, and the exact message behavior you need. Verify whether Sendblue can use the required number and whether its current terms allow the intended traffic before connecting a live inbox.
Use the same test phone and harmless prompt for each candidate. Record the number shown on the phone, whether the response lands in the intended conversation, and whether the required action is visible there. If plain text passes but a native action fails, treat the trial as a pass only for plain text. Test that action explicitly before selecting Sendblue for it.
GitHub - njerschow/openclaw-sendblue: Sendblue channel plugin for OpenClaw - iMessage/SMS via Sendblue API · GitHub