Boop Agent

There's a specific kind of side project that only makes sense once you've already built it for yourself, and Boop is one of those. The creator describes it plainly: this was never meant to be open-sourced, he built it to run his own life over iMessage, and enough people asked that he put the whole architecture on GitHub. It is not a polished product. It is a working template for a text-based agent that remembers things, drafts actions, and waits for your go-ahead before it does anything to the outside world.

The setup is the interesting part. Instead of wiring up a raw API key to Anthropic or OpenAI, Boop rides on your existing Claude Code or Codex/ChatGPT subscription login, so there's no separate billing to manage. Messages come in through Sendblue's iMessage bridge, land on a lean "dispatcher" agent that deliberately has no web access or integration tools, and get handed off to disposable sub-agents that actually do the work — search the web, touch Gmail, poke at GitHub, whatever the task needs. That separation is a small but deliberate safety choice: the part of the system that talks to you can't quietly go rogue on your accounts, because it's not allowed to touch them.

Memory is where the architecture gets genuinely clever. Boop keeps three tiers — short, long, and permanent — and runs a nightly consolidation job that's structured like a tiny courtroom: one model proposes memory merges, another argues against them, a third judges, and the result is deduplicated and pruned automatically. Integrations come via Composio, which means one API key theoretically opens roughly a thousand tools including Slack, Notion, Linear, and Stripe, all with OAuth handled for you through a debug dashboard that also visualizes the memory graph and tracks token costs per sub-agent.

Getting it running is not a five-minute affair. You need accounts with Sendblue, Convex, Composio, and ngrok, plus a CLI login for whichever model provider you pick, and the free ngrok tier rotates your public URL constantly — though Boop re-registers its webhook automatically so you're not pasting URLs into a dashboard every time you restart. There's also an in-progress native macOS app and an abandoned iOS app the creator is slowly rewriting. None of this is enterprise-grade, and the README says so directly: it's not optimized for cost or security, and you should budget and audit it like you built it yourself, because effectively, until you fork it, someone else did.