[BUG] Intercom support messenger does not load on claude.ai — "Get help" is unreachable for paid users; ticket history inaccessible

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?

What's Wrong?

The Intercom support messenger that powers "Get help" does not load on claude.ai at all. Per Anthropic's own documentation ("How to get support", updated June 1 2026), the support messenger is the ONLY route to the Product Support team for Pro and Max subscribers — there is no published support email and no phone or live chat. When the messenger fails to load, a paying customer has no working support channel inside the product.

Verified directly in-browser on a logged-in Max account:

On claude.ai:

window.Intercom            -> undefined
window.intercomSettings    -> undefined
support-widget scripts     -> NONE loaded
Intercom DOM nodes         -> 0

On support.claude.com, the identical checks return a working messenger (typeof window.Intercom === "function", container present, messenger renders).

So the Intercom SDK is simply not being served to claude.ai. This is not latency and not a network issue — nothing is loaded.

Second, related symptom: on support.claude.com, where the messenger DOES load, the Messages panel shows "No messages — messages from the team will be shown here", despite multiple open conversations on the account. Ticket history is therefore unreachable from both surfaces.

Practical consequence: I have three open support conversations and could not retrieve two of their IDs. I only have the first because I screenshotted it at the time.

What Should Happen?

What Should Happen?

"Get help" in claude.ai should load the Intercom messenger, and existing conversation history should be visible to the authenticated user on both claude.ai and support.claude.com.

Error Messages/Logs

### Error Messages/Logs

No error is surfaced in the UI. The widget is simply absent — no failed request is shown to the user, no fallback message, no indication that support is unavailable. The user experiences it as "nothing happens".

Steps to Reproduce

Steps to Reproduce

1. Log in to claude.ai on a paid (Pro/Max) account
2. Open DevTools console
3. Evaluate typeof window.Intercom — returns "undefined"
4. Evaluate document.querySelectorAll('[id*=intercom],[class*=intercom]').length — returns 0
5. Attempt "Get help" from the account menu — messenger does not open
6. For contrast, load support.claude.com and repeat step 3 — returns "function"

Platform

claude.ai web + Claude Desktop (Cowork)

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Not exposed anywhere in the application. There is no About pane, and no version string appears under Settings > General or Settings > Desktop app > General (both panes checked in full). Build in use on 28 July 2026; app was reinstalled on 23 July 2026 on the advice of the in-app assistant.

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Why this matters beyond the immediate inconvenience:

There is an existing chain of unresolved reports about Cowork project containers disappearing after an update or reinstall — #49276 (closed as duplicate), #35131, and #29373 (marked stale, closed without a fix). All three describe project data surviving on disk while the app stops reading it.

If the primary support channel silently fails for exactly the users hitting those bugs, then affected customers cannot report them through the documented route. That is a plausible contributing factor to reports like #29373 going stale, and it means the true incidence of the project-loss bug may be materially under-counted.

I am filing this publicly because I could not reach support through the product to report that support is unreachable.