You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Browser preview recordingStart times out on an agent-owned dev-client tab #28137
The built-in Browser tool returned Preview automation recordingStart timed out after 15000ms on an agent-owned tab after pairing with an isolated Windows development environment.
Pair-page actions had worked, and the app initially returned DOM text through preview_evaluate. After loading the thread page, this operation failed. The tab remained available and owned by the same caller. No credentials are included in this report. Related initial snapshot failure: #28136.
Source: 28416e9, Windows, Codex harness. Please provide recovery or useful diagnostics for this operation rather than only the timeout.
For reference, on Linux at the same commit, preview_recording_start on a freshly paired dev-client thread tab returned at once and recorded normally, so the trigger is a tab that has stopped drawing, not the dev-client page itself.
Activity
juliusmarminge commentedon Oct 31, 2026
Duplicate of https://git.cafe/pingdotgg/t3code/issues/23514.
On main at 79f1fad,
preview_recording_starton a server-driven tab captures a first frame with a barePage.captureScreenshot(captureViewportinapps/server/src/preview/ServerBrowserPage.ts) while holding the tab's capture lock, with no deadline. When the tab stops producing frames (the same condition behind the snapshot timeouts in https://git.cafe/pingdotgg/t3code/issues/28136), that capture never settles, the broker gives up at 15000ms, and later actions on the tab queue behind it. https://git.cafe/pingdotgg/t3code/issues/23514 tracks this exact sequence (snapshot timeout, thenrecordingStart, then click/evaluate timing out until the tab is closed) and asks for the same outcome: a bounded failure that leaves the tab usable.For reference, on Linux at the same commit,
preview_recording_starton a freshly paired dev-client thread tab returned at once and recorded normally, so the trigger is a tab that has stopped drawing, not the dev-client page itself.Closing in favour of https://git.cafe/pingdotgg/t3code/issues/23514; follow that issue for the fix.