Hermes, Voice, and Intelligence
Hermes is the main local conversational and operator-workflow surface in AI OS. Its agent page and Intelligence portal share Hermes-owned readiness while keeping chat, Mission Control, documents, Pantheon, Ministry, memory, voice, and recovery behavior explicit.
Hermes agent page
Section titled “Hermes agent page”- Chat supports model selection, approximate context, session continuity, stop, latest-wins queueing, compact carryover, commands, and safe Markdown.
- Mission Control supports local mission creation, preview and commit, imported missions, active goals, archive reactivation, and briefing copy.
- Documents, profiles, sessions, memory, skills, Pantheon, and connections render from their owned local contracts.
- Pantheon includes the Ministry builder and model-attributed mixture-of-agents save flow when local write readiness passes.
gpt-5.6-sol is the bundled demo and reviewed baseline, not a globally forced
default. Local Hermes configuration is authoritative, and the UI preserves its
validated configuredDefault. Claude Fable 5 is an additive frontier and
Ministry option; its catalog presence does not change that local default or
prove account entitlement.
Ask Hermes and session control
Section titled “Ask Hermes and session control”Typed requests use the Hermes local execution path. Accepted turns preserve their model and effort choices, stream structured output, and expose stop, timeout, and error recovery. Session continuity is resolved from confirmed local state rather than a UI-only assumption.
Reasoning effort is a Hermes chat control. Do not confuse it with the separate script-only OpenAI subscription runtime, whose current Codex transport does not forward a reasoning field.
Voice uses a local broker owned by the AI OS Session 08 implementation. The UI can launch it through the reviewed local path when the provider requirement is available. Sample playback and live provider success remain environment-specific proof; a control being visible does not prove either occurred.
The browser does not collect provider keys. Broker configuration stays local, and the UI receives bounded ready, starting, offline, token, provider, and recovery states.
Intelligence ownership
Section titled “Intelligence ownership”The portal and its routing are owned by the Session 09 implementation. Current docs describe the shipped local controls and recovery behavior only. AI OS does not claim a hosted voice service or a public Intelligence API.
Floating Oracle can hand one voice intent to this portal, but Intelligence still owns microphone, broker, provider, and session recovery. See Floating Oracle and the separate OpenAI subscription runtime.