CDMX
All your chats. One AI. WhatsApp, Telegram and Instagram in one inbox that keeps track of what you promised.
01 — The idea
People get hundreds of messages a day across too many apps. The big things get handled. The small promises don't: "I'll send the deck tomorrow." Claire started as a WhatsApp assistant built around that problem.
It grew into a full client. WhatsApp, Telegram and Instagram land in one inbox on iOS, web and desktop, and an AI layer sits on top. You can ask questions across every chat, draft replies that fit who you're talking to, and let Open Loops catch commitments before they go stale.
I'm building it on my own and in public. The server is AGPL and the clients are Apache 2.0.
02 — What it does
Matrix bridges bring WhatsApp, Telegram and Instagram into one message format. You sign in with a QR or pairing code, an SMS code, or Instagram's own flow, and everything shows up in one list.
Claire catches "I'll…" and "can you…", tracks who owes what, reminds you before it's late, and closes the loop when the message that settles it arrives.
Ask anything across all your conversations. Answers come from hybrid keyword and vector search, and every citation is checked against the messages that were actually retrieved before you see it.
One identity per person across networks, a memory of how you talk to them, and a voice profile so suggested replies sound like you.
Auto-replies for keywords, birthdays and thank-yous with rate caps, and a plugin SDK with typed triggers, actions and permissions.
03 — In the hand
04 — Under the hood
Each outgoing message gets a transaction ID hashed from the user, network, chat, kind and the client's request ID, so retries and server restarts never send twice. On the phone, an outbox holds messages and reactions through a lost connection and replays them on reconnect.
A free, deterministic gate reads every message first, looking for commitment, request, time and resolution language. Only messages that pass reach one combined extract-and-reconcile model call. Whether a loop involves you is decided in plain code, not by the model.
Only the metadata needed to restore a bridge session is saved. Pairing codes and cookies stay in encrypted Redis and never touch Postgres. An operations console shows the health of every bridge.
The Electron app serves its bundle from a custom secure claire-app:// scheme. Under file:// the page gets an opaque origin, local storage isn't reliable, and people would be signed out on every launch.
Built with
05 — What I took from it
A messaging app lives or dies on the boring parts:the send that goes through on bad signal, the bridge that reconnects.The AI only matters once those work.
Contact
I like talking to founders early — before the deck, before the team. Tell me what you're working on.
Write to me