Add provider field and provider-aware request headersFeat/anthropic support#35
Open
OmprakashSahani wants to merge 2 commits into
Open
Add provider field and provider-aware request headersFeat/anthropic support#35OmprakashSahani wants to merge 2 commits into
OmprakashSahani wants to merge 2 commits into
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
1 participant
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
This PR adds groundwork for provider-specific model configuration and request handling.
Changes:
providerfield toModelConfigprovider: openaiLLMClientMotivation
ShellAI currently assumes OpenAI-compatible request behavior in the LLM client. Adding an explicit provider field makes the model configuration more extensible and prepares the codebase for future provider-specific integrations such as Anthropic.
Notes
This PR does not fully implement Anthropic payload or streaming response parsing yet. It only introduces the configuration and request-header groundwork needed for provider-specific support.