[BUG] Browser pane entirely absent on macOS Intel desktop 1.24012.9 — no Views menu entry, Cmd+Shift+B no-op, despite docs requiring only v1.2581.0

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report
• [x] I am using the latest version of Claude Code

What's Wrong?

The Browser pane is entirely absent from the desktop app: there is no Browser entry in the Views menu inside an open Code session, and Cmd+Shift+B is a no-op. The desktop docs document both, requiring only Claude Desktop v1.2581.0+.

Environment:

• Claude Desktop 1.24012.9 (03c61d) 2026-07-24 — "Check for Updates" reports it is the latest
• Intel Mac, macOS 15.6 (Darwin 24.6.0); docs state the macOS build is universal for Intel and Apple Silicon
• Individual account (not under MDM / managed settings, so disableBrowserExternalNavigation / browserExternalPageTools policies do not apply)
• Browser-related toggles in Settings → Claude Code are enabled

What I ruled out:

• Version: 1.24012.9 is well past the documented 1.2581.0 requirement (other issues show the monotonic scheme: 1.2773.0 in #48827, 1.5354.0 (2026-04-29) in #56125; Browser-pane bug reports exist from desktop 1.24012.1, e.g. #80483, so the feature ships in this version line)
• Context: checked the Views menu inside an open Code session, not the home screen or Chat tab
• Settings: browser toggles in Settings → Claude Code are on

Steps to Reproduce

1. Open Claude Desktop 1.24012.9 on an Intel Mac
2. Open a Code session (local project)
3. Open the Views menu in the session toolbar → no Browser entry
4. Press Cmd+Shift+B → nothing happens

Expected

Browser pane available per the desktop docs (Views menu entry + Cmd+Shift+B), given the version requirement is met and the feature is enabled in settings.

Notes

This looks like the same class as #77071 (Dispatch tab missing), #56125 (Code tab missing; clean reinstall didn't help — concluded entitlement/rollout), and #43976 (computer-use MCP not appearing): a server-side feature gate or staged rollout leaving a fully-updated client without the feature and no UI/docs indication of why. If the Browser pane is cohort-gated, it would help to surface that state in the app (e.g. a disabled menu item with a tooltip) and in the docs.