Best possible solution:

Derive one effective channel model/provider state before /status computes auth, runtime, usage, context, and display labels, then show both effective and session/default models when they differ.

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

Yes, at source level. Configure a channels.modelByChannel override that differs from the selected/default model: current /status suppresses the differing override while the reply path applies it before execution.

Is this the best way to solve the issue?

No, not as currently patched. The direction is useful, but applying the override inside buildStatusMessage is too late when buildStatusText has already derived auth, runtime, usage, and harness metadata.

Full review comments:

• [P2] Resolve the override before deriving status metadata — src/status/status-message.ts:1001-1002
  This branch renders channelModelRef.label with activeAuthLabel, but the command path can still pass auth/runtime/usage values computed from the selected/default model before the channel override is applied. A channel override such as xai/grok-4.3 can therefore be shown with OpenAI auth/runtime/usage metadata; resolve the effective channel model before computing those fields or recompute all metadata from the override.
  Confidence: 0.86

Overall correctness: patch is incorrect
Overall confidence: 0.86

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 54b09580f61b.

Label justifications:

• P2: This is a normal-priority operator-facing status correctness bug with limited blast radius because reply routing itself is not shown to be broken.
• merge-risk: 🚨 auth-provider: The diff can display a channel override model while auth, runtime, or usage metadata remains derived from a different selected/default provider path.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🧂 unranked krab.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The PR body lists tests only and needs redacted after-fix /status proof from a real Telegram or real-channel setup; screenshots, recordings, terminal/live output, or logs count if private IDs, tokens, phone numbers, IPs, endpoints, and account details are removed, and updating the PR body should trigger a fresh ClawSweeper review or a maintainer can comment @clawsweeper re-review. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
• mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram /status output for a Telegram channel override, which is suitable for a short Telegram Desktop proof recording.

PR surface:

Source +10, Tests +31. Total +41 across 2 files.

What I checked:

• Repository policy read and applied: Root AGENTS.md was read fully, and the Telegram maintainer note was read because the PR affects visible Telegram /status behavior and proof expectations. (AGENTS.md:1, 54b09580f61b)
• Current main still suppresses differing channel overrides: resolveChannelModelNote resolves the channel override, but returns no note when the override provider/model differs from the selected/default provider/model passed to the formatter. (src/status/status-message.ts:542, 54b09580f61b)
• Status auth is derived before the formatter sees channel overrides: buildStatusText computes selected/active auth labels, harness, usage provider, and context before delegating to buildStatusMessage, so formatter-only override handling can leave metadata on the selected/default path. (src/status/status-text.ts:350, 54b09580f61b)
• Normal reply path applies the channel override: Reply execution resolves channels.modelByChannel, parses the override model, and uses the resolved override as the primary provider/model before running the reply. (src/auto-reply/reply/get-reply.ts:576, 54b09580f61b)
• PR head renders the override with precomputed auth: The PR head renders channelModelRef.label with activeAuthLabel, but the command path can pass activeModelAuth from the selected/default model when the runtime active model did not differ before the formatter override. (src/status/status-message.ts:1001, 70bab535e932)
• PR body lacks real behavior proof: The PR body lists only the targeted Vitest command and no redacted after-fix /status output, terminal/live output, logs, recording, screenshot, or linked runtime artifact. (70bab535e932)

Likely related people:

• thewilloftheshadow: GitHub commit metadata and git show identify this account as author of the original thread-aware channels.modelByChannel resolver, reply-path wiring, and initial status tests. (role: introduced existing feature surface; confidence: high; commits: f555835b0974; files: src/channels/model-overrides.ts, src/auto-reply/reply/get-reply.ts, src/auto-reply/status.test.ts)
• dutifulbob: Commit metadata for the shared session status runtime extraction points to this account as author of the status command layer now deriving auth and runtime metadata before the formatter. (role: status runtime contributor; confidence: medium; commits: 380de88a61de; files: src/status/status-text.ts)
• osolmaz: The shared status runtime extraction credits this account as reviewer/co-author, and the broader open resolver tracker is authored by this account. (role: reviewer and canonical resolver requester; confidence: medium; commits: 380de88a61de; files: src/status/status-text.ts, src/status/status-message.ts)
• xydigit-zt: Merged PR history shows this account authored the direct-user-id channels.modelByChannel resolver update that currently touches the same resolver and status call site. (role: recent adjacent area contributor; confidence: medium; commits: 9bf681d663e9; files: src/channels/model-overrides.ts, src/status/status-message.ts, docs/gateway/config-channels.md)
• LiLan0125: Current blame for the status, reply, and resolver lines points to a broad recent carry-forward commit by this account, so they are relevant for current-main context even if not the original feature author. (role: recent area contributor; confidence: low; commits: 685b95b607bb; files: src/status/status-message.ts, src/status/status-text.ts, src/auto-reply/reply/get-reply.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.

• reviewed 2026-06-22T02:46:44.508Z sha 70bab53 :: needs real behavior proof before merge. :: [P2] Resolve channel auth before rendering the override model