Repository navigation
Description
What happened
An agent on a remote Linux T3 Code server opened a browser tab. In T3 Code Desktop on macOS, the tab showed the page title and “Agent has control”, but the browser pane stayed black with the blue loading bar visible. The expected behavior is for the browser pane to show the loaded page or surface an actionable error if it receives no frame.
Diagnosis
The Linux server used its bundled Chrome Headless Shell 157.0.8103.78. In two fresh T3 tabs, the site loaded, the page reported document.readyState === "complete", and JavaScript evaluation succeeded. Neither tab delivered a requestAnimationFrame callback within a one-second probe. Snapshot capture timed out on both. A new Incognito profile also failed to produce a snapshot.
On the same host, a standalone launch of the same binary reproduced the capture timeout on a static data: page with a fresh profile and the sandbox enabled. It also reproduced with minimal launch options. This isolates a frame-production failure that can occur outside T3's viewer. The underlying reason Chromium stopped producing frames on this host is still unknown.
In this build, captureViewport places a deadline on Chromium's Page.captureScreenshot call and emits the snapshot error below. The viewer can display the tab title and control state while waiting for pixel data. Capture code in the affected build
Steps to reproduce
- Connect T3 Code Desktop on macOS to the affected Linux environment.
- Ask the agent on the Linux server to open
https://example.com/in a fresh remote browser tab withpreview_open. Observe that T3 returns the title “Example Domain” andloading: false. - Call
preview_snapshotfor the tab. On the affected host, it returns the screenshot frame timeout below. - Repeat with the Incognito profile. The snapshot also times out on the affected host.
The original desktop symptom was observed on a different page in the same remote environment. The public page reproduced the capture failure.
Version
T3 Code Desktop and server 0.1.10-nightly.20261116.4787. The server build maps to commit b5554ac8114f2ce7ce8b5973690ccb8cbb248efd. The newer nightly 0.1.11-nightly.20261118.4877 still pins Chrome Headless Shell 157.0.8103.78. Its behavior was checked in source. Newer nightly browser pin
Environment
- Client is T3 Code Desktop on macOS, connected to a remote Linux server.
- Server runs as a systemd user service on Linux x64, kernel 7.0.0-38-generic, Node v26.13.1.
- Browser is Chrome Headless Shell 157.0.8103.78 on Linux x64 with the Chromium sandbox enabled.
Evidence
preview_open: title="Example Domain", loading=false
preview_evaluate: readyState="complete", visibility="visible", animationFrame=false
preview_snapshot: The browser is not producing screenshot frames.
Standalone Chromium: HeadlessChrome/157.0.8103.78
Standalone Chromium: animationFrame=false
Standalone Chromium: Page.captureScreenshot timed out
A standalone screenshot probe also timed out after eight seconds without creating a PNG:
probe_dir="$(mktemp -d "$HOME/.cache/t3-frame-probe.XXXXXXXX")"
timeout --kill-after=2s 8s "$BROWSER_BIN" --headless \
--user-data-dir="$probe_dir/profile" --screenshot="$probe_dir/shot.png" \
--window-size=800,600 'data:text/html,%3Ch1%3EFrame%20probe%3C%2Fh1%3E'BROWSER_BIN is the path to T3 Code's bundled Chrome Headless Shell.
Related issues
- PR fix(server): a stalled viewer screencast no longer locks its preview tab #33760 also reports stalled Linux headless Chromium. It covers a viewer waiting on screencast setup. In this report, the client showed control state, server traces recorded successful viewer attaches, and the frame failure also occurred outside T3. PR #33760
- Issue [Bug]: Remote preview stays on "Connecting to browser…" when the viewer's first still capture never answers #24852 covers a viewer handshake blocked by the first still capture and was closed. Issue #24852
Workaround
On macOS, Open on this computer in the Browser tab menu uses the desktop browser for URLs reachable from the Mac. This is an available route around the Linux browser and was verified in the affected build's source. Browser tab menu implementation
Agent
Prepared by Codex using GPT-6.2 Sol (high reasoning effort) in T3 Code.
Activity