Uh oh!
There was an error while loading. Please reload this page.
feat: add Kimi K3 coding plan support - #1164
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Add Kimi K3 as the first Kimi Coding Plan model while preserving the existing
kimi-for-codingfallback.Publish K3's 1,048,576-token context window, 131,072-token output limit, vision/tool/reasoning capabilities, and sole
maxeffort. Send K3 through the existing Anthropic-compatible adapter with its required adaptive thinking mode and maximum effort on every turn.Verification
npm --workspace @maka/core test(1,069 passed)npm --workspace @maka/runtime test(2,068 passed, 7 skipped)npm --workspace @maka/core run typechecknpm --workspace @maka/runtime run typechecknpx biome linton all changed files/coding/v1/messages,x-api-key,thinking.type=adaptive, andoutput_config.effort=maxLive Kimi API validation is intentionally deferred to the benchmark dry run after the product and harness PRs merge.