feat(tools): add base_url support to OpenAI TTS provider#2064
Merged
teknium1 merged 1 commit intoNousResearch:mainfrom Mar 19, 2026
Merged
feat(tools): add base_url support to OpenAI TTS provider#2064teknium1 merged 1 commit intoNousResearch:mainfrom
teknium1 merged 1 commit intoNousResearch:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Adds configurability to the OpenAI TTS provider so Hermes can target self-hosted / OpenAI-compatible TTS endpoints via tts.openai.base_url in ~/.hermes/config.yaml, while preserving the existing default behavior.
Changes:
- Read
tts.openai.base_urlfrom config and pass it to the OpenAI client in the OpenAI TTS provider. - Document TTS configuration (including OpenAI
base_url) incli-config.yaml.example.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| tools/tts_tool.py | Plumbs base_url from tts.openai config into the OpenAI client initialization. |
| cli-config.yaml.example | Adds a commented example block showing TTS configuration, including OpenAI base_url. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
Allow users to configure a custom base_url for the OpenAI TTS provider in ~/.hermes/config.yaml under tts.openai.base_url. Defaults to the official OpenAI endpoint. Enables use of self-hosted or OpenAI-compatible TTS services (e.g. http://localhost:8000/v1). Also adds a TTS configuration example block to cli-config.yaml.example.
532cbdc to
116984f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and Why
The OpenAI TTS provider previously had
base_urlhardcoded tohttps://api.openai.com/v1, making it impossible to use self-hosted or OpenAI-compatible TTS services.This PR reads
base_urlfrom~/.hermes/config.yamlundertts.openai.base_url, falling back to the official endpoint when not set. No behavior change for existing users.Usage
Changes
tools/tts_tool.py: readbase_urlfromoai_configin_generate_openai_tts()website/docs/user-guide/features/voice-mode.md: document the newbase_urlfield undertts.openaiHow to Test
tts.provider: openaiandtts.openai.base_url: http://localhost:8000/v1in~/.hermes/config.yamlhermes chat -q "Say hello"with TTS enabled — requests should go to the custom endpointbase_urlset, behavior is identical to beforePlatform
Tested on macOS.