00adf69d92
Voice input was record-then-upload on every surface: nothing showed while the user talked, and the transcript arrived only after the whole take uploaded. With `stt.streaming: true` the openai, xai and elevenlabs providers now stream microphone PCM to their realtime endpoints while the user speaks. Partial text renders live and the final transcript is ready at end of speech. - tools/transcription_streaming.py: one session API (push_audio / end_audio / finalize / cancel, an on_partial callback, a worker thread that owns the socket) with three wires, all verified live: the OpenAI Realtime `type: transcription` session (gpt-live-transcribe, 16->24 kHz resample since the endpoint refuses < 24 kHz), xAI wss /v1/stt with interim results, and ElevenLabs Scribe v2 realtime. Plugin providers opt in through TranscriptionProvider.streaming_capable / open_stream_session. - tools/voice_mode.py: AudioRecorder taps its capture callback into the session and parks it under the WAV path. transcribe_recording uses the live transcript and falls back to the file on any failure or empty result, so CLI push-to-talk, the continuous VAD loop and the TUI gateway gain streaming with no call-site changes. - Classic CLI and Ink TUI show partial text in the input placeholder while recording (new `voice.partial` gateway event, contract regenerated). Desktop dictation streams PCM to the new /api/audio/transcribe-stream socket (provider keys stay on the host, and the host resamples) and shows partial text in the dictation pill. The recorded blob stays the fallback. The plugin streaming contract (streaming_capable / open_stream_session / TranscriptionStreamSession) and the transcribe-stream socket shape come from #103173. Co-authored-by: Vinicius <timelord1025@gmail.com>
Website
This website is built using Docusaurus, a modern static website generator.
Reading the docs on GitHub? The Markdown under
docs/is authored for the rendered site at https://hermes-agent.nousresearch.com/docs/. Cross-page links are relative Markdown paths, so they follow through on GitHub's file viewer too. Every page on the site has an Edit this page link that opens the source file here.
Authoring links in docs/
- Link to another page with a relative Markdown path, anchors included:
[Profiles](../user-guide/profiles.md),[Bundles](../user-guide/features/skills.md#skill-bundles). Docusaurus turns the file path into the page route; GitHub follows the same path. Site routes (/user-guide/profiles,/docs/user-guide/profiles) only work on the rendered site — GitHub resolves them as repository paths and 404s, and the/docs/form also emits/docs/zh-Hans/docs/...404s in the zh-Hans build becausebaseUrlis already/docs/. python3 website/scripts/check_doc_links.pyfails on any route-style link in hand-authored pages (EN and the zh-Hans mirror);--fixrewrites them. It runs in theDocs Site Checksworkflow. Generated pages (user-guide/skills/{bundled,optional},reference/*skills-catalog.md) are produced byscripts/generate-skill-docs.py, which emits the same relative form.- Pin
{#anchor}on cross-linked headings so the zh-Hans mirror keeps the same id.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.