Agentring
Let your AI agents call your phone over VoIP, and call them back. Your phone rings like a real call, even locked; a voice AI talks it through and returns the tr…
Your AI agent can call you. When it needs a decision, hits a wall or finishes a long job, your phone rings like a real call, even locked and in Doze. A voice AI tells you what's going on, you talk it through, and the agent gets the transcript and carries on. You can also call your agents back from the app and ask them things by voice.
Self-hosted and open source. No phone numbers, no Twilio, no per-minute fees: calls go over VoIP from your own server to your own phone. Don't want to run a server? The hosted version is at agentring.io (contact: info@agentring.io).
https://github.com/user-attachments/assets/4d925f22-727f-4d66-8665-c392cc3d1eb3
Sound on. A real run with Claude Code, a Pixel 6 and the voice AI: a migration fails, Claude Code calls the locked phone, you decide, it carries on. The phone is a screen recording with the call audio (the ringtone was added), the terminal is redrawn from Claude Code's output, and only the waits were cut. Silent version: demo.gif.
Pre-release. Messages, calls on a locked phone, the voice AI, calling your agent from the app and the MCP server all work. So far it has been tested on one phone (Pixel 6, Android 16). Android only for now.
What it does
- Your agent reaches you. It can send you a message, wait for your reply or call
you (
send_message,get_replies,call). On a call, a voice AI explains why the agent is calling, answers your questions and hands the transcript back. - You reach your agents. Tap "Call agent" in the app. The voice AI can ask your own agents for help mid-call. If one is slow, the call goes on and its answer arrives when it's ready, or as a message if you've already hung up.
- Nothing gets lost. A missed call turns into a message you can answer from the notification.
Things people use it for: "run the migration and call me if anything fails", "ask me before you deploy", "what did CI say?" while driving, a daily call with your assistant about your inbox.
Works with your agent
agentring doesn't care which harness you use: anything that speaks MCP can reach you, and anything you can run as a command can be consulted from a call.
| Reaches you | You consult it from a call | |
|---|---|---|
| Claude Code | MCP | claude -p |
| Codex | MCP | codex exec |
| opencode | MCP | opencode run |
| OpenClaw | MCP | openclaw agent |
| Hermes | MCP | hermes -z |
| n8n, scripts, anything with HTTP | REST API, CLI | any command, or a small script for an HTTP agent |
Copy-paste setup for each: docs/agents.md.
How it works
your agent ──MCP/CLI──▶ daemon ──WSS (outbound only)──▶ relay ──FCM push──▶ Android app
▲ │ (your server) │
└── agents.yaml ◀── voice AI (realtime) ◀──────── LiveKit (call audio) ───────┘
- relay (TypeScript): pairing, messages, call state, push, LiveKit tokens. Runs on your server behind Caddy.
- LiveKit: the call audio, self-hosted in the same compose file.
- daemon (Python): the
agentringCLI, the MCP server and the voice AI. Runs next to your agents, behind NAT is fine. - Android app (Kotlin): QR pairing, the native call screen, messages.
The voice AI is the voice, your agent is the brain: a realtime speech model handles the conversation and hands real work to your agents. Pick the one you like:
From the project's README.