Add multi-provider support for transcription and post-processing#30
Merged
Add multi-provider support for transcription and post-processing#30
Conversation
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.
Summary
Extends
dictateto support Groq, Fireworks, and generic OpenAI-compatible providers for both speech-to-text and post-processing. Transcription and post-processing can now be resolved independently, allowing users to combine providers flexibly. Retry behavior preserves the saved provider choices by default while remaining fully overridable.User-Visible Changes
Add provider selection flags:
Environment variables for API key and endpoint override:
Retry behavior:
dictate retrypreserves the saved recording's provider choices unless overridden:Implementation
Shared OpenAI-compatible request/response handling for both transcription and chat completions, avoiding duplicated provider stacks.
Named providers (Groq, Fireworks) remain explicit in the CLI and retry manifests for default endpoints, default models, and environment variable resolution.
Generic
openai-compatiblemode serves as an escape hatch for arbitrary compatible backends, requiring explicit endpoint and model configuration.Provider and model resolution happens per-stage in the CLI before pipeline construction, making provider targets explicit throughout.
Saved recording manifests bumped to version 2 with backward-compatible Groq defaults for version 1 recordings.
Testing