# fix\(server,desktop\): browser tools report why a page failed to load · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/ea692c644fa4347f936d49959a65b5cf00d077dc)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: ea692c644fa4347f936d49959a65b5cf00d077dc

Requested commit: ea692c644fa4347f936d49959a65b5cf00d077dc

Commit: ea692c644fa4347f936d49959a65b5cf00d077dc

Tree: 614ebe71d9c56a30c1a22d5a3b94377d1a6709da

Author: Robert Nisipeanu

Committer: Robert Nisipeanu

## Message

```
fix(server,desktop): browser tools report why a page failed to load

When a page fails to load in a T3 browser tab, preview_status and
preview_snapshot show only chrome-error://chromewebdata/, so agents cannot
tell why. Both now include loadError with the failed URL, the browser's
error code, and its description while the tab shows the error page.

Server-rendered tabs record the failure from Playwright's requestfailed on
main-frame navigations and clear it when the next navigation starts.
Desktop-rendered tabs can fail their first load before the server connects,
so the desktop forwards did-fail-load for server tabs over the desktop
browser channel as a loadFailed event, including failures from before the
webview registered with its tab. The server uses the desktop's report only
until it observes a navigation itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [5fe7568e871c0310c83fac0484fb84bba14d9148](https://git.cafe/pingdotgg/t3code/commit/5fe7568e871c0310c83fac0484fb84bba14d9148?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/ea692c644fa4347f936d49959a65b5cf00d077dc?format=markdown)