Project-level claudeInChromeDefaultEnabled setting is ignored at startup

Bug Description

claudeInChromeDefaultEnabled: true set in project-level .claude/settings.local.json does not enable the Chrome integration when the setting is absent or disabled in global settings (~/.claude/settings.json). However, enabling it globally works fine. This suggests the Chrome connection decision is made at startup before project-level settings are loaded, violating the documented settings precedence.

Steps to Reproduce

1. Have Chrome with the Claude extension installed and working
2. Do not set claudeInChromeDefaultEnabled in global settings (~/.claude/settings.json)
3. Set claudeInChromeDefaultEnabled: true in project-level .claude/settings.local.json:

``json
{
"permissions": {
"allow": ["Bash(php:*)"]
},
"claudeInChromeDefaultEnabled": true
}
``

1. Start a Claude Code session in that project directory
2. _Run /chrome — it returns "(no content)" and no browser tools appear_ (written by claude, not exactly true)

Expected Behavior

Per the documented settings precedence (highest → lowest):

1. Managed settings
2. Command line arguments (--chrome)
3. Local project settings (.claude/settings.local.json) ← should apply here
4. Shared project settings (.claude/settings.json)
5. User/global settings (~/.claude/settings.json)

Project-level claudeInChromeDefaultEnabled: true should override a globally absent/disabled setting, but it does not.

Actual Behavior

Chrome integration is not established. /chrome returns "(no content)". Adding claudeInChromeDefaultEnabled: true to global ~/.claude/settings.json immediately fixes it.

Workaround

Launch Claude Code with the --chrome flag: claude --chrome

Environment

• Claude Code version: 2.1.37
• Platform: Linux (Ubuntu 24.04.4 LTS, kernel 6.17.0-14-generic)
• Chrome version: 145.0.7632.75
• Native messaging host correctly configured at ~/.config/google-chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json