Forumics logo Forumics
Issue 01

Back to issue

All Claude Code known issues

CLAIM C076 Supported 2026-11-09

GitHub issue #89690 in anthropics/claude-code, opened 2026-08-26 by urda, records a report that a modelPicker row with model opusplan never reaches the /model picker in append mode because Claude Code treats the row as covered by the built-in lineup, while the built-in lineup carries no Opus Plan Mode row in an ordinary session, and that replace mode renders the opusplan row, which the author states proves the row parses, validates, and is servable. The author retested the report on later builds through 2.1.319 and reported the same result in append mode. No maintainer response appears in the thread.

Verbatim Excerpts from Cited Records
“A `modelPicker` row whose `model` is `opusplan` never reaches the `/model` picker in append mode. Claude Code treats the row as covered by the built-in lineup. The built-in lineup carries no Opus Plan Mode row in an ordinary session, so nothing covers it.”
— urda · anthropics/claude-code (issue 89690 opening body, Summary section) · 2026-08-26T02:34:36Z ·GitHub Issue ↗
“`opusplan` is a mode, not a model. `--model opusplan` runs Opus during plan mode and Sonnet during execution. `--model opus` runs Opus throughout. The coverage check compares resolved models, so it treats the two as the same row.”
— urda · anthropics/claude-code (issue 89690 opening body, Summary section) · 2026-08-26T02:34:36Z ·GitHub Issue ↗
“The picker shows the built-in lineup and nothing else. Five rows, no Opus Plan Mode row, and no message.”
— urda · anthropics/claude-code (issue 89690 opening body, Actual section) · 2026-08-26T02:34:36Z ·GitHub Issue ↗
“Replace mode renders the `opusplan` row, which proves the row parses, validates, and is servable. Only the coverage check rejects it”
— urda · anthropics/claude-code (issue 89690 opening body, Evidence section) · 2026-08-26T02:34:36Z ·GitHub Issue ↗
Counter-record: Issue open; API returned 18 comments, all 18 read. All comments are by the author urda, reporting retests on builds 2.1.250 through 2.1.319, each with the same result in append mode. On 2026-09-01 the author posted a correction in a comment, stating the collision partner is the Sonnet row, not the Opus row as the opening body says, after reading the picker code in the 2.1.257 bundle; the opening body still carries the original wording. No maintainer response appears in the thread. No retraction of the report appears in the thread. The claim documents only the original report and the author's follow-up retests, not a verified current state. Falsification probe: If issue 89690 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.