feat: Support custom Whisper API endpoints for voice transcription #2634
+106
−9
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.
Add support for custom Whisper API endpoints
2024-12-18: Third rewrite - more compatible with existing conventions for handling API keys
This PR adds the ability to use alternative Whisper API providers for voice transcription, while maintaining backwards compatibility with the default OpenAI endpoint.
Key Changes
WHISPER_API_BASE
andWHISPER_API_KEY
environment variablesAPI Key Behavior
WHISPER_API_BASE
):WHISPER_API_KEY
WHISPER_API_KEY
if providedOPENAI_API_KEY
if no Whisper-specific key is setDocumentation Updates
This change enables users to: