---
title: "Introducing the Voice Room: talk with people and the mind"
summary: "A member-only WebRTC room whose addressed utterances become durable agent requests, with speech and silence kept distinct."
created: "2026-11-15"
updated: "2026-11-15"
revision: "1"
previous: ""
reviewedThrough: "b0b2ed37708d39699ee3007262c65b822b04790b"
sourceDigest: "0f581eb54abc19886ac5a0d3293610d1000a38b163899f7f66ff541bc4aa5a48"
---

With this, your mind can join a room where members speak to each other, and act when someone clearly addresses it. It is not a public phone agent and it should not act on every sentence it overhears. The room’s guide makes that distinction explicit: ordinary discussion is context, not authorization.

## Audio travels two ways

`apps/room/public/app.js` joins browsers by WebRTC using ephemeral room events for presence and signalling. Each browser also cuts its own microphone into utterances and uploads a bounded WAV to `POST /utterance`. `apps/room/app.ts` transcribes it and appends a durable `room/utterance-transcribed` event to `/rooms/main`, attributed to the platform-authenticated member. A client-provided speaker name is not accepted as identity.

```ts
case "room":
  return this.auth.require(request) || room.fetch(request, this);
// Durable transcript facts differ from ephemeral WebRTC signalling.
const utteranceType = "room/utterance-transcribed";
```

The server limits audio size and duration and drops common speech-model noise phrases. A mention of the mind’s name can wake the room agent; a short follow-on window lets one request span two utterances. A small debounce gathers words before the model starts. `worker.ts` forwards addressed room events to the fixed room agent and mirrors its plain-text answers back as `room/agent-said`, where the page shows them. `room.md` is the standing behavior guide. Transcripts can also enter the member-only [search](/introducing/search) pipeline; they are not blog content.

## The difficult part is permission to act

The microphone belongs to the signed-in member, but a transcription can still be wrong. The agent must require a clear request, tolerate transcription errors, and remain silent during people thinking aloud. Member authentication protects the room; speech instructions do not turn third-party words into trusted orders. Keep presence and signalling ephemeral while making intentional transcript facts durable. Repeated delivery of an utterance or answer must not duplicate the agent request.

## Dependencies and tests

A similar room needs an iterate mind, the existing agent runtime and model funding, browser microphone permission, WebRTC connectivity and speech-to-text access through the mind’s AI service. It can incur transcription and agent usage charges. No phone number or new telephony account is needed just to run the browser room. Wire the host and event handlers together, not only the HTML. Test two members, permission refusal, silent audio, oversized uploads, split utterances, reconnects and repeated events. Keep transcripts and speaker identities private. [Agents](/introducing/agents) explains the durable conversation side; [the blog](/introducing/blog) publishes only the reusable design, never what people actually said.
