Install the bridge for your runtime.
Eight maintained bridges ship from this site. Each runtime has its own setup page with the package, the SHA-256 and the exact install line.
E:Voice is how you talk to the agent you already run — a voice-first Android app where agents are the point, not a bot API bolted onto a chat network.
Your runtimeTraffic runs straight from your phone to the machine your runtime runs on, over networking you control.
Both columns are written to be fair. Where Telegram wins, it says so.
| E:Voice | Telegram bot | |
|---|---|---|
| Built for | AI agents: pairing, delivery routing, correlated requests, health checks | Human chat, with a bot API bolted on |
| Voice | Voice-first — speak to any paired agent, hear results read back | Voice notes at best; no native agent voice loop |
| Network path | Direct phone → runtime over your own network; no vendor relay | Every message transits Telegram's servers |
| Tool visibility | Thought boxes show tool calls and live commentary | Opaque text stream |
| Updates | Signed, verified, state-preserving bridge updates served from the web | You build and maintain your own bot plumbing |
| Organization | Projects, briefs, and shared AERIS Node memory across agents | Flat chat history |
| Native agents | Frank, Vera, and Pulse oversight included | None |
| Platforms | Android today (Play + sideload); desktop via AERIS OS | Everywhere — a real Telegram advantage |
| Price | Free to start; pairing external runtimes is Builders, $4.99/month | Free |
| Ecosystem | Young and moving fast — eight maintained bridges | Enormous and settled |
Eight maintained bridges ship from this site. Each runtime has its own setup page with the package, the SHA-256 and the exact install line.
Tailscale (or similar) is the recommended default. Local-network testing works on the same Wi-Fi; advanced users can run their own public HTTPS reverse proxy. There is no E:MERGENCE relay — traffic goes straight from your phone to your runtime.
The bridge consumes the setup code once, then the pairing is yours.
Add Agent → your runtime → Request codeRun the package verifier or the runtime health check, then send a test message. From there it's voice or text, whichever the moment allows.
Because Telegram was the easiest chat surface with a bot API when agent frameworks needed a mobile window. It was never designed for agents — it just happened to be there.
If your runtime is Claude Code, Codex CLI, Cursor, Grok Bot, Hermes, OpenClaw, Agent Zero or Buzz, a maintained bridge already exists. Anything else can implement the public Universal Bridge contract.
Directly from your phone to the machine your runtime runs on, over networking you control (Tailscale recommended). There is no E:MERGENCE relay and no chat platform in the middle — unlike a Telegram bot, where every message transits Telegram's servers.
It's Android-only today (with desktop reach through AERIS OS), the community is young, and pairing external runtimes is part of the paid Builders plan at $4.99/month. Telegram is free and runs everywhere — what it lacks is everything agent-shaped.
Every bridge installs from this website and pairs the same way.
Free to start — Frank, premium voice, projects and memory included. Pair your own runtimes with Builders at $4.99/month. The pricing page is the authoritative source for every figure.