You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d220150
Browse filesBrowse the repository at this point in the historyBrowse files
fix(cursor): keep max as the kimi-k3 catalog default
PR #646 seeds cursor/kimi-k3 with a low/high/max effort ladder, which is the
right tier data — Cursor serves K3 only as effort-suffixed wire ids and Kimi
documents max as the model's API default. But the Cursor registry entry supplied
no modelDefaultReasoningEfforts, and that ladder has no medium rung, so
applyReasoningLevels fell through medium -> high and settled the catalog default
on high. The picker then sends high explicitly and the request builder's
no-effort fallback to kimi-k3-max is never reached.
The other K3 routes (kimi, kimi-code, opencode-go) already carry this default,
so cursor was also the odd one out.
Verified in both directions: on the PR commit alone the assembled catalog row
reports default_reasoning_level = high; with this line it reports max; removing
the line again fails the new test with Received: "high". The existing
effort-suffix tests pass either way, which is why the defect slipped through —
they assert the ladder, not the assembled default.
Scope check: modelRecordValue matches exact key, colon-family, then case-fold,
so { "kimi-k3": "max" } cannot reach kimi-k3-max, kimi-k3-low, or any other
cursor model. Confirmed across 8 model ids; only kimi-k3 is affected.
Gates: tsc clean; codex-catalog 113 pass; cursor-effort-suffix + cursor-discovery
18 pass; provider-registry-parity + reasoning-effort 70 pass.
Docs ship in the same commit because the prose asserts the ladder and default.
0 commit comments