What browser logs show
Browser logs capture everything that happens in your app’s frontend:- JavaScript errors and exceptions
- Messages from your code
- Warnings from frameworks like React
- Network request failures
- Unhandled errors
When browser logs help
Browser logs are useful when: A button click does nothingBrowser logs show JavaScript errors preventing the action. Content doesn’t appear
Browser logs reveal issues loading or displaying information. Forms don’t work
Browser logs show errors in validation or submission logic. The agent is debugging for you
When the agent investigates frontend issues, it checks browser logs to understand what’s failing. Logs give the agent the context needed to fix problems.
How to enable browser logs
By default, browser logs are hidden to keep the interface simple. Turn them on when you need to debug.- Click the Settings icon in the sidebar
- Go to the Appearance tab
- Toggle “Enable Logs” on
Using the logs panel
Expand or collapse the panelClick the chevron button on the left side of the panel to show or hide logs. Switch between log types
Click the “Browser Logs” tab to see frontend output, or “Server Logs” to see backend output. Read the logs
Logs appear in chronological order. The panel scrolls automatically as new logs arrive. Scroll up to pause auto-scroll and read older logs. Stale logs
After the agent finishes responding, browser logs are marked as “stale” with reduced opacity. This helps you tell the difference between logs from before and after the latest changes. Browser logs reset when you refresh the page.
Understanding log messages
Browser logs use colors to indicate the type of message:| Color | What it means |
|---|---|
| Gray or white | Normal output—everything is working |
| Yellow | Warning—something might be wrong |
| Red | Error—something failed |
| Blue | Information message |