# \[Bug\]: Browser tools don't tell agents why a page failed to load · Issue \#18555 · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/issues/18555)

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

Visibility: public

State: backlog

Priority: 0

## Description

[Discussion and activity](https://git.cafe/pingdotgg/t3code/issues/18555)

---

### Before submitting

- [x] I searched existing issues and did not find a duplicate.
- [x] I included enough detail to reproduce or investigate the problem.

### Area

apps/server

### Steps to reproduce

1. In a thread, open the Browser panel and load `https://self-signed.badssl.com/` (any page that fails to load: an untrusted certificate, a refused connection, a blocked port).
2. The panel shows Chromium's "This site can't be reached … ERR_CERT_AUTHORITY_INVALID" page.
3. Ask the agent to call `preview_status` and `preview_snapshot` on that tab.

### Expected behavior

The browser tools tell the agent why the page did not load: the URL that failed, the browser's error code, and its description.

### Actual behavior

`preview_status` returns only `"url": "chrome-error://chromewebdata/"` with an empty title, and `preview_snapshot` has no page text. For a tab the desktop app renders, the failure usually happens before the server connects to the page, so nothing in either result names the error. The agent has to guess (often a self-signed certificate on a LAN device) or ask the user to read the screen.

### Impact

Minor bug or occasional failure

### Version or commit

main @ 5fe7568e87

### Environment

macOS, web dev server (server-rendered tabs); desktop-rendered tabs reasoned from code.

### Workaround

The user reads the error page in the Browser panel and tells the agent. For server-rendered tabs, the failed request sometimes appears in `preview_snapshot`'s `networkEntries` if it has not been pushed out by later requests.

Earlier attempt at a fix: #16835 (closed for incomplete verification).