💬 iMessage
Text your assistant like you text anyone else.
A message from your linked handle opens or continues an agent thread, and the answer comes back in the same iMessage conversation. The thread is an ordinary node, so the conversation is readable, searchable and shareable in the portal afterwards.
What ships
- The bridge — the Messages database is polled read-only for new incoming messages.
- Inbound routing from a linked handle into that person's own agent thread;
/newstarts a fresh one. - Reply delivery back through the Messages app.
- The assistant's tools —
LinkIMessage,IMessageStatus,SendIMessage(to your own handle only) andUnlinkIMessage. - A Connections card, so linking is offered where every other account is.
This one runs on YOUR Mac
Unlike every cloud channel here, iMessage has no API — so this module is hosted by the mesh running on your Mac (LocalMesh) and speaks to the Messages app signed in there. The cloud portal cannot run it, and says so rather than pretending to listen.
macOS asks for two permissions once: Full Disk Access to read the database, and Automation to let it send. See Setting up iMessage.
What it is not
It is not an Apple integration and Apple does not support it: it reads a local file and drives a local app. A macOS update can change either. For a sanctioned business channel — customers messaging a brand — Apple's Messages for Business is the route, and it would look like the WhatsApp module rather than this one.