New Debug Bar — Laravel debugging for developers and agents

Powerful, agent-friendly Laravel debugging—free and open source

Find bugs and bottlenecks without digging through scattered logs. Inspect anything in one place—while MCP gives your agent exact context with less guessing and fewer tokens.

composer require --dev newdebugbar/newdebugbar:dev-main

Supported by

Laravel 10+ and PHP 8.1+

The New Debug Bar request inspector showing the request trace, route, controller, response, query count, and duration for a Kyoto trip page

Sponsorship

Help build what’s next.

Sponsorship gives me more time to improve the New Debug Bar for the Laravel teams who use it.

Sponsor the project via GitHub Sponsors

  • Deeper diagnostics

    More ways to understand slow requests, find bugs, and see what happened.

  • Better workflows

    A clearer browser inspector and exact debugging context for coding agents through MCP.

  • Ongoing care

    Time for reported issues, maintenance, and new Laravel and PHP releases.

Benjamin Crozat

Creator of the New Debug Bar

Available for new projects

Hire me as a freelancer.

I bring more than 10 years of professional web development experience to your team. I connect business goals with product decisions and hands-on Laravel delivery.

  • Product direction

    Turn business needs into clear priorities.

  • Laravel development

    Build, improve, and launch your application.

  • Technical leadership

    Make decisions and keep delivery moving.

Email me about your project hello@benjamincrozat.com

Roadmap

Here’s what could make the New Debug Bar even better.

View the roadmap on GitHub

Requests and performance

  1. Searchable retained history

    Find every retained page, API, command, test, and worker profile from the browser.

  2. Cross-request comparison

    Compare duration, queries, failures, and section activity between two profiles.

  3. Failed query capture

    Show failed SQL with its bindings, connection, exception, and application source.

  4. Causal performance breakdown

    Explain where request time went across captured layers without counting the same work twice.

  5. Request-level capture rules

    Let an app decide whether to capture one request after route and authentication context is known.

Laravel ecosystem

  1. Inertia inspector

    Inspect components, props, partial or deferred data, and the application source behind a response.

  2. Laravel AI inspector

    Inspect agents, providers, models, token use, tool calls, and failures.

  3. Pennant inspector

    See which feature flags were evaluated and the value each request received.

Developer workflow

  1. Custom diagnostics API

    Add application messages, timers, measurements, and manually reported exceptions.

  2. Controlled collector extensions

    Let packages add bounded inspector sections while keeping redaction and MCP access intact.

  3. Editor navigation and path mapping

    Open captured source in a local editor even when Laravel runs in Docker or on a remote machine.

  4. Server-Timing headers

    Expose useful request timing in browser developer tools without opening the inspector.