Install the bridge package.
Unzip the package next to your OpenClaw gateway and follow its README. Every package is served from this website with a published SHA-256, no private machine in the path.
E:Voice runtime bridge · OpenClaw
OpenClaw,
without the Telegram detour.
E:Voice is how you talk to the OpenClaw gateway you already run — it pairs straight with your phone, with no third-party chat network in the path.
Voice + textDirect phone → runtimeSigned updates
Paired runtime
OpenClawBridge
v0.2.13Signed, state-preserving updatesWhere the sentence goes
Phone. Your bridge.
OpenClaw. Back.
Traffic runs straight from your phone to the machine OpenClaw runs on, over networking you control.
01 · You
Say it out loud.Voice or text from the phone in your hand.02 · Your private bridge
Tailscale, or your own network.The bridge runs on your machine. No E:MERGENCE relay in the path.03 · OpenClaw
Your OpenClaw gateway, where it already runs.Pairing, message delivery, health routes and verified updates for the gateway.04 · Back to you
Read aloud, or read in full.Tool calls and thinking fold into thought boxes. The feed stays clean.What it looks like
One exchange, start to finish.
You · voice
What has my gateway been doing this morning?
Thought box
openclaw · health — gateway OK · 3 sessions
OpenClaw
Three sessions since 7am: the overnight research task finished and two inbox triages ran clean. Nothing is waiting on you.
Illustrativea written example of a typical OpenClaw exchange, not a captured session.
Pairing
Install, network, pair, talk.
Package and SHA-256 live in the manifest: /evoice/plugins/openclaw/evoice-bridge-plugin/current.json
Put the phone and the runtime on the same private network.
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.
Pair from E:Voice.
The bridge consumes the setup code once, then the pairing is yours.
Add Agent → OpenClaw → Request codeVerify and talk.
Run the package verifier or the runtime health check, then send a test message. From there it's voice or text, whichever the moment allows.
Questions
The short answers.
Do I need a server or cloud account to connect OpenClaw?
No. The bridge runs on the machine where OpenClaw already runs. Your phone connects to it directly over your own network — Tailscale or similar private networking is the recommended default.
Does my agent traffic go through E:MERGENCE servers?
No. Normal traffic is direct phone-to-runtime through the connection path you choose. This website only serves the signed plugin packages, manifests, and pairing contracts.
What does it cost?
E:Voice is free to start. Pairing external agent runtimes is part of the Builders plan at $4.99/month — see the pricing page for every plan; it is the authoritative source for figures.
Is this an official OpenClaw product?
No. This is an E:Voice-maintained bridge served from emergencerising.com. It does not imply official upstream support unless the runtime project separately lists E:Voice as supported.
Why not just use a Telegram bot?
Telegram gives an agent a chat window. E:Voice gives it a control layer — voice-first operation, pairing, delivery routing, health checks, tool transparency, and signed state-preserving updates, with no third-party chat network in the path.
More runtimes
One app, every agent you run.
Every bridge installs from this website and pairs the same way.
Claude Code
Codex
Buzz
Grok
Hermes
Agent Zero
Cursor
Bring your ownFree to start
Talk to OpenClaw from anywhere.
E:Voice Free is the real app — Frank, premium voice, projects, memory. Pairing external runtimes like OpenClaw is part of the Builders plan at $4.99/month. The pricing page is the authoritative source for every figure.