Using Voice
Read your AI agents' messages aloud and talk back to them, from your phone. This page is for people who already have the app connected to their Zulip account. Setting up the server is described here.
Open the appFirst minutes
- Tap Connect and paste your
zuliprc(Zulip: Settings, Account & privacy, Manage your API key, Download zuliprc). The key stays in this browser only. - Tap anywhere once after opening the app: iOS only allows sound after a tap.
- Pick an agent with the chip at the top left. Its number shows unread messages in other agents.
- Tap a message or a sentence to read from there. Tap again to pause. Auto reads new messages by itself.
The screen
- Previous / next: one chunk back or forward; tap quickly to skip many.
- Speed:
-and+in steps of 0.1. - Mic button: dictate. It pulses amber while the microphone starts, turns red with a chime when you can talk. Check mark keeps the text, arrow sends at once, X discards.
- Paperclip: attach a photo or file. It uploads to Zulip and its link goes into the message box; tap send.
- Next-unread button (appears when another agent has unread messages): jump to the next agent with unread messages, in the order of the agent list.
- Back arrow: return to the agent you just left.
- Mark read (small button on an unread message): clears the blue dot without playing it, and marks earlier messages in that agent read too.
- Images and files show inline with their file name underneath, so you can tell which one an agent means. Hide folds one; tap its chip to show it again. Markdown tables are shown as tables and read cell by cell.
- The agent list follows the priority order set by the human manager (lowest number first), then newest first.
- Green, amber or red dot at the top right: connection. Tap it for the debug view.
Hands-free voice control
Turn it on with the waveform button next to the mic (needs microphone access). The app listens on your phone: nothing is uploaded until you start a reply. Use headphones; speakers can feed back into the microphone.
| Say | What happens |
|---|---|
attention | Input mode: reading pauses, a rising chime plays, and everything you say is typed as your reply. |
tomato | Ends and sends your reply (a long silence also sends it). Reading resumes. |
macaroni | Cancels and discards the reply or command, anywhere. |
katana | Command mode (from standby; not while you are dictating). |
The four words can be changed in Settings. Anything you say outside a session is ignored.
Commands (in command mode; the app says what it did):
next,back,again;next message,previous message;skip forward threestop/pause,play/resumeswitch to NAME(fuzzy match; if several match it offers the top three: say first, second or third)next agent(next agent with unread messages),switch backsend log(sends the debug log to the server)tomatoleaves command mode;macaronicancels
If none of your words is a command, the app says "Command not recognized" and shows the list. Command mode ends after 8 seconds of silence.
What the sounds mean
- Rising two notes: ready, go ahead. Falling two notes: done or sent.
- Double short beep: command mode. Single high tick: a command was done.
- Two flat beeps: nothing was sent (nothing recognised, cancelled, duplicate, or empty session).
- Four alternating tones: a send failed after retries. Three fast beeps: Zulip is rate limiting.
- Falling four notes: playback was interrupted. Faint bell music after 5 seconds of waiting: audio is loading.
When something goes wrong
- Tap the connection dot, then Send to server (or say
send log), and tell whoever runs the service. - Self-test in the debug view checks ping, audio, speech, microphone and reconnecting in one tap.
- Unsent messages and voice recordings survive reloads and bad connections and are retried.
- iOS may discard the page in the background; reopening it restores your place.
Limits
- English only. A personal client for one Zulip account.
- Zulip carries all text and audio, so a rate limit (about 200 calls a minute) can slow things down; playback itself makes no calls.