Skip to content
Vulpine
Esc
↑↓navigate↵open⌘Jpreview
On this page

What you can say

What you can say to fox9 by voice: start with the callsign "Fox Nine", "niner over" closes a request at once, the verbs the gateway settles itself (cancel, start over, say again, reading controls, the mic, lights on and off, dictation), and everything else goes to the brain (home devices, room speakers, timers, coding agents).

Living doc, checked against the code 2026-11-14

Start with the callsign “Fox Nine”; say “niner over” to close a request at once. Every spoken line takes one of three paths:

  • the gateway settles it itself: a gateway verb, with no brain turn and a fixed spoken answer;
  • it opens or answers something already in flight;
  • it goes to the brain as an ordinary request.

This page lists the first two exactly as the code matches them. Everything else is the brain’s.

The callsign

Start a request with “Fox Nine”. The matcher (find_alias in crates/voice_gateway/src/invocation.rs) accepts, case-insensitively, the forms the speech recognizer writes:

accepted notes
fox nine, fox 9, fox ine, fox n ine, Fox, nine two words, one comma allowed between them
fox9, foxnine one token
box nine, box 9, box9, boxnine the recognizer’s common mishearing
fox line, box line, socks line, foxline the old name, still accepted
Fox and I only at the very start of the utterance; anywhere else it is prose

fox90, boxnines and afox9 do not match. When a room speaker (the Voice PE puck) or the phone detects “Fox Nine” on the device, the gateway treats it as the same callsign (DEVICE_WAKE_MATCHED).

What follows the callsign is the request. Say it in one breath or with pauses: the gateway holds it open until you go quiet. Three things end it early:

  • “niner over” closes the request at once; words after it are dropped.
  • “over” on its own at the end closes it too. The request commits, without the word, as soon as you go quiet (about 0.4 s instead of the 1.1 s settle), and anything after it is dropped. “Is the game over”, “it’s over”, “start over” and “hand the remote over” are requests, not closers; say “…, over” with a pause to close one of those. [invocation] bare_over_closer = false turns it off.
  • “fox” at the end closes it the same way (“turn the lights down a little, fox”). It needs two words before it. It does not fire on “hey fox”, on the callsign said twice or on a sentence about a fox (“the quick brown fox”). [invocation] bare_fox_closer = false turns “fox” off and leaves “over”.

You can also say the callsign last: “turn the lights down a little, fox nine” commits the words before it. It needs two words before it; “hey, fox nine” or the callsign alone only opens a request. [invocation] trailing_alias_commits = false turns it off.

A request longer than 240 characters after the wake is treated as TV or a second person (MAX_ARMED_REQUEST_CHARS). Saying the callsign again inside an open request does not restart it; say “start over”. With [invocation] mode = "cancel_assistant", saying the callsign while Fox Nine talks cuts the reply off (barge-in).

After a wake the recognizer hears the whole request, its pauses and the silence after it: that silence ends the request. Leave [invocation] enrolled_pcm_gate off (the default). It passes only frames whose last 300 ms sound like the wake clip, so every armed hold waits out its 4 s grace and the request reaches the brain late and partial.

Follow-ups without the callsign

After a reply to your request finishes playing, the next thing you say is taken without the callsign for a short window ([invocation] follow_up_window_ms; the default and laptop loadouts set 5 s). After a reply that ends with a question (“Which room?”) the window is 8 s (QUESTION_FOLLOW_UP_WINDOW in turn.rs). Announcements and reports open no window.

Inside the window:

  • a one- or two-word backchannel (“mm-hmm”, “okay”, “no”, “thanks”, “got it”) is ignored and leaves the window open;
  • a cancel phrase (“never mind”, “forget it”) closes the window with nothing sent;
  • a short answer to a question counts as a request even though it is short: “yes”, “yeah”, “no”, “okay”, “sure”, “confirm”, “do it”, “go ahead”, “yes please”, “no thanks”.

With the decision model on (it is optional and off by default), a follow-up it reads as not meant for Vulpine is dropped instead of going to the brain ([decision_gate]). A request that starts with the callsign is never dropped this way.

On a room speaker the bridge asks the device to reopen its mic after a reply (--follow-up question|always|off, default question); see the satellite README.

Gateway verbs

These are closed grammars in crates/voice_gateway/src/turn/phrases.rs (tier_one_verb and the per-verb *_phrase matchers) and two helper modules. Unless noted, the whole utterance after the callsign must be the phrase: “cancel that last reminder” is a request, not a cancel.

Politeness is forgiven. The gateway retries a miss with fillers and one polite lead removed (“please”, “just”, “can you”, “could you”, “go ahead and”, “I want you to”), so “could you please say that again” still routes (verb_tier::relaxed_form, on by default via verb_tier_route_relaxed). The retry also drops a recognizer’s false start, a single letter that only begins the next word (“could you s please say that again”); “a” and “i” stay.

what it does say always on?
Hang up — end the radio session; the brain starts a fresh session, the connection stays up “over and out” yes
Status report — speaks “Gateway online. Listening.” “sitrep”, “sit rep” yes
Acknowledge — closes the request, nothing sent “roger”, “copy” yes
Cancel — closes the request, nothing sent “cancel”, “cancel that”, “never mind”, “scratch that”, “stand down”, “forget it” yes
Start over — restart the brain conversation in place; a running brain turn is aborted at once, its answer never spoken “start over”, “start again”, “start fresh”, “restart” yes
Say again — repeat the last reply “say that again”, “repeat that”, “come again”, “what was that”, “pardon”, “one more time” yes
What did you hear — read back what the gateway committed “what did you hear”, “what did I just say”, “read back what you heard” yes
Recalibrate the mic “recalibrate the mic” (also “mike”, “microphone”) yes
Thinking level — how hard the brain thinks from now on “think harder”, “think less”, “think hard”, “thinking off”, “normal thinking”, “low thinking”, “minimal thinking” yes
Quota — Claude / Codex usage from the fleet snapshot “how much Codex do I have left”, “what’s my Claude quota”, “Claude and Codex usage” yes
Brain model — say the model and the others the loadout allows; switch after a read-back and a yes; “switch back” returns to the model before (the Admin’s Live sessions row shows the pin) “which models can you use”, “what model are you on”, “switch the brain to the latest luna”, “switch to the grok model”, “switch back” yes
Show a page — put a web page from the gateway’s page list on the panel: Vigil and the Glyph show it in a sandboxed frame, a panel that cannot show web pages says so; nothing is spoken when a panel took it (page.v1) “retro weather”, “show retro weather”, “show me the retro weather”, “open retrocast”, “pull up retro weather on the screen” only for a page in [panels.pages] (retro weather is the default)
Orb style — put the orb in another style of the orb-styles registry; it changes at once and is remembered; says “Orb set to Phosphor.” (a screen without the orb: “No orb here can change its style.”) “change the orb to phosphor”, “orb style dither”, “switch to the storm orb”, “use the signal orb”, “set the orb style to cloud” (the styles: iris, signal, orbital, dither, storm, cloud, phosphor, inkblot; classic, bricks, plasma, water, voxel, radar, led wall, meadow, galaxy and thermal are Labs styles, worn only when the Labs switch in Vulpine.app’s Glyph look was on at its hello; otherwise it says “Voxel is a Labs orb style. Turn Labs on in the Glyph to wear it.”) yes; only a frontend that wears orb styles (the Glyph look)
Not for you — label the last thing Vulpine acted on as a false wake; a reply still playing is cut; the answer is a chip on the screen, not speech “I wasn’t talking to you”, “that wasn’t for you”, “not you”, “wrong one” yes; [training] false_fire = false gives the words back to the brain
That was for you — label the last line Vulpine dropped as meant for it; the answer is a chip on the screen “I was talking to you”, “that was for you”, “you missed that” yes; [training] missed_address = false gives the words back to the brain
Agent report — from the coding-agent hook files “what did Claude say”, “read Claude’s message”, “how many subagents are done” yes
Lights on/off — the gateway runs the home adapter and says what changed; “back on” brings back only what it turned off “turn off the office lights”, “turn the kitchen lamp on”, “all the downstairs lights off”, “turn the office lights back on” only with [home_bridge] set up
Undo — put back the last home change “undo that”, “put them back”, “turn them back on” only within 10 min of a home change
Dictation — type your words on the screen “type this: see you at five”, “write this down, buy milk”, “take dictation: …” only with [screen] enabled
Scratch that — erase what the last dictation typed; it says when you edited the text since and leaves it “scratch that”, “scratch this”, “delete that”, “delete this”, “undo that” only for 2 min after a dictation lands; otherwise “scratch that” is the cancel
Review choices — answer an open dictation review “send it”, “say it plain”, “scratch it” (and “scratch that”, “delete that”) only while a review is open
Keep that — write the last 15 minutes of room lines to the timeline “keep that”, “remember this”, “save what we just said”, “keep the last few minutes” only with [retrieval] timeline_path set (retrieval)
Forget a call / stop recording — forget a stored call, or opt this call out “forget this call”, “forget the meeting”, “stop recording”, “stop transcribing”, “don’t transcribe this call” only while the meeting inlet runs ([meet] enabled)
Forget an approval — take back a standing approval by name “forget the systemctl approval”, “revoke the grant for web 01”, “stop trusting cargo”, “forget that approval” always; a subject-less “stop trusting” goes to the brain unless the subject matches
Read a feed item — read aloud the Nth item of the feed list the brain just read out, with the read controls below; marked read when the read reaches its end “read me the second one”, “the first one”, “second one”, “read the third”, “number three”, “read me the last one” (first to tenth, 1st to 10th, “number one” to “number ten”) only for 90 s after the brain lists unread feed items (pi_feeds unread); otherwise the words are the brain’s. With no fresh list: “I haven’t read you a list yet.” Past the end: “That list had 5 items.”
Read controls — steer an article being read aloud see below only while a read is open

The fine print, from the grammars:

  • Lights — the verb must be “turn … on/off”, and the subject must end in light(s), lamp(s) or bulb(s), in at most five words. “Turn on some music”, “turn off the speakers”, “dim the lights” and every other device go to the brain (its pi_home_act tool handles brightness, scenes, outlets and room players). A plural names a group: “the office lights” is every light in the office. “All the downstairs lights” is every light in the rooms the home map’s zones block puts downstairs (homectl init proposes zones from Home Assistant’s floors). “All the lights” with no room or zone is the whole house and goes to the brain.
  • Back on — “turn the office lights back on” (or “turn back on …”) turns on only the lights Vulpine’s own verbs turned off there in the last 12 hours. A lamp switched off by hand stays off (“office lights back on: the two I turned off.”). With nothing remembered there it is a plain “on”. The memory is owner-only, in the gateway’s state folder (home-restore.json), and survives a roll. The Admin’s Home panel shows it as the “Back on” row.
  • Undo — “undo that” with nothing recent in the house to undo goes to the brain unchanged.
  • Dictation — a bare “dictation” or “dictate” needs a pause (a colon or comma in the transcript) before the words. “Type this up later”, “write this week’s plan” and “write a poem” are requests, not dictation. The words are tidied, never rewritten: fillers (“um”, “uh”), a doubled word (“the the”) and a spoken correction (“meet Tuesday — scratch that, Wednesday at three” types “Meet Wednesday at 3.”) go, and a sentence gets a capital and a full stop. A tidy that would add, change or reorder a word is dropped, and your words are typed as spoken. “Type this literally …” skips the tidy; [screen] dictation_cleanup = false turns it off.
  • Quota — the CLI must be named (Claude, Claude Code, Codex, or both); “how much code is left in this file” is the brain’s. A few subjectless forms (“what’s my quota”) also match.
  • Show a page — the whole request must be one of the page’s aliases (or its name said as words), with at most a lead (“show”, “show me”, “open”, “pull up”, “bring up”, “put up”, “display”), a “the”, a tail (“page”, “on the screen”, “on the panel”, “for me”) and a “please”. “Show me the weather like the 90s” goes to the brain, whose pi_show_page tool puts up the same page by name. Close it with the panel’s ×.
  • Thinking — at most five words; “I think so” and “what do you think” are ordinary requests.
  • Scratch that, outcomes — the screen agent erases the typed range only if the field still reads as the words Vulpine typed. If you edited the text, even by one letter, Vulpine leaves it and says “That text has changed; I left it.”
  • Scratch, keep, review, meeting — closed sets matched on the whole utterance (“please” dropped): “remember that my sister lands at six” and “stop recording the screen” go to the brain. While a home change is recent, “undo that” undoes it first.

Reading an article aloud

A read opens from the frontend (vulpine-glyphctl read <url>, the protocol’s StartRead) or by “read Claude’s message”. No spoken phrase opens a URL. While a read is open, these controls work bare, without naming the article (reading_phrase):

control say
pause “pause”, “hold it”, “pause reading”
resume “resume”, “continue”, “keep going”, “carry on”, “go on”
next “next”, “skip”, “skip this”, “skip ahead”, “move on”
previous “back”, “go back”, “previous”, “again”, “read that again”
from the top “from the top”, “start the article over”, “restart the reading”
stop “stop reading”, “stop the article”, “that’s enough”, “enough of that”
where are we “where are we”, “where was I”, “how much is left”

Bare “stop” and bare “start over” are not read controls: “start over” restarts the conversation. Name the article instead (“stop reading”, “start the article over”).

The page is fetched before the read opens; the spoken controls work once it has landed. While the fetch is pending, the frontend’s stop (vulpine-glyphctl read stop, the protocol’s reading_control stop) cancels it and the gateway says “Stopped.” A newer read cancels the pending one.

The fetch guard refuses a private or local address, a redirect to one, too many redirects, and a user name or password in the link. The answer is read_fetch_failed, said in words (“That page points at a private address, so I did not fetch it.”).

“Did you mean …?”

With [turn] verb_confirm_band set (off by default), the gateway asks back when a line is close to a verb but not a match. “Yes” runs the verb, “no” sends your original words to the brain, and anything else carries on as normal.

Saying no to a guess

With [brain] ask_back_budget = true (off by default), a brain never asks the same thing twice in a row: the gateway picks the first option and says it with “say no if that is wrong”. Saying “no” (also “nope”, “that’s wrong”, “no, the hall light”) right after that line vetoes the subject. Until your next request, the brain’s questions on it are always spoken, never guessed.

Start over, mid-turn

“Start over” while the brain answers (or while a held turn waits) aborts the turn, never speaks its answer and restarts the brain at once. If a tool call is running, the restart waits for its result, bounded by the turn’s deadline, then aborts. A tool that asks you something ends the wait.

Lines that wait for you

A wake holds every spoken notice. From the wake until your request settles, an announcement, a finished agent’s report or an approval card waits. It speaks at the next quiet point after the reply. A finished agent’s report card is spoken only on the session that owns the agent; a room puck waits a few seconds so your own device speaks first.

The puck’s controls

The Voice PE puck’s button, dial and mute switch can drive the gateway’s turn machine instead of the bridge. This is off by default: set VULPINE_SATELLITE_CONTROLS=gateway (or --controls gateway) in the puck’s env file. The default, local, keeps the bridge’s own mapping. With it on:

control what it does
single press while the puck listens closes the request (“over”)
single press while a reply plays, or a request is with the brain cancels the reply
double press start over (the spoken verb’s path)
long press, or the mute switch toggles the mute; a muted puck rests in idle in presence, so the Admin presence strip shows it
dial the room’s volume, 3 points a click up to a ceiling of 60, applied once the dial stops; every room-speaker readout to that room plays at it

The wire shape is the satellite-controls contract. The puck’s own “Stop” word is not a control; the bridge keeps it as its own cancel.

Said twice

The gateway watches for a line that arrives twice: the same words (or the same words plus one) within 2.5 seconds, or the same verb within 1.5 seconds ([turn] commit_guards). It only notes these in the trace (commit_guard rows); both lines still run. “Again”, “once more”, “one more time”, the reading controls, dictation and a bare yes or no are never counted.

Everything else goes to the brain

Anything the grammars above do not match is an ordinary request to the voice brain, which answers with tools. The brain tool reference has the full, generated list. In the default loadout a spoken request can reach:

  • home and rooms — lights, scenes, outlets, room players (pi_home_act); say something in a room (pi_room_speak); “I’m in the kitchen” (pi_presence); who is where (pi_who_is_there, pi_where_is); a radio station by name on one room player (“play Groove Salad in the kitchen”, below);
  • time — alarms and timers on the room speakers (brain_alarm_*), puck timers (pi_satellite_timer), today’s calendar (pi_calendar_today);
  • weather — the weather and forecast at home or in a named city, and “any weather warnings?”: the National Weather Service’s active alerts for the home point, at most five, newest first, said as event and end time with no links (pi_utility weather, weather_alerts; US only, keyless, needs VULPINE_WEATHER_LAT/LON);
  • this Mac — music, volume, output device, apps, reminders (pi_mac_control); an Apple Shortcut by name (“run Lamp Off”, below); rewrite the selected text (pi_write_selection); questions about your screen or selection. The gateway adds an on-device OCR of the screen only when you name it (“what’s on my screen”, “what’s this error”), and reads the selection only when you say “selected”, “selection” or “highlighted” (screen_phrase, selection_phrase);
  • coding agents — herdr panes, dispatch, reports, stand-ups, prompts (brain_herdr_*, pi_herdr_*);
  • work and memory — capture a work note, background work, todos, past agent sessions (moraine_*), these docs (fox9docs_*), GitHub, code and file search, web search;
  • the system itself — gateway health, frontend status and reconnect, fleet digest, system status.

A radio station. The home adapter’s play_station verb finds the most clicked working station in the public Radio Browser directory, never a URL you say. It refuses no_station or station_unreachable. pi_home_act offers it as play_station with query, the station’s words in at most 64 characters: “play jazz radio in the kitchen” is subject “kitchen speaker”, query “jazz”. The gateway’s mutation route passes query to homectl as --query.

A Shortcut. It runs only when its name is a line in ~/.config/vulpine/shortcuts-allow.txt. Any other name, or no file, is refused shortcut_not_allowed. The shortcut’s text output comes back as untrusted data (shortcut_run, shortcut_list).

When the brain’s provider retries a turn, or compacts an overflowing conversation and retries, the gateway holds the turn open and says nothing; the retried answer is the turn’s one reply. A hold longer than [brain] retry_hold_ms (20 s by default) closes the turn, restarts the brain and speaks the usual provider line.

The gateway, never the brain, answers “forget that approval”. With no subject, it asks back when more than one shape holds a grant or learned trust, naming each (“trusted cargo” for a trust-only shape; that answer resets only the trust). A model switch closes the open question with both grants kept. Its lines are said at once.

A spoken “yes” or “no” also answers a question the brain asks mid-turn (pi_ask_operator) and a home action that needs your confirmation.

Not supported, and pitfalls

  • No synonyms beyond the tables. A near-miss like “halt” or “shut up” is not a cancel; it goes to the brain. The decision model (decision_shadow.rs) runs no verb: a verb is matched only by the grammars above. Besides the follow-up drop, its answers are only traced.
  • Bare “stop” is not a gateway verb. On the puck, “Stop” (the device’s own stop word) or a button press cancels a reply; elsewhere, barge in with the callsign.
  • Mic on/off and mute are not gateway verbs; only “recalibrate the mic” is.
  • One request per breath. A second callsign inside an open request is ignored.

The rules behind the radio words are ADR 0015.

Was this page helpful?