Desktop (Code tab): Max effort warning strip can't be turned off, and dismissing it doesn't last

Status Closed — duplicate
Maintainer reply None cached
Activity 2 comments · opened Oct 9, 2026 · closed Oct 12, 2026

What happens

On the Code tab, with effort set to Max, a yellow strip sits above the message box:

Claude thinks longer with Max effort and can consume 3.5× or more usage than Medium.

I chose Max on purpose, so after the first showing it is noise. Clicking the X hides it, but it comes back:

  • after every app restart
  • after I open a session on a different model or effort level and then return to a Max session

I move between Max, xhigh and high sessions all day, so I dismiss the same strip many times a day.

What I expected

Dismissing it once should hold across sessions and restarts, at least per model and effort level. Better still, a setting to turn it off.

Steps

  1. Open a Code session and set effort to Max. The strip appears.
  2. Click the X. It goes away.
  3. Open another session set to xhigh (or change this session's effort), then go back to the Max session.
  4. The strip is back. The same happens after restarting the app.

Likely cause (from the shipped UI bundle)

The dismissal for max-effort-warning-band looks to be held in an in-memory store keyed on surface, model and effort, with no saved copy. Entries for other keys are cleared whenever a composer with a different model or effort mounts.

Ask

Either of:

  • save the dismissal, per account or per device
  • add a "don't show again" option or a setting, as the model-switch cache warning already has

Environment

  • Claude Desktop 2.31226.0, Windows 11 (Store package)
  • Max plan, Opus 5.5

Related

#100278 reports the same strip coming back. This issue adds the likely cause and asks for a setting.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗