E:MERGENCE

09:00E:Voice runtime bridgeOpenClaw

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.

Install the bridgePricing: details coming soon

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

OpenClaw · on your machinebridge v0.2.23
v0.2.23
the current OpenClaw bridge, straight from its published manifest
Direct
phone to your machine over Tailscale, with no E:MERGENCE relay and no chat platform in the path
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 OpenClaw, 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.

    Download it below, check its sha256, and follow the README on the machine where OpenClaw runs. Or skip the typing: the pairing handoff E:Voice copies tells your agent to do all of this itself.

    OpenClaw installs the package through its own plugin gate, so its code scan and install policy stay active.

  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 → OpenClaw → 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:00What it looks like

One exchange, start to finish.

Speak or type. Tool calls and thinking fold into a thought box, so the thread stays readable, and the reply can be read aloud while your hands are busy.

Illustrative: a written example of a typical OpenClaw exchange, not a captured session.

You · voiceWhat has my gateway been doing this morning?

Thought boxopenclaw · health — gateway OK · 3 sessions

OpenClaw · pairedThree sessions since 7am: the overnight research task finished and two inbox triages ran clean. Nothing is waiting on you.

16:00Install

The OpenClaw bridge.

Version, package and sha256 below come from the published manifest and are regenerated with every plugin release.

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 →

18:00Where your work lives

The agent stays yours.

Comes to the phone

  • tool calls as they happen and the agent's progress notes
  • Agent Updates, images and final replies
  • usage figures, where the bridge reports them

Stays on your computer

  • the gateway's configuration, pairing state and agent files
  • the agent's own identity: a paired agent keeps being itself
  • credentials, which are never copied into the package or the pairing report

Updates

OpenClaw owns plugin updates, security scanning and gateway restarts. Reinstall the verified package through openclaw plugins install … --force; managed gateways restart on their own.

20:00Questions

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, and your phone connects to it directly over Tailscale or another private network you control.

Does my agent traffic go through E:MERGENCE servers?

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

What does it cost?

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

How do I know the package is genuine?

Its sha256 is published in the runtime's current manifest on this site, and the install steps and your agent check it before anything is unpacked. The manifests do not carry cryptographic signatures yet, so the sha256 from this site is the check.

Is this an official OpenClaw product?

No. It is an E:Voice-maintained bridge served from emergencerising.com. It does not imply official support from the runtime's makers unless they list E:Voice themselves.

Why not just use a Telegram bot?

Telegram gives an agent a chat window. E:Voice gives it a control layer: voice first, pairing, delivery routing, health checks, tool transparency and verified, state-preserving updates, with no third-party chat network in the path. The honest comparison.

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 OpenClaw from anywhere.

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

Start with a free accountSee the plansExplore E:Voice