Problems that debug true in production can bring

I agree with all above comments. I've a suggestion for system who wants to use app_debug on production for just admin if it exists.

// in app\Exceptions\Handler.php

    public function render($request, Throwable $e)
    {
        if (in_array(get_class($e), [AuthenticationException::class,ValidationException::class, AuthorizationException::class])) {
            return parent::render($request, $e);
        }

        if (config('app.debug') && auth()->check() && Gate::allows('admin')) {
            return parent::render($request, $e);
        }

        return response()
            ->view('pages.error', [],  404);
    }

So, if user gets auth or validation error, system will act as what should it do such as redirecting to login route or redirecting to back with validation messages.

For other exceptions, debug page will be rendered if and only if user is logged in and has admin ability.

And finally, users will see your custom 404 page if they don't have acccess.

But even though this solution, you should keep closed your app_debug on production and use it when an error which you should investigate is occured.