[BUG] Warning me every 2 minutes "Claude thinks longer with Max error and can consume 3.5 or more usage than medium."

Same problem here in the Claude desktop app on Windows (Code tab), app version 2.26454.2.0, Windows 11.

The banner above the input box — "Claude thinks longer with Max effort and can consume 3.5× or more usage than Medium." — comes back in every single session, even though I dismiss it with the X each time. I use Max effort on purpose and open many sessions a day, so I end up closing the exact same warning over and over.

Choosing Max effort is a deliberate decision. Being re-warned about it in every session, as if I hadn't made that choice knowingly, is patronizing and just adds noise.

What I'd expect instead:

• Show the warning once, when Max is first selected, and remember the dismissal across sessions (or offer a "Don't show again" option / a setting to turn it off).
• If some reminder is really needed, a small passive indicator next to the effort selector is fine. A full-width disclaimer banner that has to be closed manually every time is not.

Side note for triage: this is labeled area:tui, but it happens in the desktop app, so area:desktop probably fits better.

One more detail that may explain the "every 2 minutes" in the original report: the dismissal doesn't even survive within the same session.

Repro in the desktop app (Windows, 2.26454.2.0):

1. Open a session with effort set to Max. The banner appears.
2. Dismiss it with the X.
3. Switch to another session (or otherwise leave this one), then come back.
4. The banner is back, in the same session where it was dismissed a moment earlier.

There is no cooldown at all: it reappears on every single re-entry. If you jump in and out of a session, you get the banner again each time, seconds apart.

So the dismissed state seems to be lost whenever the session view is re-opened, not just when a new session starts. Anyone who moves between sessions sees it constantly.

Same here on Claude Desktop 2.31226.0 (Windows 11, Code tab, Opus 5.5 at Max).

I filed #100676 with the likely cause, read from the shipped UI bundle: the dismissal for max-effort-warning-band looks to be held in memory only, keyed on surface, model and effort, and it is cleared whenever a composer on a different model or effort mounts. That would explain why it returns after switching sessions and after every restart.

The ask there: save the dismissal, or add a "don't show again" option or a setting.

Thank you for building Max effort; I use it on purpose for most of my work. Same issue on macOS (27.0.1, Claude Desktop 2.31226.0, Code tab), so it isn't Windows-only.

Two things from the shipped UI bundle that may help whoever picks this up:

1. There already seems to be a server-side switch for it. On the code surface the band's visibility goes through a GrowthBook gate (__gb__235191659): the band renders only while that gate is off. So the plumbing to hide it exists; wiring it to a user setting, or a "don't show again" that persists, looks like a small change.
2. There is no user-side workaround. The band is drawn by the desktop app's own React (data-testid="max-effort-warning-band"), not by Claude Code, so a Claude Code plugin/mod can't hide it either: none of the ui.render components (AbovePrompt, PromptHint, InfoNotice, …) cover it. I looked into that route before landing here.

The ask, same as #100676: persist the dismissal (per account or device), or add a setting to turn it off.