Install the bridge package.
Unzip the package on the machine where Codex CLI runs 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 · Codex CLI
Codex CLI,
without the desk.
E:Voice is how you talk to the Codex CLI you already run — thread continuity, workspace state and auth stay on your workstation.
Voice + textDirect phone → runtimeSigned updates
Paired runtime
Codex CLIBridge
v0.3.7Signed, state-preserving updatesWhere the sentence goes
Phone. Your bridge.
Codex CLI. Back.
Traffic runs straight from your phone to the machine Codex CLI 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 · Codex CLI
Codex CLI, on the workstation it already lives on.Thread continuity, workspace state, pairing and owner-controlled authentication are preserved.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
Start the release build and stay on it — flag me if anything fails.
Thought box
codex · exec — npm run build:release
codex · watch — build log streaming
Codex
Build is green in 4m12s. Two deprecation warnings in the uploader, nothing blocking. Artifacts are staged for release.
Illustrativea written example of a typical Codex CLI exchange, not a captured session.
Pairing
Install, network, pair, talk.
Package and SHA-256 live in the manifest: /evoice/plugins/codex/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 → Codex CLI → 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 Codex CLI?
No. The bridge runs on the machine where Codex CLI 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 OpenAI 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
Buzz
Grok
Hermes
OpenClaw
Agent Zero
Cursor
Bring your ownFree to start
Talk to Codex CLI from anywhere.
E:Voice Free is the real app — Frank, premium voice, projects, memory. Pairing external runtimes like Codex CLI is part of the Builders plan at $4.99/month. The pricing page is the authoritative source for every figure.