fix: update Fire Pass Kimi K2.6 Turbo router - #3309
Merged
amitksingh1490 merged 1 commit intoMay 10, 2026
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
|
|
Sorry, something went wrong.
luan007
marked this pull request as ready for review
May 10, 2026 08:16
amitksingh1490
approved these changes
May 10, 2026
amitksingh1490
approved these changes
May 10, 2026
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.
Fireworks updated Fire Pass to v2, and the current Fire Pass plan only supports one router model:
accounts/fireworks/routers/kimi-k2p6-turbo
This updates Forge's Fireworks provider config from accounts/fireworks/routers/kimi-k2p6 to the new v2 router model.
Docs: https://docs.fireworks.ai/firepass
I also tried configuring this through Forge's custom model/provider flow, but Fire Pass API keys are not authorized for the /v1/models query. Because Forge validates custom provider models through that endpoint, the built-in provider list needs this direct model ID update.