Claude in Chrome: extension connects but all page-interaction tools time out waiting for document_idle

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 23, 2026

After getting the extension installed and connected (tabs_context_mcp succeeds and returns valid tab IDs), every tool that needs to read or interact with a page fails identically:

  • get_page_text, find, and computer screenshot all fail
  • Error for get_page_text/find: "Page still loading (executeScript waited 45000ms for document_idle)"
  • Error for computer screenshot: "Script injection timed out after 5000ms — the page is busy or mid-navigation"

Troubleshooting already done, all with the same result:

  • Tried on the original LinkedIn tab, a brand-new tab, and a completely fresh session/tab group
  • -restarted Chrome and PC after install
  • Tried on a totally static page with no JS (https://example.com) — same failure
  • Disabled all other extensions (AdBlock, Adobe Acrobat, Google Docs Offline, Pop up blocker, Volume Master. . .etc) so only the Claude extension was active — same failure
  • Checked chrome://policy — no ManagedExtensionSettings or other policy restricting the Claude extension or scripting; only one unrelated policy (LocalNetworkAccessAllowedForUrls for a SharePoint domain)
  • Confirmed extension is version 1.0.85, enabled, site access set to "On all sites"
  • Restarted Chrome fully after install

Environment:

  • Windows, Chrome (managed browser — org profile, but no relevant policy found in chrome://policy)
  • Claude extension v1.0.85
  • Multiple Chrome extensions also installed (now disabled during testing): AdBlock, Adobe Acrobat, Google Docs Offline, Pop up blocker, Volume Master

Expected: get_page_text/find/screenshot should return page content/screenshots.
Actual: every one of them times out waiting for document_idle, even on a blank static page, suggesting the extension's script injection mechanism itself is not completing on this setup.

View original on GitHub ↗