E:Voice runtime bridge · Buzz

Buzz keeps working.
You keep moving.

E:Voice is how you talk to the Buzz runtime you already run — Buzz stays busy on your machine, the whole conversation comes to your phone.

Voice + textDirect phone → runtimeSigned updates
Paired runtime
Buzz
Runs on your machine
Bridge
v0.1.6Signed, state-preserving updates
Where the sentence goes

Phone. Your bridge.
Buzz. Back.

Traffic runs straight from your phone to the machine Buzz 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 · Buzz
Buzz, on the machine it already lives on.A website-served adapter with verified downloads, preserving runtime state across updates.
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

Buzz, queue the render job and tell me when the frame checks pass.

Thought box

buzz · queue — render:master · position 1

Buzz

Queued and rolling. Frame checks are passing at 96% so far — the full pass lands in about ten minutes and I'll ping this thread.

Illustrativea written example of a typical Buzz exchange, not a captured session.

Sending a work order to a paired agent from E:Voice
Pairing

Install, network, pair, talk.

Package and SHA-256 live in the manifest: /evoice/plugins/buzz/evoice-bridge-plugin/current.json

01

Install the bridge package.

Unzip the package on the machine where Buzz runs and follow its README. Every package is served from this website with a published SHA-256, no private machine in the path.

02

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.

03

Pair from E:Voice.

The bridge consumes the setup code once, then the pairing is yours.

Add Agent → Buzz → Request code
04

Verify 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 Buzz?

No. The bridge runs on the machine where Buzz 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 Buzz 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.

Free to start

Talk to Buzz from anywhere.

E:Voice Free is the real app — Frank, premium voice, projects, memory. Pairing external runtimes like Buzz is part of the Builders plan at $4.99/month. The pricing page is the authoritative source for every figure.