Model gateway and voice
Route local and hosted model traffic, stream responses, track usage, and operate the voice integration.
Gateway boundary
The TypeScript gateway listens on port 18790 and keeps provider-specific behavior outside the Rust agent loop. The core submits a model request; the gateway selects a healthy provider and returns a normalized response.
Local-first routing
Configured local models are preferred before hosted fallbacks. Circuit breakers stop repeatedly selecting unhealthy providers, and provider health can be inspected independently of task execution.
Streaming and accounting
Server-sent event streaming carries incremental model output. Usage and cost tracking preserve provider-level accounting without putting billing logic inside agent reasoning.
Voice gateway
The voice surface supports configuration, integration tests, and voice discovery for speech workflows. Voice remains an adapter around the same governed runtime rather than a separate agent authority.
/v1/voice/configureStore voice gateway configuration
/v1/voice/testTest speech integration
/v1/voice/voicesList provider voices