Desktop app crashes irrecoverably (requires Windows "Repair") when Browser pane visits explee.com

Status Closed — duplicate
Maintainer reply None cached
Activity 1 comment · opened Jul 31, 2026 · closed Aug 25, 2026

Title

Desktop app crashes irrecoverably (requires Windows "Repair") when Browser pane visits explee.com

Environment

  • OS: Windows 11 Pro (10.0.26200)
  • App: Claude Code desktop app
  • Trigger surface: the in-app Browser pane (automated browser tool), used to visit a live website mid-conversation

What happens

Every time the Browser pane navigates to explee.com, the desktop app crashes. This isn't a soft error the session recovers from — the app becomes unusable and won't reopen normally afterward. The only fix is going into Windows Settings → Apps → Claude Code → Repair.

This has now happened on multiple separate occasions/sessions, always tied to this same site.

Steps to reproduce

  1. In an active Claude Code session, open the Browser pane.
  2. Navigate to https://explee.com.
  3. App crashes.
  4. Relaunching the app fails / doesn't work normally.
  5. Only resolved by Windows Settings → Apps → Claude Code → Repair.

Expected behavior

A problematic page (heavy client-side animation, aggressive scripts, bot-detection, whatever the underlying cause is) should fail gracefully within the Browser pane — a load timeout, a blocked-content message, a tool error — not take down the entire desktop application to the point of needing a system-level repair.

Notes / suspected contributing factors (unconfirmed)

  • The page has a fairly heavy animated background (particle/network-line effect), which may be resource-intensive for the embedded browser.
  • Possible that the site's bot/automation detection serves different (broken or resource-heavy) content to automated visitors specifically.
  • Neither of these is confirmed — flagging as the only distinguishing thing about this site versus others that load fine.

Severity

High from a usability standpoint — an unrelated third-party website should never be able to force an OS-level repair to recover the app.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗