Repository navigation
feat: support non-factory LanguageModelV2 class exports in dynamic provider loader - #16794
Closed
coconutbird wants to merge 3 commits into
Closed
coconutbird wants to merge 3 commits into
coconutbird wants to merge 3 commits into
Conversation
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
1 task done
coconutbird
marked this pull request as ready for review
March 9, 2026 19:39
Contributor
|
Closing this pull request because it has had no updates for more than 60 days. If you plan to continue working on it, feel free to reopen or open a new PR. |
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.
Issue for this PR
Closes #16793
Type of change
What does this PR do?
Adds a fallback in the dynamic provider loader for npm packages that export a
LanguageModelV2class instead of acreate*factory (e.g.@augmentcode/auggie-sdk). The loader triescreate*first, then falls back to duck-typing classes by checking fordoGenerate/doStreamon the prototype. Constructor assumption isnew Class(modelId, options)— same convention risk as the existingcreate*path.How did you verify your code works?
Configured
@augmentcode/auggie-sdkas a custom provider inopencode.jsonand verified all 8 Augment models load and respond correctly viaopencode run -m augment/<model> "say hello".Screenshots / recordings
N/A — no UI changes.
Checklist