E:MERGENCE

09:00E:Voice runtime bridgeYour runtime

Any runtime. One contract.

E:Voice is how you talk to the agent you already run, including yours. Your framework can speak the same public pairing contract the eight maintained bridges do.

Read the contractPricing: details coming soon

The best AI products come from the people with a message and no voice.

Your runtime · on your machinepublic pairing contract v1
1 contract
public and versioned, linked from every entry in the plugin catalog
8 bridges
maintained today: Claude Code, Codex CLI, Cursor, Grok Bot, Hermes, OpenClaw, Agent Zero and Buzz
Pricing: details coming soon
for the E:MERGENCE plan with AERIS OS, which pairing needs; start with a free account

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 your own runtime, 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.

Compare the two plansAERIS OS

12:00How it works

Install, network, pair, talk.

  1. Install the bridge.

    Start from the closest maintained bridge below and implement the pairing contract. Publish each package with a sha256 so the agent installing it can check it.

  2. 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.

  3. Request a code on the phone.

    Bridge → Add Agent → Compatible E:Voice Bridge → give it a name → Request code. Review pairing handoff shows exactly what you are about to hand over; copy it to your agent.

  4. 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.”

14:00The contract

What your bridge has to answer.

Every runtime entry in the plugin catalog links its versioned pairing contract (pairingContractUrl). Start from the closest maintained bridge; the shape is the same for all of them.

Endpoints

  • GET /plugins/evoice-bridge/health, reachable from the phone
  • POST /plugins/evoice-bridge/bootstrap/consume on the runtime
  • optional GET /.well-known/evoice-bridge.json with protocolVersion evoice.universal-bridge.v1

Health must report

  • runtimeKind, version and pairingMode (account or local)
  • phoneFacingBaseUrl, equal to the bridge URL you submit
  • phoneFacingBaseUrlAllowed: true

Before the code is spent

  • bind on a genuine Tailscale interface, on a free port from 20000 to 49000
  • never report loopback, wildcard, LAN, the account site or another runtime's URL
  • take the setup code on stdin, consume it once, never echo it

16:00Reference bridges

Eight maintained bridges to start from.

Every maintained E:Voice bridge, from the published manifests
RuntimeBridgePackageContractLinks
Claude Code0.2.77308 kB1.0.4Setup · current.json
Codex CLI0.3.25207 kB1.0.4Setup · current.json
Cursor0.2.459 kB1.0.5Setup · current.json
Grok Bot0.1.334 kB1.0.4Setup · current.json
Hermes0.2.60195 kB1.0.4Setup · current.json
OpenClaw0.2.23159 kB1.0.4Setup · current.json
Agent Zero0.2.25149 kB1.0.4Setup · current.json
Buzz0.1.22189 kB1.0.4Setup · 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.

Do I need a server or cloud account to connect my runtime?

No. The bridge runs where your runtime runs, and your phone connects to it directly over Tailscale or another private network you control.

Do I have to get my bridge approved?

No. The contract and the plugin catalog are public. Build against the pairing contract, check your health endpoint returns every required field, and pair it as Compatible E:Voice Bridge.

What does it cost?

Pricing is coming soon. You can start with a free E:MERGENCE account today. Pairing your own agents needs AERIS OS, which is part of the E:MERGENCE plan. Pricing: details coming soon. AERIS OS installs from here.

Does my agent traffic go through E:MERGENCE servers?

No. Normal traffic goes straight from your phone to your runtime. This website serves the packages, manifests and pairing contracts, and the account service issues setup codes. There is no E:MERGENCE relay.

21:30More runtimes

One app, every agent you run.

Every bridge installs from this website and pairs the same way.

E:Voice overviewThe pairing chapter of the manual

23:00Nightfall

Talk to your runtime from anywhere.

Start with a free E:MERGENCE account. Add the E:MERGENCE plan when you are ready to pair your runtime.

Start with a free accountSee the plansExplore E:Voice

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 →