Chrome DevTools & Console Errors

There’s another source of errors that’s really useful, and that’s your browser’s developer tools. Chrome DevTools (A set of web developer tools built into Chrome. Right-click -> Inspect to open it. Used for debugging, checking styles, and testing code.), specifically. If something’s not working on your website, like a button doesn’t do anything or data isn’t loading, the answer is usually in the console.

You open DevTools by right-clicking anywhere on the page and clicking Inspect, or pressing Command+Option+I on Mac or Ctrl+Shift+I on Windows. Then you click the Console tab. And you’ll see any errors that JavaScript is throwing, any failed network requests, all sorts of useful stuff.

The red text in there is what you want to pay attention to. It might say something like “Failed to fetch” or “Uncaught TypeError” or “404 Not Found.” That’s your clue. You copy that, you paste it to the agent, and you say “seeing this in the console when clicking the submit button.” That’s way more useful than just “it doesn’t work.”

And there’s a Network tab too, which shows you all the requests your page is making. If you’re trying to load data from an API and it’s not working, you can see in the Network tab whether the request is even being sent, what it’s sending, and what the server responded with. Super useful for debugging. You can screenshot that or copy the error details and give them to the agent.

This is another use case for browser tools — the agent can look at the site directly, inspect the console, read the error messages, and pass them back to its own context to fix.