-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(weave): Add gpt-4.5-preview and deepseek to playground #3830
Conversation
WalkthroughThis pull request expands model configuration support by updating multiple files. It adds new token limit entries and provider details for GPT-4.5 and DeepSeek models in a TypeScript configuration file, augments a JSON configuration with several new model provider entries (including for Azure AI, Anthropic, and Bedrock), and updates a Python mapping for DeepSeek to include its API key. Additionally, one existing provider entry is modified to reflect a new mapping requirement. Changes
Possibly related PRs
Suggested reviewers
Poem
✨ Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
@@ -107,6 +107,15 @@ export const LLM_MAX_TOKENS = { | |||
max_tokens: 100000, | |||
supports_function_calling: true, | |||
}, | |||
'gpt-4.5-preview': { | |||
litellm_provider: 'openai', | |||
api_key_name: 'OPENAI_API_KEY', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why does this need an api key name but the others dont?
"anthropic.claude-3-5-sonnet-20240620-v1:0": { | ||
"litellm_provider": "bedrock", | ||
"api_key_name": "BEDROCK_API_KEY" | ||
}, | ||
"anthropic.claude-3-7-sonnet-20250219-v1:0": { | ||
"litellm_provider": "bedrock", | ||
"litellm_provider": "bedrock_converse", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
huh, why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
new format?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm this was auto exported but let me just double check
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i thought i made a merge error, but I guess thats what its suppposed to be, shouldnt matter since we dont expose 3-7 under bedrock in the frontend yet
Description
Testing
How was this PR tested?
Summary by CodeRabbit