09:00E:Voice runtime bridgevs Telegram
Telegram was never built for agents. E:Voice is.
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.
The best AI products come from the people with a message and no voice.
- 0 relays
- between your phone and your runtime: no E:MERGENCE server and no chat platform
- 8 bridges
- maintained today, plus a public contract for everything else
- Pricing: details coming soon
- for the E:MERGENCE plan with AERIS OS, which pairing needs; start with a free account
14:00Head to head
The honest table.
Both columns are written to be fair. Where Telegram wins, it says so.
| Topic | 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 to 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 | sha256-verified, state-preserving bridge updates from one published manifest per runtime | You build and maintain your own bot plumbing |
| Organisation | 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 and sideload); desktop through AERIS OS | Everywhere, a real Telegram advantage |
| Price | Free E:MERGENCE account; pricing is coming soon | Free |
| Ecosystem | Young and moving fast: eight maintained bridges | Enormous and settled |
10:30What you need
Pairing needs AERIS OS, on the E:MERGENCE plan.
Pricing is coming soon. You can start with a free E:MERGENCE account today. Pairing your own agents, such as Claude Code or Codex, needs AERIS OS on your computer, which comes with the E:MERGENCE plan (Pricing: details coming soon): every app, including AERIS OS.
Downloading and inspecting the bridge needs no account. The pairing step does.
12:00How it works
Install, network, pair, talk.
Install the bridge.
Pick your runtime below. Each setup page has the package, its sha256 and the install lines, and the pairing handoff tells your agent to do it for you.
Put both on Tailscale.
Install Tailscale on the phone and the computer and sign both into the same account. Settings in E:Voice should read “App + private network active”. Same Wi-Fi is for local testing only: pairing rejects plain LAN and loopback addresses. A public HTTPS reverse proxy you run yourself is the advanced alternative.
Request a code on the phone.
Bridge → Add Agent → your runtime → give it a name → Request code. Review pairing handoff shows exactly what you are about to hand over; copy it to your agent.
Let it verify, then talk.
The agent binds on its Tailscale address, checks its own health, consumes the single-use code once and reports where it listens. The phone then checks that address itself: “Phone reachability confirmed.”
16:00Bridges
Eight runtimes are ready today.
Each runtime has its own setup page with the package, the sha256 and the exact install lines.
| Runtime | Bridge | Package | Contract | Links |
|---|---|---|---|---|
| Claude Code | 0.2.77 | 308 kB | 1.0.4 | Setup · current.json |
| Codex CLI | 0.3.25 | 207 kB | 1.0.4 | Setup · current.json |
| Cursor | 0.2.4 | 59 kB | 1.0.5 | Setup · current.json |
| Grok Bot | 0.1.3 | 34 kB | 1.0.4 | Setup · current.json |
| Hermes | 0.2.60 | 195 kB | 1.0.4 | Setup · current.json |
| OpenClaw | 0.2.23 | 159 kB | 1.0.4 | Setup · current.json |
| Agent Zero | 0.2.25 | 149 kB | 1.0.4 | Setup · current.json |
| Buzz | 0.1.22 | 189 kB | 1.0.4 | Setup · current.json |
Release 19 · shared core 2.6.1 · published 2026-09-19. From /evoice/plugins/manifest.json; each package's sha256 is in its manifest.
20:00Questions
The short answers.
Why do AI agent frameworks use Telegram bots at all?
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.
Can E:Voice actually replace a Telegram bot for my agent?
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 pairing contract.
Where does my agent traffic go?
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.
What does E:Voice honestly not do yet?
It is Android-only today, with desktop reach through AERIS OS, and the community is young. Pairing your own agents needs AERIS OS, part of the E:MERGENCE plan. Pricing: details coming soon. Telegram is free and runs everywhere; what it lacks is everything agent-shaped.
21:30More runtimes
One app, every agent you run.
Every bridge installs from this website and pairs the same way.
Claude Code
Codex CLI
Cursor
Grok Bot
Hermes
OpenClaw
Agent Zero
Buzz
Bring your own23:00Nightfall
Talk to your agents from anywhere.
Start with a free E:MERGENCE account. Add the E:MERGENCE plan when you are ready to pair your agents.
Pre-launch
Not launched yet
We're not launched yet. Everything is still being worked on. Sign up for the newsletter to hear first when it's ready.
We'll only use your email to tell you about launch. See Privacy.
Request beta access →