fix(models): restore Kimi K3 1M context#4481
Conversation
Seed the Moonshot kimi-k3 offering in both bundled metadata catalogs so offline and runtime resolution carry its 1,048,576-token context and 131,072-token output limit instead of falling back to 128K. Keep the tier-dependent Kimi Code k3 identity separate from the direct API route. Signed-off-by: Hunter B <hmbown@gmail.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Claude finished @Hmbown's task in 2m 12s —— View job Reviewing PR #4481
SummaryClean, well-scoped fix. Tests are appropriately placed at each layer: catalog hydration ( Minor observations (non-blocking)
No correctness bugs, no provider-prefix inference issues, and no missing test coverage found. Nice, focused fix. |
Summary
kimi-k3model to both bundled offline catalogsk3identity and OAuth compatibility path separateThis closes the current mismatch where live model discovery can display K3 at 1M context, but the runtime resolver falls back to the unknown-model 128K floor.
Official model reference: https://platform.kimi.ai/docs/guide/kimi-k3-quickstart
Verification
cargo fmt --all --checkgit diff --checkcargo test -p codewhale-config(386 passed)Only the known macOS
__eh_framelinker warning appeared.Checklist