Skip to Content
Debugging with Logs and Screenshots

Debugging with Logs and Screenshots

AI agents debug better when they have the same evidence a strong engineer would ask for.

The most useful evidence

  • the exact route
  • whether you were signed out, without access, with granted access, or newly paid
  • the exact error message
  • the screenshot
  • the steps that produced the issue

Why logs matter

Logs show what the system thought was happening. That is often more valuable than a summary like “login is broken” or “payments are weird.”

Why screenshots matter

Screenshots show the visible state, the wrong copy, the loading state, the missing button, or the unexpected layout. They are often the fastest way to remove ambiguity.

Good debug handoff

Give the agent:

  • one bug at a time
  • the raw error text when possible
  • the screenshot or browser evidence
  • the exact expected behavior

What success looks like

You are debugging well when each report gives enough context that the agent can investigate a root cause instead of asking basic follow-up questions.

Last updated on