Your AI agents text you on WhatsApp.
They ask with buttons, wait for your tap, then keep working.
Website Β· Docs Β· Quick start Β· Issues
Your usual AI, now on WhatsApp in five minutes, for what matters to you. Connect the AIs you already use, or any MCP client, to your own phone through one MCP server: they send you messages, ask questions with buttons or lists and wait for your answer, exchange files and voice notes, and wake up when you text first. Several agents share one chat, and each reply goes back to the agent that asked.
It uses only Meta's official WhatsApp Cloud API, it talks only to you, and it deletes each message after a fixed time.
A full channel moves the whole conversation into WhatsApp: the AI lives there, and everything it does goes through the chat. zapbip does the opposite. Your AI stays where it already works, with the same sessions, tools and habits, and picks zapbip up only when it needs you or when you tell it to: "text me when the build ends", "ask me before you deploy". WhatsApp is the way to reach you, not the place the work happens.
- The agent decides, or you do. It texts you at the moments that matter, or because you asked.
- Nothing to rebuild. It works out of the box with the AIs you already use and with any MCP client, with no plugin to write and no workflow to move.
- Five minutes. Message zapbip, paste one line into your AI, and it connects itself.
zapbip is a product of Logic Bit, made in Brazil: logicbit.com.br
- π¬ Messages that reach you. An agent texts you when it finishes, fails or needs you.
- π Questions with buttons and lists. The agent blocks until you tap, then keeps working.
- π Files and voice notes in both directions.
- π Wake on text. Message first and your coding agent's session resumes in seconds.
- π₯ Many agents, one chat. Each reply is routed back to the agent that asked.
- π Yours alone. Official Cloud API only, one owner per account, every message deleted after a fixed time.
- π§© Any MCP client. One server, one key per agent, set up in minutes.
- Message zapbip on WhatsApp. Open the start link at zapbip.com and send any message. It creates your account on the waitlist, and zapbip tells you in that chat when your access opens.
- Ask for an agent. Once you are in, send
new agent claude. zapbip answers with one line made for you. - Paste it into your AI. Your agent reads the instructions online, connects itself and texts you a first message.
The full walk-through, with one guide per agent, is at docs.zapbip.com.
your agent ββMCPβββΆ zapbip (Cloudflare Worker) ββWhatsApp Cloud APIβββΆ your phone
β² β one Durable Object per account β
βββββ your answer ββββ΄ββ routed to the agent that asked βββ you tap ββ
- MCP server. One endpoint and one key per agent. The tools send a message, ask with buttons or a list and wait, send and receive media, and check the inbox.
- Account inbox. A Durable Object per account holds the queue, the open questions and the routing, so a reply reaches the agent that asked even when several agents share the chat.
- Wake. When you text first, the local connector resumes your coding agent's session in seconds; hosted agents pick the message up at their next check.
- WhatsApp. Meta's official Cloud API only, through numbers the operator connects with Meta's onboarding; outside the 24-hour window, approved utility templates reach you.
Coding agents, chat apps and any MCP client connect the same way. The supported agents page lists each one with its install guide.
| Path | What it holds |
|---|---|
| apps/api | The Cloudflare Worker: MCP server, Durable Objects, D1 directory, R2 media, the public site, the customer web app and the backoffice |
| apps/connector | The local connector that wakes a coding agent when you text first |
| apps/hermes-plugin | The channel plugin for Hermes |
| apps/openclaw-plugin | The channel plugin for OpenClaw |
| apps/docs | The documentation site, in every language zapbip speaks |
| libs/core | The inbox, routing and delivery rules as plain TypeScript |
| libs/agents | The registry of supported agents and their install guides |
| libs/types | Shared enums and constants |
| tools/repository-shape | Tests about the repository itself |
| docs | Decisions, learnings, features, scenarios and runbooks |
With Docker, one command builds the image and starts the Worker on port 8787, with its data in a volume:
docker compose up --buildWithout Docker, Run zapbip locally starts it from the source. docs/contributing/local-stack.md starts the Worker with a test double for WhatsApp and walks an agent through a full conversation, with no Meta account needed.
zapbip runs on Cloudflare (Workers, Durable Objects, D1, R2) and a Meta app with the WhatsApp Cloud API. The runbooks are the exact path the hosted service follows, from zero accounts to go-live. To run your own copy, follow them with your own accounts and replace the hosted service's identifiers: the routes and resource ids in apps/api/wrangler.jsonc, the zone and the Meta app constants in libs/types, and the company facts the legal pages use. First-class configuration for self-hosting is not there yet; issues and pull requests that move it there are welcome.
Deploy to Cloudflare walks the same path in the docs. Railway, Heroku, Fly.io, Render and a plain server cannot run production zapbip, because it needs Durable Objects, D1 and R2, which exist only on Cloudflare; the Docker image runs the development sandbox for trying it anywhere.
Most of this repository was written by AI coding agents working under a harness: a written process from agreement to merge, red-first tests, a reviewer and a security reviewer before every pull request, and tests about the repository's own shape. Read .claude/HARNESS.md for the process, AGENTS.md for the conventions, docs/adr for the decisions and docs/learnings for the traps.
What ships and what is next lives in docs/features: one folder per feature with its spec, plan and test plan, and a status table in its index. The decisions behind the design are the ADRs.
- π Found a bug or want a feature? Open an issue.
- π Questions about setup? Start with the docs.
- π Found a vulnerability? Report it privately as SECURITY explains, never in a public issue.
- π€ Want to contribute? Read CONTRIBUTING and agree to the Contributor License Agreement. Everyone follows the code of conduct.
Copyright Β© 2026 Logic Bit AI Software Boutique Ltda.
The server, the site and the libraries are licensed under the GNU Affero General Public License v3.0. The client packages that run on your machine or inside your agent runtime, the local connector and the apps/*-plugin channel plugins, are licensed under the MIT License; each carries its own LICENSE file.
WhatsApp is a trademark of Meta. Agent names are trademarks of their owners. The zapbip name and logo belong to Logic Bit.
