Blog

Why it broke

Notes on the trace, the ticket, the version that was live, and the pull request an AI debug engineer opens before you debug.

A blank card already on the desk while a stack of papers sits unopened behind it.

What an AI debug engineer actually does

An AI debug engineer reads the visit and the commit that was live, then can open a pull request. It does not merge, and it does not guess from a paste.

  • Three doorways in a graphite wall, with one copper thread running through all three.

    Logs, replay, and APM are three rooms

    Logs, session replay, and an APM each show one piece of a failure. The person, the request, and the line were one visit. Read them together.

  • Two open notebooks of the same size, one with a copper bookmark and one without.

    You debugged the code on your screen

    The failure remembers the commit that was live. The file in your editor may be a later one. Set the release, then read that commit.

  • A thin strip of paper, like a stack trace, alone on a wide empty desk.

    The stack trace is not the bug

    A stack trace names the line that threw. It does not name the person, the click, or the request. Here is what to read instead.