### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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? Every synthetic input action from Claude in Chrome (computer left_click / type / key) is silently dropped, on every site and every tab. Tool results still

[BUG] [BUG] Claude in Chrome 1.0.85 + Chrome 151 (Windows): all clicks/keystrokes silently dropped — "Debugger is not attached to the tab with id" on every input dispatch

Status Open

Maintainer reply None cached

Activity 0 comments · opened Aug 21, 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?

Every synthetic input action from Claude in Chrome (computer left_click / type /
key) is silently dropped, on every site and every tab. Tool results still report
success ("Clicked at…", "Typed…") but the page receives nothing: after a click,
document.activeElement stays BODY; after typing, input values stay empty.
Meanwhile navigate, screenshot, read_page, get_page_text and javascript_tool all
work perfectly. Started abruptly ~2026-08-20 19:00 UTC with no local change.

Root-cause evidence (extension service-worker console open during a live probe,
screenshot attached): the "Claude started debugging this browser" banner IS
showing (browser-level attach succeeds), and every input action logs — twice:

Unchecked runtime.lastError: Debugger is not attached to the tab with id: <tabId>.

from mcpPermissions-192xiXNg.js:2, alongside {keyInputs: Array(1)}. So per-tab
debugger input dispatch is being issued against tabs the extension is not
attached to, and the failure is swallowed — the tool reports success while
Chrome discards the event.

Not fixed by: full Chrome restart · desktop app update + restart · extension
Update (stays 1.0.85) · disable/enable toggle · remove + reinstall · full PC
reboot. Fresh tabs and fresh tab groups fail identically. Confirmed from two
independent Claude sessions. Only other extensions installed: Bitwarden and
Google Docs Offline (no debugger conflict).

Environment: Claude in Chrome 1.0.85 (Web Store) · Chrome 151.0.0.0 · Windows ·
Claude Desktop app current as of 2026-08-21.

Impact: all click/keystroke browser automation is dead machine-wide; read-only
automation unaffected.

What Should Happen?

Clicks and keystrokes dispatched by the extension should be delivered to the
page: clicking a text input should focus it (document.activeElement becomes the
input) and typed characters should appear in it — as they did until
~2026-08-20 19:00 UTC. If per-tab debugger attach fails, the computer tool
should surface an error instead of reporting "Clicked"/"Typed" success.

Error Messages/Logs

Unchecked runtime.lastError: Debugger is not attached to the tab with id: 134174171.
Unchecked runtime.lastError: Debugger is not attached to the tab with id: 134174171.
{keyInputs: Array(1)}    (from mcpPermissions-192xiXNg.js:2)

These two errors appear in the extension's service-worker console for EVERY
click/type action, at the same moment the «"Claude" started debugging this
browser» banner is displayed. Same tab-id pattern for every tab tried,
including freshly created ones. Screenshot attached.

Steps to Reproduce

Windows PC, Chrome 151.0.0.0, Claude in Chrome extension 1.0.85, connected

to a Claude session through the Claude Desktop app.

Ask Claude to open any page with a text input in a new tab (e.g. a GitHub

repo's Branches page, which has a "Search branches" box).

Ask Claude to real-click the input and type a short token (e.g. "ZQXJ")

with the computer tool. The tool reports success ("Clicked at…", "Typed…").

Read the input state via javascript_tool: document.activeElement and the

input's value.
Expected: input focused, value "ZQXJ" (length 4).
Actual: activeElement is still BODY, value length 0 — every attempt, every
site (github.com, chatgpt.com), every fresh tab, from two independent
Claude sessions.

Open chrome://extensions → Claude → Inspect views → "service worker",

repeat step 3: each input action logs two
"Unchecked runtime.lastError: Debugger is not attached to the tab with
id: <tabId>." errors (from mcpPermissions-192xiXNg.js:2) while the
«"Claude" started debugging this browser» banner is displayed.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Input worked on this same machine until ~2026-08-20 19:00 UTC. Extension shows 1.0.85 after the failure began; I can't confirm which extension version was running immediately before (silent auto-update suspected), or whether Chrome updating to 151 is the trigger.

Claude Code Version

N/A — not using the CLI. Claude Desktop app (updated to latest 2026-08-21) + Claude in Chrome extension 1.0.85.

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Not fixed by: full Chrome restart, desktop app update + restart, extension

Update, disable/enable toggle, remove + reinstall, full PC reboot.

Read-only tools (navigate, screenshot, read_page, get_page_text,

javascript_tool) work perfectly throughout — only injected input is dead.

Only other extensions installed: Bitwarden, Google Docs Offline.
Service-worker console screenshot attached (errors during a live probe).

View original on GitHub ↗