[BUG] --chrome integration stops registering browser tools after simultaneous update of CLI (2.1.175→2.1.289) and extension (1.0.94→1.0.98)

Status Open
Reported on v2.1.289
Maintainer reply None cached
Activity 0 comments · opened Oct 5, 2026

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

  • OS: Linux Mint 22.3 (kernel 7.0.0-34-generic, x86_64)
  • Chrome: 154.0.8037.97
  • Claude Code CLI: 2.1.289 (updated today from 2.1.175 — system install)
  • Claude in Chrome extension: 1.0.98 (auto-updated today from 1.0.94)

## What happened
Both the CLI and the extension updated on the same day (Oct 5, 2026).
After the updates, the browser control tools no longer register in Claude Code
sessions started with --chrome. The integration was working before the updates.

What Should Happen?

## Expected behavior
When Claude Code starts with --chrome, browser tools (navigate, click,
screenshot, type) should be available in the session, allowing Claude to
control the browser and request user approval per action.

## Actual behavior

  • The side panel opens and shows only the claude.ai web chat interface.
  • No browser control tools appear in the session tool registry.
  • No errors are logged anywhere (silent failure).
  • The native messaging host launches correctly (confirmed via ps aux):

/home/user/.npm-global/.../claude.exe --chrome-native-host (PID active)

  • The bridge socket is created: /tmp/claude-mcp-browser-bridge-<user>/<pid>.sock
  • Despite all components appearing healthy, no tools register.

## Additional context

  • The extension has "Em todos os sites" (all sites) access granted.
  • The alias correctly passes --chrome: command claude --remote-control --chrome
  • Before the updates, a stale native host was running from the system install

(/usr/lib/node_modules/.../claude.exe --chrome-native-host, v2.1.175).
Killing it and reopening the Chrome panel started a new host from the correct
user install (v2.1.289), but tools still did not register.

  • 6+ session restarts attempted — no effect.
  • The `~/.config/google-chrome/NativeMessagingHosts/

com.anthropic.claude_code_browser_extension.json` manifest is present and
points to the correct script.

Error Messages/Logs

Steps to Reproduce

## Reproduction steps

  1. Have Claude in Chrome extension v1.0.98 installed and active.
  2. Start Claude Code with claude --chrome (or alias equivalent).
  3. Open the Chrome side panel.
  4. Observe: panel shows claude.ai chat only; no browser tools available in CLI.

## Workaround
None found. Manually providing credentials as text in the CLI chat as interim.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.289

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Xterm

Additional Information

_No response_

View original on GitHub ↗