[BUG] In-app Browser: actions fail with "Screenshot timed out after 5s" while the page is loaded

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?

Actions in the in-app Browser fail now and then with a render timeout, even though the page has loaded and is responsive:

• It happened 6 times in about two hours of Claude driving one dashboard site, to left_click, scroll, screenshot and zoom.
• In 5 of the 6 cases Claude retried the same call a few seconds later, and the retry succeeded. The sixth was not retried.
• Around the failures, get_page_text, find and javascript_tool calls on the same tab worked, so the page itself was fine.
• When the failing action is the first step of a browser_batch, nothing in the batch runs and Claude has to send the whole batch again.

The error text says the Claude window may be behind another window, which can stop the page from drawing. That fits my session: I was working in other applications while Claude drove the Browser, so the Claude window was often not in front. I could not confirm the window state for each failure.

What Should Happen?

While the tab is loaded, clicks, scrolls and screenshots should work whether or not the Claude window is in front. The error itself says the pane does not need to be displayed. If the page stops drawing because the window is in the background, the Browser could keep the pane from being throttled, or capture the screenshot without needing a fresh frame, instead of failing after 5 seconds.

Error Messages/Logs

actions[0] (computer:left_click) failed: left_click failed: Could not get the tab ready for input (it is not on screen and has not drawn yet): Screenshot timed out after 5s: the page did not finish rendering in time. Retry; the pane does not need to be displayed. Claude's window may be behind another window, which can stop the page from drawing; if this repeats, continue with `get_page_text` or `find`, or ask the user to bring it forward. (0 completed, 3 remaining)

actions[0] (computer:scroll) failed: scroll failed: Could not get the tab ready for input (it is not on screen and has not drawn yet): Screenshot timed out after 5s: the page did not finish rendering in time. Retry; the pane does not need to be displayed. Claude's window may be behind another window, which can stop the page from drawing; if this repeats, continue with `get_page_text` or `find`, or ask the user to bring it forward. (0 completed, 1 remaining)

actions[5] (computer:screenshot) failed: screenshot failed: Screenshot timed out after 5s: the page did not finish rendering in time. Retry; the pane does not need to be displayed. Claude's window may be behind another window, which can stop the page from drawing; if this repeats, continue with `get_page_text` or `find`, or ask the user to bring it forward. (5 completed, 0 remaining)

Steps to Reproduce

1. In the Claude desktop app on Windows, start a Claude Code session and open the in-app Browser on a client-rendered web app (mine was a single-page dashboard).
2. Ask Claude to fill in forms there, so that it sends browser_batch calls (navigate, wait, left_click, type, scroll).
3. While it works, switch to another application so the Claude window is behind it.
4. Within a few calls, a left_click, scroll or screenshot fails with the error above. Retrying the same call a few seconds later succeeds.

It does not happen on every call. It happened 6 times in about two hours.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude desktop app 2.19675.0.0, Claude Code 2.1.286

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Claude desktop app (Code tab) on Windows 11. The failures were not tied to one page: they happened on several pages of the same site (forms, settings, a thumbnail list).