People searching “Laravel Telescope Vue” install it in production to watch Inertia requests. It records request bodies. That includes passwords if you are not careful, and it is a second app on your URL. Keep it local.
TL;DR
- Telescope is a dev dependency.
- The default gate should not let the public open /telescope.
- Do not return true for every user so a Vue admin link can open it.
- Do not require Telescope without
--devand then try to prune it later.
The fix#
composer require laravel/telescope --dev
php artisan telescope:install
php artisan migrateThe published TelescopeServiceProvider gates viewTelescope. Leave that gate on local. Do not return true for every user so a Vue admin link can open it.
Inertia requests show up as HTTP requests. You can see the props and the session. That is useful on your machine. It is not a product feature, and the Vue page should not iframe it.
What to avoid#
Gotcha
Do not require Telescope without --dev and then try to prune it later. Do not register it in every environment because CI was missing the provider. CI does not need the UI.
FAQ#
How do I install Telescope for local debugging?
Telescope is a dev dependency. The default gate should not let the public open /telescope.
What goes wrong with Laravel Telescope Vue?
Many developers install it in production to watch Inertia requests. Do not return true for every user so a Vue admin link can open it.



