[BUG] Dispatch (beta) shows "Desktop appears offline" on all surfaces - including the Desktop app itself - fresh Win11 install 1.26832.0, local bridge healthy, zero inbound

Environment

• Windows 11 Pro (build 26200), Claude Desktop 1.26832.0 (MSIX), fresh install 2026-08-11, Authenticode-verified installer from downloads.claude.ai
• Max plan; latest Claude app on both iOS and Android
• Desktop signed in, running (11 processes), 9 established TLS connections to Anthropic edge (160.79.104.10:443)

Symptom

Dispatch permanently shows "Desktop appears offline. Will run when it reconnects." on:

1. the iOS app,
2. the Android app, and
3. the Dispatch pane of the Desktop app itself, on the very machine that is online - the desktop reports itself offline while signed in with a live session.

Regular Cowork tasks work normally. Only Dispatch presence is broken.

Local diagnostics (all healthy - the failure is not client-side)

From %LOCALAPPDATA%\Packages\Claude_*\LocalCache\Roaming\Claude:

• logs/main.log: [sessions-api] Registered environment: env_01YM8F... -> success; [buddy] starting bridge / bridge started; [claude-in-chrome] WebSocket connected; zero errors related to dispatch/auth/network
• bridge-state.json: enabled: true, userConsented: true, live remoteSessionId: cse_01HCZ..., processedMessageUuids static at 7 - no inbound message ever arrives no matter how many dispatches are sent from either phone
• ant-device-registry.json: 1 enrolled pk1: credential, written at app start
• GrowthBook chicago_config: enabled=true (computer use on)
• claude.ai account Settings shows Trusted devices: "No trusted devices" despite active desktop + mobile sessions (question below)

Already tried (mirrors the closed duplicates - none of it works)

Sign-out/in on all devices, fresh install, phones on same account, VPN on and off, Cowork session active during dispatch. The community in the issues below additionally tried deleting bridge-state.json, reinstalling mobile apps, and virtualization checks - also without effect.

Relationship to existing issues

Same shape as #63179 (Win11, never worked on first use), #54378 (Win, verified-healthy bridge), #68481, #45962, #45937 - all closed as duplicates of #49545, which went stale and was closed "not planned" with no staff response and no fix (open since April 2026). Filing fresh because: (a) the canonical is closed while the bug still reproduces on a brand-new install four months later, and (b) the desktop-reports-itself-offline datum plus a fully receipted healthy local bridge narrows this to the server-side presence/relay layer.

Questions for the team

1. Must a machine appear under account Trusted devices for the Dispatch relay to mark it online? If so, the Desktop app never offers enrollment - that would be the actual bug.
2. Can someone check the relay records for environment env_01YM8F... (full ID available privately / via in-app report)?

An in-app report with full logs was also submitted from the affected machine.