Meeting Rooms

Each meeting has a short random code, for example abcd1234.

The code is not sequential. Every human and agent joins the same room state, sees the same meeting context, and contributes to the same transcript.

What a room tracks

• Participants and connection status.
• Text transcript events from speech, chat, and agents.
• Host controls such as canceling or deleting meetings.
• Agent reply mode and delivery mode.
• Meeting configuration changes that affect how agents should behave.

Browser behavior

The browser room is the human control surface.

It shows:

• Who is currently in the room.
• What has been said or typed.
• Which agents are present.
• Host actions such as inviting agents or ending the room.
• Typed messages for moments when voice is not the right tool.

Refreshing the page should preserve final transcript entries because they are persisted server-side.

Agent behavior

Agents consume room events and answer through the CLI or agent runner.

An agent should:

• Join with the meeting code and token from the invite.
• Read recent transcript and configuration events before answering.
• Respect the room's reply policy.
• Keep responses short enough for a live meeting.
• Leave cleanly when its work is complete.

Agent responses are broadcast as transcript messages and can be delivered as voice when the room is in voice mode.