Laravel ships Cloud CLI

Laravel has added a new terminal mode called `cloud tinker` to its Cloud command-line tool, extending Laravel Cloud further into day-to-day developer work. (cloud.laravel.com) (x.com) The Cloud command-line interface is Laravel’s terminal app for deploying and managing apps, environments, databases, caches, domains, and other hosted resources on Laravel Cloud. Laravel’s documentation says the tool installs through Composer, requires PHP 8.2 or higher, and supports browser-based OAuth plus manual token entry. (cloud.laravel.com) (github.com) “Tinker” in Laravel is the framework’s read-eval-print loop, or REPL: a live console where developers can run small pieces of PHP code inside an application without editing files first. Laravel maintains Tinker as a separate open-source package, and the new Cloud variant brings that style of live inspection to hosted environments from the terminal. (github.com) (x.com) Laravel has been pushing Cloud beyond a web dashboard for weeks. In March 2026, the company said the Laravel Cloud application programming interface and command-line interface were generally available, describing the CLI as a layer built directly on top of the Cloud API. (laravel.com) (cloud.laravel.com) That shift puts more infrastructure work into scripts and local terminals instead of browser clicks. Laravel’s own docs say the CLI can create applications, configure environments, deploy code, monitor deployments, and save repository defaults so developers do not have to pass the same app and environment settings every time. (cloud.laravel.com) (github.com) The new `--editor` flag points in the same direction. The feature adds integrated editor support to the Cloud CLI workflow, giving developers a way to jump from a terminal session into an integrated development environment while working against a Cloud environment. (x.com) Laravel introduced the Cloud CLI publicly in March 2026 as a Laravel Zero-based tool for teams that prefer terminal-first deployment and management. The company’s blog said the tool was meant to fit into continuous integration and continuous delivery pipelines, feature-branch environments, and other automated workflows. (laravel.com 1) (laravel.com 2) The result is a steadier pattern in Laravel Cloud’s rollout: more of the platform’s hosting controls are moving into programmable interfaces, and more of the developer experience is happening without leaving the shell. (cloud.laravel.com) (laravel.com)