feat(deepseek): wire DeepSeek into dynamic router-model cache#15
Merged
Conversation
Adds DeepSeek to the dynamicProviders tuple and registers a new fetcher that hits https://api.deepseek.com/models, merging the live list with the static deepSeekModels specs. Known model IDs keep their pricing and context-window data; unknown models receive sensible 128K/8K-output defaults so they become selectable in the generic model picker. The webview aggregator pushes a DeepSeek candidate when an API key is present (mirroring the Poe pattern), and useSelectedModel falls back to the static list when the live fetch fails — so existing users keep working on deepseek-chat / deepseek-reasoner without regressions.
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.
Adds DeepSeek to the dynamicProviders tuple and registers a new fetcher that hits https://api.deepseek.com/models, merging the live list with the static deepSeekModels specs. Known model IDs keep their pricing and context-window data; unknown models receive sensible 128K/8K-output defaults so they become selectable in the generic model picker.
The webview aggregator pushes a DeepSeek candidate when an API key is present (mirroring the Poe pattern), and useSelectedModel falls back to the static list when the live fetch fails — so existing users keep working on deepseek-chat / deepseek-reasoner without regressions.
PR - re-implemented after:
Zoo-Code-Org/Zoo-Code#40 by taltas