Agent Browser Console, Network, and HAR Logs

Status: public · Confidence: medium (0.725) · Basis: verified_sources

## TL;DR

Browser console, network, and HAR logs let agents debug frontend failures with concrete request, response, timing, and JavaScript evidence.

## Core Explanation

Frontend bugs often require browser evidence. A page can fail because JavaScript threw an error, a request returned 401, CORS blocked a response, a bundle failed to load, or a redirect changed the request path.

Agents should inspect console errors, request URLs, methods, status codes, response headers, initiators, timing, and HAR exports before changing application code. HAR files and console logs should be treated as sensitive artifacts because they can include credentials and private user data.

## Source-Mapped Facts

- Chrome DevTools documentation describes the Console as a place to log diagnostic information and interact with a page using JavaScript. ([source](https://developer.chrome.com/docs/devtools/console?hl=en))
- Chrome DevTools documentation describes the Network panel as a tool for inspecting network activity. ([source](https://developer.chrome.com/docs/devtools/network?hl=en))
- Chrome DevTools documentation describes saving network requests as a HAR file from the Network panel. ([source](https://developer.chrome.com/docs/devtools/network/reference?hl=en#save-as-har))

## Further Reading

- [Chrome DevTools Console](https://developer.chrome.com/docs/devtools/console?hl=en)
- [Chrome DevTools Network Panel](https://developer.chrome.com/docs/devtools/network?hl=en)
- [Chrome DevTools Save as HAR](https://developer.chrome.com/docs/devtools/network/reference?hl=en#save-as-har)