Operations

Runs like infrastructure, not a script.

A settings UI, full request tracing, browser log tailing, and a Windows tray app — the operational surface an always-on router needs.

Every turn, fully traced

Each stage reports its own status and duration into the turn’s trace. The last 200 are kept in memory at /v1/traces — what the console’s Activity feed reads.

14:02:31 audio dante fallback 612ms
sttfaster-whisperok240ms
agenta2a › danteok310ms
ttselevenlabs → openaifallback62ms

Windows tray app

Polls /health every 5s — green when online, red when not.

Router online — 6 agents
Open test console
Settings & agents
Stop listening
Restart router

Live settings, zero restart

Edit agents in the browser. Saving PUTs the whole config and the router reloads it in place.

- voice_id: bella
+ voice_id: aria
PUT /v1/config → reloaded

Log tailing, no SSH

A rotating file handler (5MB × 3 backups) keeps history; /v1/logs?lines=300 tails it straight into the console.

14:02:31 INFO turn 8f3ac1 kind=audio agent=dante status=fallback duration=612ms
14:02:31 WARN stage tts target=elevenlabs status=error: connection refused
14:02:31 INFO stage tts target=openai status=ok 180ms

Ready to route your own voice stack?