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.
Open source, with no phone numbers, no Twilio and no per-minute telephony fees: calls go over VoIP straight to the app. Use the hosted version at agentring.io, or run everything on your own server.
agentring-demo.mp4
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.
With the hosted version there is no server, Firebase project or voice AI key to set up.
-
Install the app from Google Play (Android 8 or newer).
-
Sign in at agentring.io with your email (free plan, no card) and scan the QR code on your dashboard with the app. The phone is paired.
-
Add the MCP server to your agent. The dashboard shows the command with your key:
claude mcp add --transport http agentring https://agentring.io/mcp \ --header "Authorization: Bearer ak_…"
Then ask your agent: "run the migration and call me if anything fails."
The free plan has 1 phone, 10 call minutes a month with the voice AI included, and 100 messages a day. Other agents (Codex, opencode, OpenClaw, Hermes, n8n): docs/agents.md. To run it all yourself instead, see Self-hosting.
- 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.
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 |
| Grok Build | MCP, or the plugin | |
| 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. OpenClaw and
Hermes have one command for all of it: agentring connect openclaw / agentring connect hermes,
or install the skill and ask your agent to set agentring up.
The skill installs in any harness that reads skills with npx skills add mutonby/agentring
(skills.sh), and from ClawHub as @mutonby/agentring.
Everything on your own machines, free and without limits. You need:
- somewhere to run the relay: a Linux server with Docker and a domain name, or your own computer with Docker (the phone on the same Wi-Fi, or anywhere over Tailscale),
- a free Firebase project, which is what makes a locked phone ring (docs/firebase.md),
- a key for the voice AI: Gemini (free tier), or OpenAI, xAI (Grok) or Phonic (providers),
- an Android phone.
# 1. The relay, on a server with a domain (ports 80, 443, UDP 50000-50100 and TCP 7881 open)
cd deploy && cp .env.example .env && $EDITOR .env && docker compose up -d --build
# ... or on your own computer, at its LAN or Tailscale IP
cd deploy && cp .env.local.example .env.local && $EDITOR .env.local \
&& docker compose -f docker-compose.local.yml --env-file .env.local up -d --build
docker compose logs relay | grep -A2 "API key" # add the same -f/--env-file for the local one
# 2. The computer where your agent runs
uv tool install './daemon[voice]'
agentring init --relay https://relay.example.com --api-key ak_...
agentring pair # scan the QR code with the app
agentring msg "hello" # the phone gets a notification
echo GEMINI_API_KEY=... >> ~/.agentring/.env # or OPENAI_API_KEY / XAI_API_KEY / PHONIC_API_KEY
agentring call "Testing agentring" --ai # + --provider openai|grok|phonic
# 3. Your agent (Claude Code here; others: docs/agents.md)
claude mcp add agentring -- agentring mcpInstall the app from Google Play (recommended: it updates itself, and the same app works with agentring cloud and with your own relay). The APK on Releases is for those who'd rather not use Play; it's signed with a different key, so uninstall one before installing the other. The full tutorial, step by step for both options and with a troubleshooting table: docs/setup.md. If the phone doesn't ring when locked, it's usually the vendor's battery saver: docs/troubleshooting-oem.md.
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:
| Voice AI | --provider |
Key |
|---|---|---|
| Gemini Live (default, free tier) | gemini |
GEMINI_API_KEY |
| OpenAI Realtime | openai |
OPENAI_API_KEY |
| Grok Voice (xAI) | grok |
XAI_API_KEY |
| Phonic | phonic |
PHONIC_API_KEY |
| Your own server, e.g. HF speech-to-speech + a small model on llama.cpp (experimental) | local |
none |
Set AGENTRING_VOICE_PROVIDER in ~/.agentring/.env to use one for every call, from the
CLI and from MCP. How they compare (latency, tool use), how to measure them yourself
(agentring voice bench), the local setup and how to add another one:
docs/voice.md.
More: architecture · protocol · voice AI
Self-hosted, everything runs on your own servers and accounts (for the hosted version, see its privacy policy). Messages and call metadata are stored on your relay. Push notifications go through your own Firebase project; they are signed, not encrypted, so Google's FCM can read pushed text. Call audio goes through your LiveKit server and, with the voice AI, to the provider you chose (Google, OpenAI, xAI or Phonic); on Google's free tier, Google may use that data to improve its products.
Over the phone, the voice AI acts on what it hears, so give it only the tools and agents you'd trust someone holding your phone with. Details and the threat model: SECURITY.md.
- Android only (no iOS yet). Android Auto is in beta and only in the APK from Releases: Google Play doesn't allow calling apps for cars in production yet (docs/android-auto.md).
- It's a young project. The app is on Google Play, and we test it most on a Pixel 6 (Android 16); other vendors' battery savers can hold a call back (docs/troubleshooting-oem.md). If it misbehaves on your phone, please open an issue.
- Self-hosted, one user per relay: no accounts.
- The voice AI works best with a cloud realtime model (Gemini, OpenAI, Grok or Phonic). A local
one runs on your own machine (
--provider local), but it's experimental and slower; others plug in throughRealtimeBackend.
cd relay && npm ci && npm test # relay
cd daemon && uv run --extra voice pytest # daemon (+ e2e against the relay build)
cd app-android && ./gradlew :core:test :app:assembleDebugCI builds the APK and runs an end-to-end test on an Android emulator against a real relay. See CONTRIBUTING.md and docs/release.md.