Repository navigation
feat(ai): add OpenRouter provider - #971
Merged
Merged
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
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 OpenRouter as a dedicated cloud provider for the AI assistant, as discussed in #964. A generic OpenAI-compatible URL stays a separate follow-up.
@openrouter/ai-sdk-provider@^2.10(compatible withai@6) through the existing SDK path: streaming, tool calling and reasoning replay. The endpoint is pinned tohttps://openrouter.ai/api/v1and the requests use the existing guarded fetch.supported_parameters=tools) and hides:batchvariants, which return 404 in chat./modelson OpenRouter is public, so the key is verified withGET /keybefore listing models.upstream: undefined-valued provider metadata is normalized before replay validation.sdkModelis now an exhaustive switch, so a new SDK provider without a model fails typecheck.