[BUG] Usage item missing from Settings sidebar in Claude Desktop (Windows), page still reachable via search

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

The "Usage" entry is no longer shown in the Settings sidebar of Claude Desktop on Windows. It is not under Billing or any other section. The Usage page itself still works and can be opened by typing "usage" into the Settings search box, so the page exists but the sidebar entry is not being rendered.

Current Settings sidebar shows: General, Account, Privacy, Billing, Capabilities, Memory, Design systems, Claude Code, Claude in Chrome (then Desktop app / Customize / Platform sections). No Usage.

The entry was present and in regular use earlier on the same day (Sep 24, 2026). Settings > Usage is the page I use most often, so losing direct access is a real regression.

What Should Happen?

"Usage" should appear in the Settings sidebar as before, giving one-click access to the session and weekly limit meters and the Resets section.

Steps to Reproduce

1. Open Claude Desktop on Windows.
2. Open Settings.
3. Look at the left sidebar: no "Usage" entry.
4. Check Billing: Usage is not there either.
5. Type "usage" into the Settings search box: the Usage page opens normally.

Error Messages/Logs

Steps to Reproduce

1. Open Claude Desktop on Windows.
2. Open Settings.
3. Look at the left sidebar: no "Usage" entry.
4. Check Billing: Usage is not there either.
5. Type "usage" into the Settings search box: the Usage page opens normally.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.7032.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Possibly related: #95987 (Code tab missing from Claude Desktop on Windows since around Sep 21, 2026). That is a different UI entry, but it is on the same platform in the same week, so it may be the same rollout or feature-flag issue.