Your LangGraph agent just got a phone number. Weirdly it has better boundaries than most group chats.
A post on r/AI_Agents this week (also crossposted to r/aiagents) shared an open-source starter that drops a normal LangGraph agent into WhatsApp. You scan one QR code and people message the agent like any other contact: text, voice note or photo. Voice gets transcribed, photos go to the model with the question, and if someone asks for a picture the agent makes one and sends it back.
The title says it "remembers each person without a database," which is the bit that got the clicks. Hot take: that's the least interesting thing in the repo. The good stuff is the boring plumbing, and that's what you should actually steal.
ok so what's in the box
It's TypeScript, Docker and MIT licensed. Three services run on your machine: WAHA (the WhatsApp gateway), an adapter, and the LangGraph Agent Server with your agent inside. WAHA forwards each message to the adapter as a signed webhook, the adapter runs your agent on that sender's thread, and the reply goes back to the same chat.
The agent is a standard LangChain createAgent in one file, src/agent/index.ts, so swap in your own tools or graph.
Out of the box it runs on sample replies, so you can test the wiring before pasting in a single key lol. For real answers the README uses OpenAI's GPT-6 Luna for chat and photos, plus Whisper Large V3 Turbo and FLUX.2 Klein 4B on Cloudflare for voice notes and images.
"without a database" is doing a lot of work
So about that memory claim. Every chat maps to its own LangGraph thread, and the thread ID is a keyed hash of the chat ID. Same person, same thread, and their phone number never shows up in the ID. That part is genuinely clean.
Long chats aren't kept in some clever custom store either. Per the post, summarizationMiddleware compacts the older messages and keeps the last few word for word. And "no database" really means the local Agent Server keeps state in a Docker volume, with disk writes slightly delayed, so a crash can lose the newest messages. The README says plainly that LangGraph's production Agent Server uses Postgres and Redis instead.
Also "remembers each person" means remembers each chat. Contact profiles that carry names and preferences across threads sit on the "where to take it next" list, not in the shipped code.
the other big asterisk is WAHA. It's an unofficial gateway that links like WhatsApp Web, it's not Meta's WhatsApp Business Cloud API. The author says to use a spare number and treat it as a way to try an idea with real people before moving to the official API. imo take that seriously, an unofficial linked device is a fine lab and a shaky foundation for a product.
More honest limits: private chats only, English voice notes only, failed replies not retried, and the message queue lives in memory so a restart can lose what's waiting.
none of this is a dunk btw. The author lists all of it out loud, which is more than most agent demos manage. My read is just that the headline undersells the real lesson.
the parts worth stealing (fr)
I'd copy these into any agent that texts real humans.
The model never picks the recipient. It returns text and maybe an image, and the adapter sends it to whoever wrote in. In the post's words: "A prompt injection can change what it says, but not who receives it." One line of architecture, a whole category of bad days gone.
One run per chat. Two runs on one thread fight over the same history, so each chat handles one message at a time, with up to four chats in parallel. Messages that land mid-reply wait their turn and piled-up texts get answered together, because people split one thought across five texts (guilty).
Closed by default. WAHA_ALLOWED_SENDERS starts empty, so nobody gets a reply until you add their ID. You can set it to * but the README says only do that with spending limits on your provider accounts, since there's no built-in spending cap.
Cap the expensive tool. Image generation is limited to once per run so one message can't trigger a pile of image calls.
The demo agent ships with a calculator and an image tool. Cute. The second you swap in real tools it gets kinda spicy.
Say your WhatsApp agent puts a dinner booking on someone's Google Calendar or logs a note in Notion. Now every sender needs the agent acting on their accounts, not yours, and you need to decide which tools a random texter is even allowed to trigger.
That's the spot MewCP fills. With a project toolset, its LangGraph guide has you send an x-mewcp-enduser-id header per user, and each call runs on the accounts that person connected and nobody else's. If they haven't connected the app yet, the tool result carries a connect link the model can pass along, which in a WhatsApp chat is lowkey perfect. You also pick which tools each agent gets, so "read and send, but not delete" is a setting instead of a prompt you hope holds.
what people are saying
The original r/AI_Agents thread had 14 points and 23 comments but wouldn't load for us, so this is off the r/aiagents crosspost.
There, one commenter said the keyed hash was the choice they'd steal first, then asked about messages dropped mid-reply and crashes losing recent ones. The author replied that the first is already fixed and that crash safety depends on where it runs, since LangGraph's production Agent Server saves to Postgres. Another commenter called the model-never-picks-the-recipient rule "such a smart call."
A search snippet from the original thread also shows someone mentioning voice note errors on a local setup, but we couldn't open it, so treat that as unverified.
Sources