Repository navigation
v2.4.0
Two new opt-in features: WhatsApp (read-only) and an MCP server mode. Both are off until you turn them on.
WhatsApp, read-only
- LLMessenger can now read WhatsApp Desktop's local history on your Mac, the same way it reads iMessage, so WhatsApp chats show up in digests and owed replies.
- There is no local way to send through WhatsApp, so LLMessenger never sends there. It drafts the reply; you copy it and answer in WhatsApp.
- Enable it in Settings → Services. Requires WhatsApp Desktop installed and signed in, and Full Disk Access.
MCP server mode
LLMessenger --mcplets an MCP client you configure (Claude Desktop, Claude Code, Cursor) read your owed replies and latest digest, list conversations, and search your messages, all locally over stdio.- An agent can only propose a reply. It lands in your Act queue labelled as coming from an external agent, is never part of a batch send, and is sent only if you approve it.
- Conversations marked Local-only are never exposed, and are left out of digests while MCP is on. Global Local-only mode blocks all MCP reads.
- Enable it in Settings → AI & Privacy → Privacy, where the config snippet for your client is shown.
Also
- If the database fails to open, the app now explains and asks before moving it aside, instead of silently starting fresh. Automatic recovery still happens for a genuinely corrupt file.
Known issues, fixed on main and coming in the next release
These only matter if you turn MCP on:
- A connected agent could replace the text of its own pending proposal after you had read it.
- A digest could still be served over MCP after one of the conversations it was built from was marked Local-only.
Install
The app is unsigned: after unzipping, right-click LLMessenger.app → Open → Open on first launch (or System Settings → Privacy & Security → Open Anyway). Verify the download against SHA256SUMS.
Full Changelog: v2.3.3...v2.4.0