Messaging infrastructureiMessage backends
macOS relay
Send through Messages.app and ingest chat.db changes on a real Mac host.
macOS relay — contract and behavior
- Send uses AppleScript against Messages.app while receive tails chat.db incrementally using ROWID and WAL/FSEvents behavior.
- Schema inspection handles macOS version drift before reading the chat table.
- The host needs a signed-in Messages account, Full Disk Access for chat.db, and Automation permission for Messages.app.
- The relay is production-ready for its supported surface but cannot provide private IMCore-only actions by itself.