Best possible solution:

Land the narrow status-copy, docs, and test correction after exact-head checks and automerge gates pass.

Do we have a high-confidence way to reproduce the issue?

Yes, from source inspection. Current main and v2026.6.6 emit the old /reset hint, while /model default clears persisted model overrides and /reset intentionally preserves user-selected overrides.

Is this the best way to solve the issue?

Yes. Updating the status copy, docs, and focused expectations is the narrowest maintainable fix because the clearing behavior already exists; changing /reset would be a broader reset-contract change.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 0314819f918a.

Label justifications:

• P3: This is a small user-facing status/docs correction with limited blast radius and no config, migration, provider, protocol, or dependency change.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 🚀 automerge armed: This PR is in ClawSweeper's automerge lane. Not applicable: The contributor proof gate does not apply to this MEMBER-authored, maintainer-labeled PR; the PR body and live checks provide focused test evidence for the changed status paths.

PR surface:

Source 0, Tests 0, Docs +4. Total +4 across 7 files.

What I checked:

• PR diff updates both status emitters: The PR head changes both rich status and CLI status section clear hints from /model <configured> or /reset to /model default, with matching expectations in the adjacent status tests. (src/status/status-message.ts:999, 1181624daa70)
• Current main still has the old hint: Current main still emits Clear with: /model ${configuredDefaultModelLabel} or /reset, so the central PR change is not already implemented on main. (src/status/status-message.ts:999, 0314819f918a)
• /model default is an existing reset selection: The directive resolver treats raw default as the configured default provider/model and marks the model selection as isDefault: true. (src/auto-reply/reply/directive-handling.model-selection.ts:72, 0314819f918a)
• Default model selection clears persisted overrides: Applying an isDefault model selection deletes provider/model override fields and modelOverrideSource, which is the behavior the new hint points users to. (src/sessions/model-overrides.ts:42, 0314819f918a)
• /reset preserves user model overrides: Reset preservation intentionally keeps user-driven model overrides, so advertising /reset as the clear path for a user-pinned model is misleading. (src/config/sessions/reset-preserved-selection.ts:18, 0314819f918a)
• Latest release still has the old hint: The latest release tag v2026.6.6 still emits the old /model ${configuredDefaultModelLabel} or /reset rich status hint, so this is an unshipped correction. (src/status/status-message.ts:992, 8c802aa68351)

Likely related people:

• steipete: git shortlog --all shows Peter Steinberger with the heaviest history across the central status/model docs and status helper files, including status helper consolidation and model-selection docs work. (role: area history owner; confidence: high; commits: 72dcf9422138, 756cb22f15a7, c72f539ced72; files: src/commands/status.command-sections.ts, docs/concepts/models.md, docs/cli/status.md)
• kevinslin: git blame attributes the current old status hint and the existing /model default resolver lines to commit e82d19f, merged through feat(codex): add auto plugin approvals #92625. (role: current-line introducer; confidence: high; commits: e82d19fb06b5; files: src/status/status-message.ts, src/commands/status.command-sections.ts, src/auto-reply/reply/directive-handling.model-selection.ts)
• frankekn: The reset-preservation behavior central to this fix was introduced through the merged reset model override work in fix(gateway): clear auto-fallback model override on session reset #63155. (role: reset behavior contributor; confidence: high; commits: 5d46e4dc4f45; files: src/config/sessions/reset-preserved-selection.ts, src/gateway/session-reset-service.ts)
• vincentkoc: Recent history shows Vincent Koc touching adjacent rich status output in the same status-message surface and authoring the latest release commit checked for shipped behavior. (role: recent adjacent contributor; confidence: medium; commits: 5b460c4669d4, 8c802aa68351; files: src/status/status-message.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.