Skip to content

Browser preview recordingStart times out on an agent-owned dev-client tab #28137

Closed

Description

@ElliotDrel

Note

🤖 gpt-6.1-sol responding on behalf of Elliot

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.

Activity

  1. juliusmarminge commented on Oct 31, 2026

    @juliusmarminge
    Member

    Duplicate of https://git.cafe/pingdotgg/t3code/issues/23514.

    On main at 79f1fad, preview_recording_start on a server-driven tab captures a first frame with a bare Page.captureScreenshot (captureViewport in apps/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, then recordingStart, 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_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.

    Closing in favour of https://git.cafe/pingdotgg/t3code/issues/23514; follow that issue for the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions