# LaraBug version 4 is live

Published on 16 November 2026 at https://www.larabug.com/news/larabug-version-4-is-live

LaraBug started in 2016 as an exception tracker for Laravel. Version four is a different product with the same name: it watches the whole application, and an exception is one of the things it catches rather than the only one.

What it collects comes in two streams. **Issues** are what needs a person: an exception, a JavaScript error, a vulnerable dependency, or something the telemetry shows drifting. **Telemetry** is everything underneath, every request, query, job and scheduled task, kept with the context that explains it.

Issues

### What is new for issues

Exceptions used to be the whole product. They now share one list with everything else that needs someone, and each issue arrives with enough around it to act on.

- **The request behind the exception.** The exception page was rebuilt around it. The route, the user, the queries that ran and the job that dispatched it sit next to the stack trace.

- **JavaScript errors.** The browser, Vue, React and Inertia each have an SDK, and what they catch lands in the same list as the PHP errors.

- **CVE findings.** Your lockfiles are checked each night against the Packagist and OSV advisories. A vulnerable package becomes an issue that names the version that fixes it. Included in every paid plan.

- **Twenty detections.** Nothing has to be thrown for an issue to open. A route whose p95 passes its threshold opens one, and so does a statement repeated through one request, a queue whose ready jobs wait too long or a scheduled task that never fired. Each carries the evidence it was opened on.

- **Made for a team.** An issue has an assignee, a priority and comments. It can be snoozed, and it reopens itself if it comes back after you marked it fixed.

- **Alerts.** Slack, Discord, Microsoft Teams, email or a signed webhook, per team or per application, and quiet outside office hours if you ask. Email is on every plan, the other channels on the paid ones.

- **Agents.** An MCP server with eleven tools lets Claude, Cursor or any other client list your issues and read the latest occurrence with its stack trace. With a token that allows it, an agent can resolve, assign, snooze and comment, and every change it makes is on the issue's activity. Autofix, in beta, opens the fix as a draft pull request.

More on [issue tracking](https://www.larabug.com/features/issue-tracking), [vulnerability scanning](https://www.larabug.com/features/vulnerability-scanning), [alerts](https://www.larabug.com/features/alerting) and [the MCP server](https://www.larabug.com/features/ai-and-mcp).

Telemetry

### What is new for telemetry

Version three knew about exceptions and little else. The Laravel package now records what the application does between its errors, and the panel has a page for each kind.

- **Requests.** Every request with its queries, cache calls, outgoing HTTP, mail and the jobs it queued, on one timeline. A slow page shows you the line that made it slow.

- **Queries.** Slow queries are ranked by what they cost you, the time per call multiplied by how often it runs. The N+1 is listed with the endpoint it runs on.

- **Queues and jobs.** Throughput, failures and wait time per queue, and every job with its attempts and how long it took.

- **Scheduled tasks and commands.** Every run of every task on your schedule, including the one that quietly stopped firing.

- **Logs, mail and cache.** Your application log, searchable. Every mail the app sent, with its body. The hit rate of your cache and the keys that miss.

More on [performance monitoring](https://www.larabug.com/features/performance-monitoring), [query insights](https://www.larabug.com/features/query-insights), [queues and jobs](https://www.larabug.com/features/queues) and [scheduled tasks](https://www.larabug.com/features/scheduled-tasks).

### The panel, rebuilt

The applications, the settings and the issue list were rebuilt around the new data, and the whole panel works on a phone and a tablet. Two factor and passkeys are in, and so is a request for your data.

### The clients

The Laravel package registers itself with the exception handler and needs one value in `.env`, the DSN. There is no log channel to add and nothing to change in `bootstrap/app.php`. Install it with `composer require larabug/larabug`. The browser, Vue, React and Inertia SDKs are each their own package.

### Pricing

Every plan has unlimited seats. The tiers differ in how much you send and how long we keep it, and the paid ones add CVE scanning and the alert channels beyond email. The free plan stays free, and your data stays in the EU.

### The changelog and the roadmap

This page is the announcement. Everything that changed, line by line and with the release of each package it shipped in, is in [the version 4 changelog](https://www.larabug.com/changelog/version-4), and what version 3 shipped before it is [there too](https://www.larabug.com/changelog/version-3). What comes next is decided on [the public roadmap](https://roadmap.larabug.com): vote on what has already been asked for, or add the thing you are missing.

### What comes next

If you have been with LaraBug since the exception tracker days, thank you for waiting. If you are new, the free plan is the place to start, and the first error arrives a couple of minutes after `composer require`.
