Thanks for your input@crynobone, but this doesn't solve the full problem. The problem still exists if you use justconsole.php route file.

This change introduces a new issue where you cannot use both->withSchedule() on app bootstrap ANDconsole.php route file. You can observe this by having a task scheduled in both places and runningphp artisan schedule:list.

Note:inspire is scheduled insideconsole.php (comes by default in new install) andtest is scheduled inside bootstrap.

Before this change:

After this change:

You should defer resolving code dedicated for Schedule ifconsole.php. The file itself needs to be loaded for all artisam requests.

You are correct, I forgot the fact thatconsole.php is used for more than just schedule.

So the only issue I see now is that both methods cannot be used simultaneously while it could have been before.

So the only issue I see now is that both methods cannot be used simultaneously while it could have been before.

As in Laravel 10? It should only be possible to register Schedule withinApp\Console\Kernel::schedule(). So this should makewithScheduling() behave similar to the old method.

As in Laravel 11 before this change. I'll re-itterate my previous message.

This change introduces a new issue where you cannot schedule commands in both->withSchedule() on app bootstrap ANDconsole.php route file. You can observe this by having a task scheduled in both places and running php artisan schedule:list.

Note:inspire is scheduled inside console.php (comes by default in new install) andtest is scheduled inside bootstrap.

Before this change:

After this change:

With this change->withSchedule() is only resolved whenconsole.php route file is empty, otherwise it only lists (and processes) schedule fromconsole.php and ignores->withSchedule().

I'm pretty concerned about this breaking other applications.

I've been thinking how to solve it and I like this approach if it didn't have that drawback. It feels like it would need a different hook to somehow call the callback only when actually calling schedule commands? Or somehow have scheduled commands insideconsole.php route file to not resolveSchedule class until they are actually needed.

The only possible breaking change is when someone useswithScheduling() to add and schedule command, but that's never how it was intended to be used:

return Application::configure(basePath:dirname(__DIR__))    ->withSchedule(function ($schedule) {        Artisan::command('go',fn () =>$this->comment('Done!'))->hourly();    })->create();

With this PR,go command is only loaded viaschedule:list andschedule:run and cannot be called directly viaartisan.

Add additional tests to cover the limitation when adding new artisan commands withinwithSchedule()

I dunno, I'm not comfortable merging this without much more community feedback and input.