Claude in Chrome: screenshot/JS calls intermittently take 30-45s on a subset of pages (not a universal timeout)

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 24, 2026

Component: Claude in Chrome extension — renderer bridge for the computer screenshot action and JavaScript execution

Summary: Screenshot and JavaScript-execution calls against some pages are intermittently slow — 30 to 45 seconds — rather than returning in a few seconds like most pages. This is narrower than issues like #94757/#77670 (which describe a consistent timeout across all pages): here most pages are fast, and a minority of pages are slow, intermittently, rather than uniformly failing.

Steps to reproduce:

  1. Navigate to a page with substantial dynamic content (observed on a marketing SaaS dashboard and a Google console page, among others).
  2. Issue a computer screenshot action, or a JavaScript-execution call, against that page.

Expected: The call returns within a few seconds, consistent with lighter pages.

Actual: The call intermittently takes 30 to 45 seconds, and occasionally times out outright, specifically on a subset of heavier pages. Observed repeatedly across an extended attended-automation session; in a separate, later verification pass, two different dashboard-style pages each needed a second, longer wait before a screenshot returned usable content, though neither crossed into an outright timeout that time.

Impact: Slows down automation tasks and raises the odds of a mid-batch disconnect on the affected pages.

Current workaround: keep batches of tool calls small, and wait explicitly for a page to settle before trying to read or screenshot it.

View original on GitHub ↗