[Bug] /chrome Claude in Chrome Status: Disabled - Native Messaging Host not installing (Windows)

Resolved 💬 3 comments Opened Dec 25, 2025 by marksgonepublic Closed Dec 28, 2025

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?

/chrome shows Status: Disabled even though Extension: Installed. Selecting "Reconnect extension" opens Chrome briefly then closes immediately. Status never changes to Enabled. Native Messaging Host is not being created.

Tested on 2 different Windows 11 machines - same result on both.

What Should Happen?

Status should change to Enabled after running "Reconnect extension" and authorizing the connection.

Error Messages/Logs

No error messages displayed. Chrome tab opens briefly and closes. Status remains "Disabled".

Steps to Reproduce

  1. Install Claude Chrome extension v1.0.36
  2. Set Chrome as default browser
  3. Run: npx @anthropic-ai/claude-code --chrome
  4. Login with Claude subscription (Option 1)
  5. Type /chrome
  6. Select "Reconnect extension"
  7. Chrome opens briefly, then closes
  8. Status remains "Disabled"

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.76

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Claude Model: Sonnet 4.5
Is this a regression?: I don't know
Claude Code Version: 2.0.76
Platform: Claude.ai (Pro/Max subscription)
Operating System: Windows
Terminal/Shell: PowerShell

  • Chrome version: 143.0.7499.170
  • Extension version: 1.0.36
  • Subscription: Max plan
  • API credits: $49.97 balance
  • Tried: logout/login, re-authorizing extension, clearing API key env variable
  • Same issue reproduced on 2 different Windows 11 machines

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗