docs: Hermes Agent integration guide - #887
Conversation
New overview page covering both integration surfaces: the MCP hookup (hermes mcp install voicebox — catalog entry submitted upstream) for agent-invoked speak/transcribe/captures tools, and the hermes-voicebox provider plugin (github.com/jamiepine/hermes-voicebox) that routes Hermes's entire voice pipeline — spoken replies, Telegram voice bubbles, and incoming voice-message transcription — through local Voicebox.
📝 WalkthroughWalkthroughAdds a Hermes Agent documentation page covering Voicebox MCP tools, the ChangesHermes Agent documentation
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/content/docs/overview/hermes-agent.mdx (1)
1-140: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winUpdate the Hermes docs links Lines 70-72 point to
https://hermes-agent.nousresearch.com/docs/developer-guide/..., which return 404. The#per-client-bindingsanchor is fine; the GitHub repo links are also reachable. Point those docs links at the current Hermes docs paths.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/content/docs/overview/hermes-agent.mdx` around lines 1 - 140, Update the TTS providers and transcription providers links in the provider plugin section to use the current valid Hermes documentation paths instead of the obsolete developer-guide URLs. Leave the per-client-bindings anchor and GitHub repository links unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@docs/content/docs/overview/hermes-agent.mdx`:
- Around line 1-140: Update the TTS providers and transcription providers links
in the provider plugin section to use the current valid Hermes documentation
paths instead of the obsolete developer-guide URLs. Leave the
per-client-bindings anchor and GitHub repository links unchanged.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: b7745a87-3fce-42cc-a18e-fbc0bcb5fff6
📒 Files selected for processing (2)
docs/content/docs/overview/hermes-agent.mdxdocs/content/docs/overview/meta.json
Adds a new Overview docs page showing how to wire Voicebox into Hermes Agent in both directions:
hermes mcp install voicebox(catalog entry submitted upstream) or a manualmcp_servers.voiceboxblock, giving the agentvoicebox.speak/voicebox.transcribe/voicebox.list_profiles/voicebox.list_capturesas tools it can choose to call.Includes behavior notes (app-must-be-running, first-generation model load, Whisper 202 download) and Docker port differences. Page added to the Overview sidebar after MCP Server.
bun run buildpasses with the new page compiled.Companion PR:
optional-mcps/voiceboxcatalog entry submitted to hermes-agent (NousResearch/hermes-agent#63498). The provider plugin itself ships standalone: hermes-voicebox (PyPI).Summary by CodeRabbit