Laravel Boost now forcibly installed with the Laravel Installer?

[zircuitz]

The installer used to ask me if I'd like to install Laravel Boost in new projects. Now it doesn't do that anymore and just assumes yes. What happened to that?

Personally I don't use AI, so I have no need for Laravel Boost in my projects. Now I have to manually go in there and clean it out again. Is there a reason for this?

Really frustrating to me :(

[damiogunsiji]

Found the cause: c71e395 ("Quick onboard", merged July 2, 2026 in laravel/installer). It silently sets boost to true on the default no-starter-kit path, so the actual confirm prompt never fires:

// src/NewCommand.php#L292
if (! $input->getOption('boost') && ! $input->getOption('no-boost')) {
    $input->setOption('boost', confirm(
        label: 'Do you want to install Laravel Boost to improve AI assisted coding?',
    ));
}

Since boost is already true by then, ! $input->getOption('boost') is false and confirm() never runs.

Workaround: laravel new myapp --no-boost

Probably worth filing as a bug on laravel/installer rather than laravel/framework, since that's where the change lives.