::callout{type="danger" title="Never registered in a build"}
The panel exposes the resolved config, the file system paths behind it and a
button that deletes a cache directory. None of that is anybody's business in
production, which is why the module returns before registering anything outside a
dev server.
::

## Response

`text/html`, one document per panel: `/_duxt/devtools` is the Sources panel and
each other panel hangs off it — `/_duxt/devtools/paths`, `/_duxt/devtools/pages`
and so on, in the order the tab row shows them.

The same documents are what Nuxt Devtools frames in its **duxt** tab, so the
route exists to be opened in a window of its own — a wide table is easier to read
outside a drawer.

## Notes

What each panel answers, with every panel rendered as it looks, is a section of
its own: [Devtools](/reference/devtools).