No, it’s highly risky! Laravel is designed for stateless environment States bleeding among coroutines will be a mess in Laravel Event if Laravel supports coroutines within single request , the worker is still occupied until the end of all I/O operations Laravel team has little possibility to support coroutine due to the considerations of the current ecosystem and backward compatibility It’s not a package-level thing, it’s about the whole framework and related ecosystem