Skip to content

fix(cursor-review): move the default Moonshot cell back to kimi-k3-max - #393

Merged
mattmillerai merged 3 commits into
mainfrom
matt/default-panel-kimi-max
Oct 9, 2026
Merged

mattmillerai merged 3 commits into
mainfrom
matt/default-panel-kimi-max

Conversation

@mattmillerai

@mattmillerai mattmillerai commented Oct 9, 2026 •

Copy link
Copy Markdown
Member

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 don't run slow, they die

~25 seconds in, RetriableError: [resource_exhausted] after three internal reconnects, zero findings, leg red, Panel integrity red with it.

measured 56 panels, one consumer
kimi-k3-high cells red 24 of 76 (32%)
of those, this error 19
on the last day 12 of 22

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 (30s, then 90s).

-max, not removal — the lane earns its place

The 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:

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 roughly three times what dropping Gemini did, so the fix is the tier, not the lane.

What this costs, stated plainly

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 -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 — 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 remaining kimi-k3-high example outside the era-pinned tests moved to -max — the CURSOR_PANEL_MODELS copy-paste examples in docs/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.

.github/cursor-review/tests     1257 OK
.github/workflow-pins/tests      551 OK  + check_workflow_pins.py OK
check_agents_md.py --root .     passed

The historical-era fixtures and test_catalog_drift.py's REAL_PANEL pin their own eras by design (per #243) and are deliberately untouched.

Provenance

  • Verified:
    • .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: pass
    • PR CI at head 2dadf0e: pending at handoff; no merge-queue run yet
  • Deviations: none — the diff matches the description (default Moonshot cell kimi-k3-high → kimi-k3-max, workflow comment, README rationale, and the stale -high doc/prompt examples)

🤖 Generated with Claude Code

`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>
@coderabbitai

coderabbitai Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

  • Run on-demand review

This review includes 4 billable files and costs up to $1.00.

  • Ask an admin to make reviews automatic

Open in CodeRabbit

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.

Check out review usage here.

View limit details

Limit 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.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Team
  • Run ID: bad9c204-6fec-458b-b3b6-e51582e79b8a

📥 Commits

Reviewing files that changed from the base of the PR and between 281033e and 2dadf0e.


📒 Files selected for processing (4)
  • .github/cursor-review/README.md
  • .github/cursor-review/prompt-judge.md
  • .github/workflows/cursor-review.yml
  • docs/callers/cursor-review.md


  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@mattmillerai mattmillerai added the cursor-review Multi-model cursor review label Oct 9, 2026
…plit

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 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)

Comment thread .github/workflows/cursor-review.yml Resolved
Comment thread .github/workflows/cursor-review.yml Resolved
Comment thread .github/cursor-review/README.md Resolved
…-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>
@mattmillerai
mattmillerai merged commit ad02463 into main Oct 9, 2026
8 checks passed
@mattmillerai
mattmillerai deleted the matt/default-panel-kimi-max branch October 9, 2026 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cursor-review Multi-model cursor review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants