Repository navigation
fix(cursor-review): move the default Moonshot cell back to kimi-k3-max - #393
Merged
Merged
Conversation
`kimi-k3-high` is capacity-bound, so the built-in panel is currently one lane short on every consumer that has not overridden it — which is most of them. The cells do not run slow, they die: ~25 seconds in, `RetriableError: [resource_exhausted]` after three internal reconnects, zero findings, leg red, `Panel integrity` red with it. Measured on one consumer over 56 panels, 24 of 76 `kimi-k3-high` cells red (32%), 19 of those this error, and 12 of 22 on the last day. Not a property of one repo: the same model threw the same error the same day on two unrelated consumers. And #388's in-step retry does not rescue it, because the condition is sustained rather than transient — both cells on this repo's own panel for #392 exhausted all three attempts. `-max` rather than dropping the lane, because the lane earns its place. The 2026-08-27 attribution that cut Gemini was re-run over 1,158 judge-kept findings (82 PRs), normalised per finding raised so panel size flatters nobody: model raised sole distinct sole/PR c/h sole kimi-k3-max 229 39 17% 1.05 3/58 kimi-k3-high 81 22 27% 1.05 0/11 gemini-3.1-pro 99 12 12% 0.33 0/58 Kimi contributes 1.05 unique findings per PR at BOTH tiers and uniquely caught 3 of 58 critical/high at `-max`. Gemini — cut for exactly this reason — managed 0.33 and 0 of 58. Dropping Kimi would cost about three times what dropping Gemini did, so the fix is the tier, not removal. This deliberately gives back the spend the `-high` notch in #243 was for; it is a partial reversal of that change, not an oversight. And the reliability it buys is NOT established at this tier under present conditions: `-max` was 0 of 36 cells red, but that was 2026-10-07, before the capacity trouble, and the two tiers may share a pool. Recorded in the workflow so the next person does not have to rediscover it, along with what the evidence says to do if `-max` goes the same way: drop to a two-lab Cursor panel rather than substitute Gemini or Grok. Grok `4.7-high` was tried on 2026-10-09 and raised 0 unique findings in 17 while timing out on 11 of 20 cells. Default change, so it reaches every consumer on the next SHA bump; a repo that wants the old tier back sets CURSOR_PANEL_MODELS. README panel table and history updated alongside. Tests: cursor-review 1257, workflow-pins 551 + pin lint, agents-md — all green. The historical-era fixtures and `test_catalog_drift.py`'s REAL_PANEL pin their own eras by design and are deliberately untouched. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
Warning Review limit reached
This review includes 4 billable files and costs up to $1.00.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 35 minutes for your next included review. View limit detailsLimit details: You’ve used the included review currently available. Your 132 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (4)
Comment |
…plit Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
🔍 Cursor Review — Consolidated panel
Triggered by @mattmillerai.
Found 3 finding(s).
| Severity | Count |
|---|---|
| 🟢 Low | 1 |
| ⚪ Nit | 2 |
Panel: 4/6 reviewers contributed findings.
Reviewers that did not contribute: kimi-k3-max:adversarial (error), kimi-k3-max:edge-case (error)
…-max pin The CURSOR_PANEL_MODELS copy-paste examples would otherwise change two axes and silently put a fleet back on the capacity-bound -high tier. Also reword the README's 32% figure to match the source data. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
kimi-k3-highis capacity-bound, so the built-in panel is currently one lane short on every consumer that has not overridden it — which is most of them.The cells don't run slow, they die
~25 seconds in,
RetriableError: [resource_exhausted]after three internal reconnects, zero findings, leg red,Panel integrityred with it.kimi-k3-highcells redNot a property of one repo — the same model threw the same error the same day on two unrelated consumers. And #388's in-step retry does not rescue it, because the condition is sustained rather than transient: both cells on this repo's own panel for #392 exhausted all three attempts (30s, then 90s).
-max, not removal — the lane earns its placeThe 2026-08-27 attribution that cut Gemini was re-run over 1,158 judge-kept findings (82 PRs), parsed from the judge's own
_Raised by N of M reviewers (...)_lines and normalised per finding raised, so panel size flatters nobody:kimi-k3-maxkimi-k3-highgemini-3.1-proKimi contributes 1.05 unique findings per PR at both tiers and uniquely caught 3 of 58 critical/high at
-max. Gemini — cut for exactly this reason — managed 0.33 and 0 of 58. Dropping Kimi would cost roughly three times what dropping Gemini did, so the fix is the tier, not the lane.What this costs, stated plainly
-highnotch in ci(cursor-review): cut panel spend — 3-lab panel, xhigh judge, cell time cap, bot-bump skip #243 was for. This is a deliberate partial reversal of that change, not an oversight.-maxwas 0 of 36 cells red, but that was measured 2026-10-07, before the capacity trouble, and the two tiers may share a pool.Both are recorded in the workflow and the README so the next person doesn't rediscover them — along with what the evidence says to do if
-maxgoes the same way: drop to a two-lab Cursor panel rather than substitute Gemini or Grok. Grok4.7-highwas tried on 2026-10-09 and raised 0 unique findings in 17 while timing out on 11 of 20 cells — worse than Gemini on value and worse than Kimi on reliability.Scope
Default change, so it reaches every consumer on the next SHA bump. A repo that wants the old tier back sets
CURSOR_PANEL_MODELS. README panel table and history updated alongside, and every remainingkimi-k3-highexample outside the era-pinned tests moved to-max— theCURSOR_PANEL_MODELScopy-paste examples indocs/callers/cursor-review.md(so they again differ from the built-in list by exactly one axis), the judge prompt's attribution example, and the leg-context-name examples.The historical-era fixtures and
test_catalog_drift.py'sREAL_PANELpin their own eras by design (per #243) and are deliberately untouched.Provenance
.github/cursor-review/tests: 1257 OK;.github/workflow-pins/tests: OK (43 skipped)check_workflow_pins.py,check_agents_md.py --root .,check-org-repo-literals.sh: passkimi-k3-high→kimi-k3-max, workflow comment, README rationale, and the stale-highdoc/prompt examples)🤖 Generated with Claude Code