feat(web): make context window indicator opt-in

[maria-rcks]

The circular context window indicator is now a legacy feature that defaults off for existing and new client settings. Users can restore it from Settings → General → Legacy features, and settings search plus restore-default behavior include the new toggle. Verified with contracts and web typechecks, focused settings and meter tests, targeted lint, and a direct schema decode check. Built by gpt-5.6-sol in T3 Code through the Codex harness.

---

Note

Low Risk
Client-local UI preference with a default-off legacy toggle; no auth, data, or server behavior changes beyond settings persistence.

Overview
The composer’s circular context window usage indicator is hidden by default. A new client setting, contextWindowMeterEnabled (default false), gates whether ChatComposer passes context-window data to the footer primary actions.

Users who want the old behavior can turn it on under Settings → General → Legacy features (“Context window indicator”). Settings search, restore-defaults tracking, and patch/schema decoding in contracts cover the new flag; tests assert default-off and explicit opt-in.

^{Reviewed by Cursor Bugbot for commit 5523463. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add opt-in contextWindowMeterEnabled setting to ClientSettings

• Adds the boolean contextWindowMeterEnabled field to ClientSettingsSchema and ClientSettingsPatch, defaulting to false when absent so the context window meter is off by default.
• Forwards activeContextWindow to ComposerFooterPrimaryActions only when the setting is true; otherwise passes null so the meter is hidden.
• Exposes a legacy "Context window indicator" switch in General settings under LegacyFeaturesSection, with searchable terms registered in settingsSearch.ts.
• Updates useSettingsRestore to detect and reset contextWindowMeterEnabled, and adjusts the desktop test fixture to set it explicitly false.
• Behavioral Change: existing clients with no contextWindowMeterEnabled value now decode as false; verify any out-of-tree consumers of ClientSettings expecting the meter to show by default.

^{Macroscope summarized 5523463.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR changes the persisted default behavior of the web composer by hiding the existing context-window indicator unless users opt in through a legacy settings control. The implementation is otherwise contained and additive, but the default change warrants review of the intended product experience.

Notes:

• No code objects were reviewed. Approvability was decided on eligibility alone.

^{You can add or adjust custom eligibility rules. Learn more.}

[jwilmsnallian]

@maria-rcks Could you share why this is marked as legacy? I found it very useful

[bman654]

came to ask the same question. I'm worried if there isn't a replacement planned. Managing context is key part of getting good model results.

[maxredundancy]

I'd also be super interested in why this was disabled by default and hidden in legacy?

[ElliotDrel]

Adding another strong vote against classifying this as legacy. I love the context-window indicator and rely on it during long-running work.

Context pressure and compaction materially affect how I manage a thread; hiding that signal makes it harder to decide when to checkpoint, start a new thread, or change course before context quality degrades.

I understand making it optional for people who prefer a cleaner composer, but I would really like this kept as a normal, supported feature—not an opt-in “legacy” feature that signals it may be removed. Ideally it should live in the regular General settings, with a clear long-term commitment or a documented replacement.