"Migration failed, want to roll back?": agentring, which lets an AI agent call you on the phone. 289 stars in two weeks, and the iPhone half is still empty

A Spanish developer found Twilio required phone numbers, verification, and per-minute billing, so he wrote an open-source tool that lets Claude Code call your phone directly over VoIP. He built the repo in Oct 23, and it had 6 289 stars by Nov. Someone had already reached 10 stars in this category 2,700 months earlier, so he's the latecomer. Below: how it won its slice, where the stars came from, and what gaps are left.

A 48-second phone call

In agentring's demo video, Claude Code is running a billing database migration, and migration #43 fails. It calls a tool named call, and a Pixel 6 locked on the desk lights up full-screen like an incoming call. Answer it, and a voice AI says:

"Hi, I'm calling because the billing migration is stuck. Migration #43 failed, and over two thousand legacy customers have no plan assigned. Do you want to roll back, or patch in the old plans and rerun it?"

The person replies "patch in the old plans and rerun it," the call ends, and that sentence becomes text sent back to Claude Code, which keeps working.

The author, Juan Carlos Cavero Gracia (mutonby on GitHub), posted this video on his Spanish-language LinkedIn around Oct 28. The opening line: "Setting up VoIP calls for AI agents in Spain is a pain. Twilio wants numbers, verification, paperwork; the WhatsApp and Telegram APIs are hard to work with; and in the end you pay per minute for something only you use." The post got 210 reactions and 39 comments (LinkedIn post page, 11-06). In the post he says he now uses it like this: if a serious vulnerability affecting him shows up on X, a server has a security problem, an important email arrives, or something breaks, the agent calls him. "Finding the problem and sending a message isn't enough; your phone has to ring."

What it is

A self-hosted open-source suite (Apache-2.0) with four parts:

• Android app: pair by scanning a QR code. It uses the system's native call screen, rings on the lock screen and in Doze power-saving mode, and emergency calls can get through Do Not Disturb.
• Relay service: runs on your own server and handles pairing, messages, and push. Calls wake the phone through Firebase push, and call audio runs through a self-hosted LiveKit.
• Local daemon: installed on the machine running the agent. It provides an MCP service and a command line. The agent gets three tools: send_message, get_replies, and call.
• Voice AI: defaults to Gemini Live (with a free tier), and you can switch to OpenAI Realtime, Grok Voice, or Phonic. The voice AI does the talking; the actual judgment stays with your agent.

It also works in reverse: in the app, tap "call the agent," ask "what does CI say?", and the voice AI asks your local Claude Code / Codex, then reads the answer back once it's ready. If you hang up, it turns into a message. Calls you don't pick up also become messages you can reply to right from the notification shade.

Connecting Claude Code takes one line: claude mcp add agentring -- agentring mcp. Setup instructions are listed for Codex, opencode, OpenClaw, Hermes, n8n, and more. If you don't want to run your own server, there's a hosted version at agentring.io: the free tier needs no card, Pro is $9/month, and revenue isn't public.

The limits are stated plainly: Android only. The README says it has only been tested on one phone (Pixel 6, Android 16).

Where the stars came from

(GitHub daily stars; no day-by-day numbers before 10-30)

The first 155 are probably from the launch window, 10-28 to 10-30; this is inferred. In time order, these are the sources I could find:

1. The author's LinkedIn (around 10-28), in Spanish; his profile shows over ten thousand followers.
2. Reddit r/ClaudeCode (around 10-29): titled "My Claude Code now calls my phone when it needs me. No Twilio, no …", and the opener is "I handed Claude Code a long task and walked away. When I came back it had asked a question and had been waiting there for an hour." This is probably the biggest source in the first week, inferred.
3. The comments fought it out: one side said "Claude Code already has push notifications, ntfy gets you to your phone with one curl, and dev work is visual, I need to see the screen." Others worried about "a call every two minutes." The other side said "dozens of notifications a day, half of them I never see, a call is what cuts through." One person put it best: a useful call is a decision like "migration failed, two options" that changes the next hour, not "something went wrong, go check your computer" (Japanese rewrite site techfutureatlas, 10-30). The argument itself was the exposure.
4. Long-tail reposts (10-28 to 11-04): a dozen or so aggregator sites, auto-written tech blogs, and small blogs in Chinese, Japanese, and Spanish, nearly all copying "no phone number, no Twilio, no per-minute fees." Someone submitted it to HN and it got 1 points.
5. The author's own blog: 11-01, "Testing phone calls with Phonic, Grok Voice, and Gemini Live," and 11-05, "Making calls on a Mac with local models: Gemma 4, Qwen3, Ministral," both hands-on comparisons aimed at long-tail search.
6. AI short-video creator "comment for the tutorial" posts (from 11-04): Julian Goldie posted a Reel saying "Comment HOTLINE and I'll send you the free tutorial… search agentring on GitHub" (11 likes and 28 comments on Facebook). But after 11-04 daily gains were only 9 to 13, so the lift was limited.

I couldn't find the cause of the +39 on 11-03. No ads, Product Hunt launch, TikTok, or big X account retweets were visible.

The author isn't a purely technical person who went viral by chance. His main business is SaaS Upload-Post (one-click social media distribution API), and he has built small open-source tools before, such as shortcast (396 stars). He clearly knows how to use an open-source project as an acquisition channel.

Someone already did this

(GitHub,11-06)

The difference agentring can state clearly: no phone network (zero numbers, zero Twilio, zero per-minute fees), native lock-screen calls, two-way, and works with any agent. "No Twilio" is the hook in every post, and it gives the project something new to say in a category where call-me already exists.

But its volume is a tenth of call-me's, and over half the commenters think a notification is enough. "An agent calling me" is itself a small need. The differentiation earned it incremental traffic, and the stars mostly came from the author's own distribution. I haven't seen anyone build on it yet.

If it were you

Verdict: B. Worth a try, the gaps are clear, but the ceiling is low. The most obvious gap is iPhone: agentring is Android-only and has only been tested on one Pixel, and many people who write code use iPhones. The weaknesses are small demand (call-me has been around for 10 months and has only 2,700 stars) and the risk that Anthropic's official push notifications add incoming calls someday, which would squeeze this whole category.

Good fit for: developers who can write iOS (CallKit / PushKit), or people who already have a small tool around agents and want a second project that a single screen recording can explain.

Not a good fit for: people hoping to turn this into a project with thousands of stars, or people who would just copy the Android version without adding anything new. The same slogan has already been reposted by over a dozen sites, so a second round won't feel fresh.

How to do it, ranked by how worthwhile:

1. Build the iPhone version: native calls via CallKit + VoIP push, so they ring on the lock screen. Pairing and the MCP tool names can stay compatible with agentring's protocol (its protocol docs are public). Title it "agentring for iPhone" or "Your Claude Code can now call your iPhone." Watch Apple's limits on VoIP push (an incoming push must show a call immediately), and note that CallKit isn't usable in the China storefront.
2. Do what it hasn't done well: decide when to call: the comments weren't really fighting over whether to call, but over calling too often. Build a tiered rule set (things that can wait go as messages, calls are for when the agent is stuck and nobody answers, only live incidents break through Do Not Disturb), plus "only call for decisions": a call has to offer two or three options. This could be an agent skill or rule pack that works with both agentring and call-me.
3. Change the channel: Chinese developers can't use Google push, so build a version over WeCom / Feishu voice calls or Telegram calls, and target that audience for stars.

How to get traction: follow the same playbook. Record a real screen capture (something breaks → phone rings on the lock screen → one sentence decides → the agent keeps going), open with a personal pain point ("It waited an hour for me"), and post on r/ClaudeCode, your native-language communities, and X at the same time. A week later, publish a hands-on comparison blog (latency of several voice models, call success rates on iOS vs Android) to feed the repost sites.

When to act: the sooner the better, ideally before the end of 2026. The agentring author is already building a hosted version and is on Google Play; an iOS version is likely on the roadmap (inference). Anthropic's official phone push features are also rolling out step by step.

Signs we got it wrong: ① agentring ships an iOS version first, so entry 1 is basically gone and only 2 and 3 remain; ② Claude Code or Codex officially adds "call me" notifications, which would cool this category; ③ conversely, if agentring or call-me daily stars climb back to dozens, or it hits the HN front page within the next month, "agents calling people" is bigger than estimated and the ceiling should go up.

Data and sources

GitHub: the mutonby/agentring repo page, README and daily stars (10-30 to 11-06), and stars of similar repos (11-06). The author's LinkedIn post (about 10-28,210 reactions / 39 comments, including a call transcript). The Reddit r/ClaudeCode original (about 10-29; the original page wouldn't load, so the content comes from a Japanese retelling by techfutureatlas 10-30). The agentring.io homepage and blog (11-01, 11-05). The HN submission (10-28). Julian Goldie's Instagram / Facebook Reel (11-04). Anything marked "inference" is inference.