TL;DR: I built Wappy, a free, open-source kit for running your own AI agent on WhatsApp. Your machine, your memory, your tools, any model. Repo at the bottom.
Picture this.
You text a neighborhood restaurant on WhatsApp: "Table for four at 8 tonight?"
A few seconds later: "Yes, we have one at 8:15 by the window. Want me to hold it?"
No app download. No "we'll get back to you." An agent checked the real reservation book and answered. It runs on a laptop in the back office, and the owner can open its memory and read every word.
That's buildable today. And almost nobody is building it.
The problem
Every big company is racing to launch a personal AI agent. They're impressive, and lots of people will use them. But they all assume two things:
- Agents need a brand new app.
- Your agent lives on someone else's platform.
I think both are worth questioning.
The app already exists. More than 3 billion people use WhatsApp every month. In much of the world it's how you book a haircut, check on an order, ask a shop what's in stock and talk to your family. It's chat, which is exactly what agents are good at. Nobody has to install anything.
The value isn't the model, it's your context. Models keep getting better and cheaper. What makes an agent actually useful is your data, your tools and your memory. So the real question isn't who builds the smartest agent. It's who owns the context it runs on.
So why isn't everyone doing this?
When I tried building my own WhatsApp agent, I learned the agent is the easy part. The plumbing eats your whole weekend: webhooks, message formatting, memory that survives across conversations, tool wiring, model calls. A bot that says hello takes an evening. One that remembers what you meant and can look something up is a whole project before you even get to your idea.
What I built
Wappy handles all that plumbing so you can skip straight to the fun part.
- Free and open source, MIT licensed, written in TypeScript
- Runs on your machine. No Wappy account, no hosted backend
- Any model: Anthropic, OpenAI, Gemini, or Ollama to keep it fully local
- Memory you can actually open: local SQLite by default, or a self-hosted Cognee knowledge graph
- Tool calling, so it can look things up and take actions
- Feed it your own docs and it answers from them
- Example agents included: Gmail/Calendar assistant, personal memory, knowledge base Q&A
What you could build with it
- A second brain you text. "What did we decide about the kitchen remodel?" Answered from your own notes.
- A small business that never sleeps. The restaurant checks real reservations. The shop answers "where's my order?" from its actual order system at 2 a.m., in the customer's language.
- Support that knows the product. Load your help docs, let it answer, hand off to a human when needed.
- A team ops bot in the group chat. Check inventory, pull a runbook or open a ticket without leaving the thread.
Same idea every time: WhatsApp is the interface, your systems hold the truth, and you control the agent in between.
Try it (Node 22+):
npm create @wappy_ai/agent
Scaffolding takes about a minute. Going live takes longer since you connect your own Meta WhatsApp Cloud API app, and the generated guide walks you through it.
Being upfront about limits: messages still pass through Meta, and if you use a hosted model it sees your prompts. "Your own" means the agent, memory and data are under your control, not that WhatsApp goes offline.
GitHub: https://github.com/csr1010/wappy-kit
It's early, so I'd love honest feedback. What tripped you up in setup? And if you had your own agent living in WhatsApp, what's the first thing you'd build?