Hand off production errors to your coding agent

When a new error appears, AI Bug Analysis runs the first investigation against your production data and your code. Your coding agent reads it through the Inspector MCP server and starts from the likely cause.

AI Bug Analysis is included in every plan.

How it works

  1. 1

    Connect your repository

    Connect GitHub or GitLab to your app, and AI Bug Analysis turns on.

  2. 2

    Inspector investigates the error

    When a new error appears in production, Inspector checks it against your production data and your code, then lists the likely causes.

  3. 3

    Hand it to your coding agent

    Copy the prompt from the dashboard or the error email into your coding agent. It reads the analysis through the Inspector MCP server and fixes the code.

It starts from what happened in production

The analysis reads the latest occurrences of the error, how often it happens, the request or job that failed and the commits from the week before it first appeared.

Latest errors detected

MessageAppHitsLast seenAI Analysis
Call to a member function format() on nullshop-api482 minutes agoRead analysis
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entrybilling129 minutes agoAnalyzing
cURL error 28: Operation timed out after 5000 millisecondsshop-api71 hour agoRead analysis

Evidence your agent can check

It ranks up to three likely causes by confidence. Each one shows its evidence from production, your code or the commit history, and says what to change in which files. It also lists what it ruled out and what it couldn't verify.

AI Bug Analysis

ReadyHigh confidence

Invoices created by the import job have no due date, so dueDate() returns null and format() throws.

Read main@4c1e9a7f02 · occurrence 2026-11-18 09:42:13 UTC · evidence 2026-11-11 to 2026-11-18

1. Imported invoices have no due date

  • productionThe 10 latest occurrences are all on invoices created by the import job.transaction:8f3a91c07e
  • codeThe import job creates invoices without setting due_date.app/Jobs/ImportInvoices.php:57
  • historyThe import job was added two days before the error first appeared.commit:9b1e4c2d7a

What to change: Set a due date when the import job creates an invoice, or show a placeholder when it is missing. This is a product choice, so ask the user.

app/Presenters/InvoicePresenter.php:31app/Jobs/ImportInvoices.php:57

Ruled out: A change to the date format: the date is null, not malformed.

Your coding agent takes it from there

AI Bug Analysis describes the change and never writes code. Your coding agent reads the analysis first through the MCP server, checks it against your code, then makes the change and can open a pull request. If an error has no analysis yet, the agent's request starts one.

Coding agentInspector MCP connected

Investigate and fix an error that Inspector detected in production.

  • get_error_analysis Call to a member function format() on null
  • transaction_details GET /api/invoices/{id}

The analysis checks out: ImportInvoices never sets a due date. Should imported invoices get one, or should the page show a placeholder?

Show a placeholder.

app/Presenters/InvoicePresenter.php
- return $this->invoice->dueDate()->format('d/m/Y');+ return $this->invoice->dueDate()?->format('d/m/Y') ?? 'Not set';

Give your coding agent eyes on production

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.