{"slug": "building-an-agent-that-reads-whatsapp-notifications-and-never-sends-on-its-own", "title": "Building an agent that reads WhatsApp notifications and never sends on its own", "summary": "Itamar, a construction business owner, built Focus 100, an Android app that uses a NotificationListenerService limited to user-selected apps to read incoming WhatsApp and email notifications and convert them into structured tasks via Claude. The system sends each message to a stateless server that returns structured JSON (task, promise, event, or noise), then applies deterministic code for date fixes, group rules, deduplication, and calendar conflicts, with every outgoing message requiring an editable card and manual Send button. The developer reports that a self-hosted Gemma model matched Claude Haiku on a small eval but suffered 110-170 second cold starts, prompting a switch to Claude at roughly $0.0006 per request with the open model kept as fallback.", "body_md": "I'm Itamar. I run a construction business, and most of my real tasks arrive in WhatsApp groups, voice notes and email. I built Focus 100 to read those and turn them into tasks. Here's what mattered technically.\n\nOn Android, a `NotificationListenerService` limited to the apps the user picks (WhatsApp, WhatsApp Business, mail apps). It only sees new messages that post a notification, so muted chats are invisible. That limit is a feature for privacy: no scraping, no linked device.\n\nEach message (with a bit of same-chat context) goes to a stateless server that asks Claude for structured JSON: task / promise-to-me / event / noise, title, due date, suggested reply. Then plain code checks it: weekday and \"tomorrow\" fixes, group rules (a task only when you're named, tagged, or everyone is asked), dedup, calendar clashes.\n\nPoki, the assistant, receives a contact summary (names, relations, which channels exist, the usual channel) but no numbers or addresses. The phone fills those in at execution time. Every outgoing message is a card with editable text and a Send button.\n\nOur own open model (Gemma on a serverless GPU) was about as accurate as Claude Haiku on a small eval, but cold starts were 110-170 s. We switched to Claude (~$0.0006/request) and kept the open model as a fallback.\n\nTasks live on the device. Optional sync is end-to-end encrypted (AES-GCM, key only on devices); the server holds one ciphertext per space; merge is last-write-wins per task with tombstones.\n\niOS doesn't let apps read other apps' notifications, so on iPhone it's a web app (paste, import an exported chat, or talk to Poki).\n\nIt's free, no account, no ads; web app in 15 languages. I'm the developer, and I'd love feedback on false positives in busy group chats.\n\nAndroid: [https://focus100-il.netlify.app/get?ref=devto](https://focus100-il.netlify.app/get?ref=devto)\n\nWeb: [https://focus100-ios.netlify.app](https://focus100-ios.netlify.app)", "url": "https://wpnews.pro/news/building-an-agent-that-reads-whatsapp-notifications-and-never-sends-on-its-own", "canonical_source": "https://dev.to/__d03cc26214f3/building-an-agent-that-reads-whatsapp-notifications-and-never-sends-on-its-own-3bog", "published_at": "2026-11-19 14:38:57+00:00", "updated_at": "2026-11-19 14:43:59.673546+00:00", "lang": "en", "topics": ["ai-agents", "large-language-models", "ai-products", "ai-tools"], "entities": ["Focus 100", "Itamar", "WhatsApp", "Claude", "Anthropic", "Gemma", "Poki"], "also_reported_by": [], "takeaway": "A self-hosted Gemma model matched Claude Haiku on a small eval but cold starts of 110-170 seconds made Claude at ~$0.0006/request the better default, with the open model kept as fallback.", "recommendation": {"advice": "Keep the LLM stateless and validate its structured JSON with deterministic code for dates, group rules, dedup and conflicts, and gate every outgoing message behind an editable card with a manual Send button.", "playbook": "agent-architecture", "playbook_url": "https://wpnews.pro/playbooks/agent-architecture"}, "alternates": {"html": "https://wpnews.pro/news/building-an-agent-that-reads-whatsapp-notifications-and-never-sends-on-its-own", "markdown": "https://wpnews.pro/news/building-an-agent-that-reads-whatsapp-notifications-and-never-sends-on-its-own.md", "text": "https://wpnews.pro/news/building-an-agent-that-reads-whatsapp-notifications-and-never-sends-on-its-own.txt", "jsonld": "https://wpnews.pro/news/building-an-agent-that-reads-whatsapp-notifications-and-never-sends-on-its-own.jsonld"}}