feat: Add support for custom provider endpoints and headers #245
+301
−36
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.
This commit introduces several enhancements for configuration flexibility and usability.
Users can now specify a custom
baseURL
andheaders
for API providers (e.g., OpenAI, Gemini, Groq). This enables routing requests through proxies, corporate gateways, or connecting to self-hosted, API-compatible services.Additionally, two new command-line flags have been added:
--config
: Allows specifying a path to a custom JSON configuration file, overriding the default search behavior.--prompt-file
: Enables loading a prompt from a markdown file, making it easier to run complex, multi-line prompts in non-interactive mode.The README has been updated to document these new features.