[BUG] Claude in Chrome: "Browser extension is not connected" on Windows — `tengu_chrome_auto_enable` forced to `false` by server

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?

Environment

• Platform: Windows 11
• Claude Code version: 2.1.72 (native install)
• Chrome extension version: Latest from Chrome Web Store
• Chrome profile: Default
• IDE: Cursor (also tested from standalone terminal)
• Anthropic plan: Paid (Max)

Bug Description

All mcp__claude-in-chrome__* tool calls return "Browser extension is not connected" despite:

1. /chrome reporting Status: Enabled, Extension: Installed
2. /mcp showing claude-in-chrome · ✔ connected
3. Native messaging host correctly configured
4. Chrome extension installed and enabled with no errors

The MCP layer reports a successful connection, but every actual tool invocation (e.g., tabs_context) fails with the "not connected" error.

Root Cause Identified

The server-side feature flag tengu_chrome_auto_enable is set to false in cachedGrowthBookFeatures inside .claude.json. Manually changing it to true is immediately reverted on the next Claude Code startup when the server pushes the cached config.

"tengu_chrome_auto_enable": false

This matches the root cause identified in #29528, #30722, #31971, and #32496.

Troubleshooting Already Performed

• Full Chrome restart (taskkill /f /im chrome.exe + reopen)
• Reinstalled Chrome extension
• Verified same account on claude.ai and Claude Code CLI
• Created native messaging host config manually at:

%LOCALAPPDATA%\Google\Chrome\User Data\NativeMessagingHosts\com.anthropic.claude_code_browser_extension.json

• Added Windows Registry entry at:

HKCU\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code_browser_extension

• Native host wrapper exists at ~\.claude\chrome\chrome-native-host.bat pointing to ~\.local\bin\claude.exe --chrome-native-host
• Manually set tengu_chrome_auto_enable: true in .claude.json → reverted to false on next startup
• Verified only Default Chrome profile exists (no profile mismatch)
• /chrome → "Reconnect extension" → still fails on tool calls

Actual Behavior

Tool calls fail with "Browser extension is not connected" because the tengu_chrome_auto_enable feature flag is forced to false server-side, overriding any local configuration.

Request

Please enable the tengu_chrome_auto_enable flag for my account, or roll out Chrome support more broadly so the flag isn't gating connections that are otherwise fully functional.

What Should Happen?

Expected Behavior

When /chrome reports Enabled and /mcp shows claude-in-chrome · ✔ connected, browser tool calls should work.

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce

1. Install Claude Code v2.1.72 on Windows
2. Install Claude in Chrome extension from Chrome Web Store
3. Log into claude.ai in Chrome with the same account
4. Run claude --chrome in terminal
5. Run /chrome → reports Status: Enabled, Extension: Installed
6. Run /mcp → shows claude-in-chrome · ✔ connected
7. Ask Claude to "Take a screenshot of my current Chrome tab"
8. Get error: "The Chrome browser extension isn't connected"

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.72

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Cursor

Additional Information

_No response_