The product

Investigations

What happens when you press Run investigation, and what the report may claim.

For LLMs

Where the button is

Run investigation sits on a session and on an issue. A session investigation explains that one visit. An issue investigation explains the group of errors that share a fingerprint.

Press it once. While it runs, the panel says it is reading the timeline and your code. That usually takes under a minute. Investigate again starts a new run. A follow-up question stays on the report you already have.

What it reads

The AI debug engineer reads that person’s timeline, other visits that look the same, and the repositories connected to this project. It can search log text and search code, including with a pattern it writes, then read the matching lines at the commit your release reported.

An investigation only reads. It cannot change your database. A separate step can pull the repositories you chose, run their tests, and open a pull request on a new branch when the report qualifies and the monthly allowance remains. A member can ask from the report after that. Merging stays theirs. It cannot push to the default branch or comment.

Overview lists each pull request with the issue, the people who hit it, and whether the failure was in the web app or the API. Open the request to read the diff and the tool calls. Both are stored with the request.

Connect at least one repository before you run an investigation. A web app, an API, and a worker can all be attached to the same project. After you connect one, Bugwalk reads the repository and shows the language and whether it looks like a frontend, a backend, or a worker. Set BUGWALK_RELEASE to the commit SHA in your build so the lines it cites are the ones that were deployed.

What the report contains

A headline, a confidence level, what happened, the root cause, and the findings. Every finding cites an event id or a file and line. A finding with no citation is marked that way, on purpose.

Low confidence is shown, with the reason. Treat that report as a lead. A suggested fix appears when the agent has one. A run that fails before it finishes is not charged.

What it costs

Each finished investigation counts toward the monthly number on your plan. Pro includes 100, Team includes 1,000. The count is on Project, Usage.

The agent has to be switched on for the workspace. If the button is disabled, that is why.