Inertia DevTools Lands on the Chrome Web Store

Inertia DevTools is now listed on the Chrome Web Store, dropping the "download from GitHub and load unpacked" step that previously gated adoption. The extension adds an "Inertia" panel to Chrome DevTools that records every Inertia visit and shows exactly what was sent and received — the same category of visibility React and Vue DevTools give you for component state, applied to Inertia's request/response cycle.

What actually shows up in the panel

Every visit lands in a timeline on the left, with a live indicator while a request is in flight. Related requests — a visit and its follow-up partial reloads, deferred loads, polls, prefetches, and Precognition validation calls — are grouped into one entry instead of scattering across the list, which is the detail that makes the panel usable on a busy page rather than just a longer network log.

Selecting an entry opens four tabs:

• Props — every prop as a tree, with badges for deferred, optional, merged, and shared props
• HTTP — full request and response headers and bodies
• Route — the matched route name, URI, and controller action
• Page — the full page state after Inertia has processed the response, including anything merged in via partial reloads

File references throughout link straight into your editor, with VS Code, PhpStorm, Cursor, and Zed supported out of the box (Sublime Text needs a URL scheme handler).

Catching what the Network tab misses

Some Inertia interactions never touch the network — client-side visits and requests served from the prefetch cache don't generate a request Chrome's Network tab would show. The DevTools panel records these as their own timeline entries, so a navigation that resolved instantly from cache still shows up as something inspectable, instead of looking like nothing happened.

Privacy: nothing leaves your machine

Recorded entries are written to storage/inertia-devtools on your own application and pruned automatically; retention, limits, and the storage path are configurable under devtools.storage in config/inertia.php. Sensitive prop keys and headers — passwords, tokens, authorization headers — are redacted before storage, with the redacted key list configurable under devtools.redact. Common tooling routes like Telescope and Horizon are excluded from recording by default.

Getting it running

There's no package to install for the recording itself — it ships inside libraries most Inertia apps already have: the client-side adapter at ^3.6 and up, and the Laravel adapter at ^3.2 and up. Install the Chrome extension, open DevTools, select the "Inertia" panel, and run your Vite dev server for full functionality. Full setup details are in the Inertia DevTools documentation.