Specialists

Talking to it

A live voice conversation with the agent, for when typing is the slow part.

Code
/voice                 start a voice conversation
/voice text            switch back to typing mid-conversation
/voice status          what's connected
/voice leave           leave, keep it running
/voice end             end it

What it's for

Thinking out loud. Describing a bug is often faster spoken than typed, and "walk me through how this module works" is a better question asked than typed.

The conversation is a normal session — same project memory, same permissions, same captured decisions. Voice is an input method, not a different product.

In a meeting

Code
/voice join <id>       join an existing meeting
/voice say <text>      speak a line without using the microphone
/voice mute
/voice list            meetings you can join

Useful when the agent should hear a design discussion and capture the decisions as they're made, rather than being told about them afterwards.

What gets kept

The same things as any session: decisions, lessons, and the transcript. Ask "what did we decide in that call" later and the answer is there.

If it doesn't work

It can't hear you. Check the input device your terminal has access to. /voice status reports what it's connected to.

It mishears technical terms. Type them — /voice text switches to the keyboard without ending the conversation, and /voice say <text> inserts a line exactly.

It's too slow for quick exchanges. Voice suits explanation and discussion. For "run the tests", typing wins.

Next