Support

Install

Install and launch Messages for AI

Messages for AI is a macOS app. Install the notarized app, move it to Applications, then launch it from your Applications folder. First launch walks you through the transports you want to enable.

What to expect

• iMessage is local to your Mac and needs Full Disk Access before thread reads work.
• WhatsApp is optional and pairs with a QR code if you choose to enable it.
• The menu bar app is the control center for drafts, scheduled messages, settings, and diagnostics.

Permissions

Grant Full Disk Access and Contacts

iMessage reads require Full Disk Access for Messages for AI.app. Add the app bundle itself in System Settings, not an inner helper binary or command-line symlink.

Full Disk Access

1. Open System Settings.
2. Go to Privacy & Security → Full Disk Access.
3. Add Messages for AI from Applications and turn the toggle on.
4. Quit and reopen Messages for AI and your assistant app if reads still fail.

Contacts

Contacts access lets the app show names instead of raw phone numbers. If names are missing, open System Settings → Privacy & Security → Contacts and turn on Messages for AI.

Assistant setup

Connect Claude or Codex

Messages for AI works through a local MCP/plugin bridge. Your assistant can request message context and stage drafts, while the Mac app remains the visible review and send surface.

• After changing permissions, fully quit and reopen Claude, Codex, or whichever client is running the local bridge.
• If a client cannot read threads, run its health check if available; it can usually identify missing Full Disk Access or Contacts access.
• Keep the default approval flow on unless you really want direct sends from the assistant.

Drafts and sending

Review drafts, scheduled messages, and sends

The app is built around the idea that AI proposes and you approve. Drafts appear in the menu bar app, grouped with their conversation context. You can review, send, discard, or schedule them according to your settings.

• Drafts are pending messages that have not been sent.
• Scheduled messages are approved messages waiting for their send time.
• Failures stay visible so you can retry or discard instead of losing track.

WhatsApp

Pair or unpair WhatsApp

WhatsApp support is optional. It pairs by QR code and uses an unofficial WhatsApp Web client. That means it may carry account risk, including the possibility that WhatsApp flags or restricts your number.

• Enable WhatsApp only if you understand that risk.
• If pairing stalls, turn WhatsApp off in Settings, turn it back on, and reopen the pairing window.
• If you no longer want WhatsApp connected, unpair it from Messages for AI and from WhatsApp's linked devices screen.

Labs

Use Texting Wrapped, Texting Analytics, and Labs

Labs build on local message access. Some are metadata-only, like Texting Wrapped and Texting Analytics. Others may use a model provider you configure.

• Texting Wrapped creates playful recap cards from local iMessage and WhatsApp metadata.
• Texting Analytics focuses on dashboards: reply speed, top people, volume, and ghost risk.
• Texting Style can use your API key to turn aggregate style patterns into a reusable drafting guide.
• EQ may send selected excerpts to your chosen model provider, because relationship analysis needs context.

Privacy

Understand product analytics

Product analytics are opt-in and off by default. If enabled, they use allowlisted metadata events such as feature viewed, draft staged, draft sent, Lab scan started, and diagnostics export created.

Analytics do not include message bodies, drafts, prompts, model responses, contact names, phone numbers, emails, chat IDs, message IDs, API keys, file contents, or user-identifying file paths. Session replay, screen capture, and autocapture are disabled.

Diagnostics

Export support diagnostics

Diagnostics exports are local files you create from Settings. They are not uploaded automatically. Use them when support asks for more context.

• Local app events are metadata-only events like launches, status checks, and export actions.
• Crash reports can help diagnose app failures.
• Daemon logs may include transport identifiers, so leave them off unless support asks.

Exports should exclude message bodies, prompts, drafts, and API keys. Still, review files before sharing if you have strict privacy requirements.

Updates

Updates, signing, and safety controls

Distributed builds are Developer ID signed and notarized by Apple. Updates are signed so the app can verify them before installing.

Sunrise Labs may require a newer app version or temporarily disable a risky feature if a security issue or third-party service problem appears. Update when prompted.

Payments

Tip jar payments

The tip jar is optional and handled by Stripe. It is a tip to Sunrise Labs, not a charitable donation. The app does not see or store your card details.