The New Debug Bar
Debug Laravel with exact request data
Start with a request, follow the evidence to the code that produced it, and give local coding agents the same captured context.
-
Capture a request
Install the package, repeat the action, and select its exact profile. -
Follow the evidence
Use the inspector or your coding agent to trace a finding to its source. -
Verify the change
Repeat the same action and compare its data, behavior, and measurements.
Getting started
Installation
Install the package and confirm the bar appears in your Laravel app.
Read the guideRequests
Choose the right request profile and understand what happened during it.
Read the guideLocal environments
Keep Laravel web requests, MCP commands, containers, and queue workers aligned on the correct PHP runtime, environment, and profile storage.
Read the guideTroubleshooting
Troubleshooting
Fix a missing Laravel debug bar, an MCP connection problem, or missing request profiles with focused checks and a visible result.
Read the guideThe bar will not open
Diagnose missing toolbar injection, disabled profiling, JSON responses, asset failures, and Livewire startup errors in a Laravel app.
Read the guideMCP connection problems
Diagnose PHP paths, wrong Laravel applications, startup errors, missing MCP tools, and an empty profile list.
Read the guideMissing profiles and data
Find a missing Laravel request profile and distinguish retention, current-page discovery, capture limits, MCP pagination, and live-only evidence.
Read the guideUse with agents
Debugging workflows
Queries
Find slow, repeated, and likely N+1 queries, then trace them to application code.
Read the guidePerformance
Use duration, query time, memory, and the timeline to locate expensive work.
Read the guideLivewire
Inspect Livewire requests, mounted components, updates, and related browser activity.
Read the guideErrors and logs
Follow exceptions and log messages back to the code and context that produced them.
Read the guideArtisan commands
Inspect Laravel Artisan command profiles, exit codes, queries, logs, and failures through The New Debug Bar local MCP server.
Read the guideFramework activity
Eloquent
Review model retrievals, writes, repeated work, and the queries behind them.
Read the guideBlade views
Inspect Blade view occurrences, original template sources, registered composers, and retained view data with The New Debug Bar.
Read the guideEvents and listeners
Find dispatch sources, repeated Laravel events, listener registrations, duplicate listeners, and related queued activity.
Read the guideAuthorization
Trace a Laravel authorization decision to its ability, user, arguments, policy or Gate handler, and application source.
Read the guideValidation
Inspect Laravel and Livewire validation failures, error bags, failed fields, messages, rules, source, and the selected response.
Read the guideHTTP client
Inspect outbound Laravel HTTP requests, responses, timing, and failures.
Read the guideQueues
See which jobs were dispatched, where they were sent, and what triggered them.
Read the guideMail and notifications
Preview mail and inspect notification recipients, channels, payloads, and failures.
Read the guideCache and Redis
Understand cache results and direct Redis commands without losing their source.
Read the guideReference
Inspectors
See what each inspector captures and when to use it.
Read the guideConfiguration
Change environments, thresholds, retention, and capture limits only when needed.
Read the guideData and privacy
Understand local profile storage, retention, capture limits, and redaction controls.
Read the guideTesting
Turn saved profiles into focused Pest assertions for performance and correctness.
Read the guideMCP tool reference
Reference the five MCP tools in The New Debug Bar, including arguments, defaults, filters, response limits, JSON Pointer paths, and error states.
Read the guide