Guides
Is there an AI assistant for iMessage on the Mac?
Updated July 2026
Yes. It’s called Clarence, and it only runs on a Mac (I’ll explain why in a second). It reads your iMessage history and uses AI to help you write back, catch up on a thread, or notice who you’ve quietly drifted from.
An app that reads your messages only deserves to exist if you can trust it. So the rest of this page is how Clarence works, and the two things that decide whether it earns that trust: where your message data goes, and who presses send.
Why this only works on the Mac
Your iPhone won’t allow it. iOS keeps your message history sealed off from other apps. That is why a phone app can nudge you to text someone but can never see whether you already did, or what you said. (We get into that ceiling in app to remind me to text friends.)
The Mac is different. Messages keeps your full history in a local file on your
machine (chat.db), and macOS lets you grant an app permission to read it
through Full Disk Access. That one fact is the whole reason Clarence can exist.
On a Mac, software you choose can see the real state of your friendships: the
threads that went quiet, the replies you owe, years of how you and someone
actually talk.
That access is a big deal. So the rest of this page is about trust.
What Clarence actually does
- Drafts replies that sound like you. Grounded in the real thread and years of how you text that person, so it reads as your voice, not beige AI. You edit and send.
- Catches you up on a thread. What was said, what went unanswered, where it left off. Replying after three busy weeks stops being archaeology.
- Turns a spoken ramble into a text. You talk (“tell her congrats on the house, we’re overdue for a call”) and a draft appears, shaped for that thread. The transcription runs on your Mac, so your voice never leaves it.
- Notices who’s drifting. This is the real point of reading your history. It can see which friendships have gone silent and say something before months turn into years.
- Gets you through a backlog. When you owe eight people a reply, doing them in one sitting, each one drafted and each one approved by you, turns a guilt pile into twenty minutes.
The two questions that decide it
Where does your message data go? Your messages are about the most personal data you own, and half of every thread is your friend’s words, which they never signed up to share. So with Clarence the analysis happens on your Mac, what it keeps is encrypted on your Mac, and your history is never uploaded. Nothing about a draft is kept once it’s written. If a privacy page can’t tell you that plainly, that tells you something.
Who presses send? This is the line between an assistant and an impersonator. Drafting, recapping, noticing: you are still the author. Auto-sending takes that away, and the moment a message goes out without you, your friend is talking to software. Clarence never sends on its own. You approve every send, and every send is logged where you can see it.
One more, quieter: can you leave? Turning off Full Disk Access cuts Clarence off, and deleting it deletes what it kept. Data you can’t take back was never yours.
Where Clarence stands
I built the whole thing on one bet: an app that reads your messages lives or dies on trust. So everything happens on your Mac, what it keeps is encrypted on your Mac, and your history is never uploaded. Voice runs on-device. You edit every draft, you press every send, and every send is logged. The point was never texting faster. It’s noticing the people you’re drifting from, and making it easier to reach back. I’m building it in the open, threat model and all.
Clarence is a private Mac app that notices who you’re drifting from and drafts the message to bring them back, on your Mac, never uploaded. If you want to see exactly how it treats your messages before you trust it, I published the whole privacy architecture: how Clarence treats your messages.
Frequently asked questions
Is it safe to give an app Full Disk Access on a Mac?
It's as serious as it sounds. Full Disk Access lets an app read essentially everything, which is why macOS gates it behind an explicit System Settings toggle rather than a one-tap prompt. It can be a reasonable grant, but only for software that earns it: published by an identifiable developer, specific about what it reads, local-first about where data goes, and revocable the moment you change your mind (the toggle works both ways). Never grant it to an app that's vague about any of those.
Does Apple allow apps to read iMessage?
On iPhone and iPad, no. iOS sandboxing makes your message history unreachable to third-party apps, full stop. On the Mac, yes, indirectly: your iMessage history lives in a local database file (chat.db) in your user library, and an app you've granted Full Disk Access can read it. Apple provides no official API for this; it's a deliberate property of the Mac being a more open platform than iOS.
Won't AI-written texts sound fake to my friends?
Generic AI text does. That pleasant, beige, no-friction voice is instantly recognizable and worse than not texting. What matters is whether a draft is grounded in your actual history with each person (your shared register, your inside shorthand, how you two actually talk) and whether you edit before sending. A draft you shape and approve is your message with the blank-page problem removed. An auto-generated one is a stranger wearing your name.
Can an app send messages without me?
Technically the capability exists, a Mac app can be built to send through Messages, which is exactly why you should ask who presses send. The trustworthy answer keeps a human on the button: the app drafts, you edit, you send, and every send is logged. Clarence has no auto-reply mode at all.