Interface · internal system
Voice Interface
Always-on spoken status, routed to whichever machine is actually in earshot.
Live
No public endpoint
Voice
The problem it solves
Reading is a full-attention activity. If the only way to know what an autonomous system is doing is to look at a screen, it can only work while you are watching it — which defeats the point of it being autonomous.
How it works
01
Summarise
each turn produces a short spoken headline
→
02
Cap
hard-limited to a couple of sentences
→
03
Synthesise
local speech engine by default
→
04
Route
played on whichever machine is nearby
→
05
Interrupt
one command stops it mid-sentence
Under the hood
- The spoken block is a status headline, never a narration of the written answer — the screen already has the detail.
- Deterministically truncated, so a long answer never becomes a long monologue.
- A local speech engine is the default; a premium cloud voice is opt-in rather than the standard path.
- Speech is suppressed entirely when nobody could hear it, so tokens are not spent on an empty room.
Why it matters
Hands-free status is what lets the system keep working while its owner is doing something else — which is the whole design goal.