Connect your repository, and Inspector analyzes production errors against your code, then sends you a proposed change to review.
AI Bug Fix is included in every plan.
Give Inspector access to GitHub or GitLab, then choose the projects to activate.
When an error occurs in production, Inspector reads the stack trace and the code it points to in your repository.
You receive the proposal by email and find it next to the error in your dashboard, ready to review.
Each proposal is based on what happened in production, so it works from the actual stack trace rather than a description of the problem.
| Message | App | Hits | Last seen | AI Bug Fix |
|---|---|---|---|---|
| Call to a member function format() on null | shop-api | 48 | 2 minutes ago | Read the fix |
| SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry | billing | 12 | 9 minutes ago | Try AI Bug Fix |
| cURL error 28: Operation timed out after 5000 milliseconds | shop-api | 7 | 1 hour ago | Try AI Bug Fix |
A proposal explains the cause and shows the change it suggests. You decide what goes into your code.
Bug fix proposal
Invoices created by the import job have no due date, so dueDate() returns null and format() throws. Return a placeholder when the date is missing.
- return $this->invoice->dueDate()->format('d/m/Y');+ return $this->invoice->dueDate()?->format('d/m/Y') ?? 'Not set';AI Bug Fix proposes the change. To have it applied, connect your coding agent to the MCP server: it reads the same error, changes the code and can open a pull request for you.
What broke in production this morning?
Invoice::dueDate() returns null for invoices created by the import job. A guard in InvoicePresenter fixes it. Should I open a pull request?
Yes, open it.
Install the package, connect your agent, and let it find the next problem before your customers do.
Free up to 30K transactions a month. No credit card.