Laravel Artisan: Complete 2026 Guide

Laravel Artisan is the command‑line interface that turns routine tasks into lightning‑fast workflows. Whether you’re a solo developer or a team running a production API, Artisan’s evolution through Laravel 13 brings a unified dev stack, built‑in diagnostics, and a sleek terminal UI that replaces ad‑hoc scripts. In this guide we’ll dissect every core feature, walk through the setup on modern stacks, benchmark real‑world tradeoffs, and finish with persona‑specific recommendations that match your team’s maturity level.

Overview of Laravel Artisan

What is Artisan?

Artisan is the CLI bundled with Laravel. It exposes a spectrum of commands—from php artisan make:model to php artisan migrate:fresh—that scaffold code, manage database migrations, and run background jobs. The new php artisan dev command, introduced in Laravel 13.16, consolidates several development processes into a single, tabbed terminal session.

History of Artisan in Laravel

Artisan debuted in Laravel 4, quickly becoming the go‑to tool for generating boilerplate. Over the years, each Laravel major release added depth: custom commands, testing helpers, and environment‑specific shortcuts. Laravel 13.25 introduced laravel/multiplex, a terminal UI that replaces the old concurrently wrapper, enabling color‑coded tabs and auto‑restart logic.

Artisan’s Role in the Laravel Ecosystem

Artisan sits at the heart of Laravel’s developer experience. It powers package scaffolds, automates test runs, and provides diagnostics like php artisan doctor. In 2026, the command is the single touchpoint for setting up a new project, debugging, and deploying to production—all while keeping the PHP stack lean.

Why Laravel Artisan Matters in 2026

Modern PHP Development Trends

PHP 8.2, released in late 2025, introduced union types, readonly properties, and a new pcntl_fork extension that Artisan leverages for the pail log viewer. Teams increasingly rely on side‑by‑side JS tooling like Vite, and Artisan’s dev command now orchestrates both the PHP dev server and the Vite dev server in a single process.

Artisan’s Impact on Productivity

By consolidating server launch, queue listening, and log streaming into one command, Artisan eliminates context switching. Developers no longer launch separate terminals for each task; the UI shows real‑time logs, timestamps, and allows per‑process restarts. The dev:list subcommand exposes the registry, helping teams debug misconfigurations quickly.

Integration with New Laravel 13 Features

Laravel 13.25 adds queue:pause and queue:resume as global queue controls, accessible via Artisan or the Queue facade. Horizon and Reverb are now first‑party services that can be registered through DevCommands::artisan('horizon', 'queue') and DevCommands::artisan('reverb:start', 'reverb'), respectively. Stripe CLI integration is also streamlined through DevCommands::register('stripe listen …').

Prerequisites & System Requirements

Supported PHP Versions

Laravel 13.25 requires PHP 8.1+; the full dev stack runs best on PHP 8.2 for the pcntl_fork extension, which powers the Pail log viewer. Without pcntl_fork, Pail falls back to a less efficient process.

Composer & Node Package Managers

Composer 2.6+ handles PHP dependencies. Node.js 22.13+ is required for laravel/multiplex. The NodePackageManager helper auto‑detects npm, yarn, pnpm, or bun based on lockfiles, ensuring npm run dev works regardless of the local setup.

Operating System & Server Stack

Any Linux distribution—Ubuntu 22.04, Debian 12, or CentOS Stream 9—supports Artisan out of the box. Windows users can run Artisan inside WSL2; however, Pail is unavailable on Windows due to missing pcntl_fork. For production, Apache or Nginx can proxy to the built‑in server during local dev.

Setting Up a Development Environment with Artisan

Installing Laravel 13.25

composer create-project laravel/laravel myapp "13.25.*"

Composer pulls the latest 13.25 release. Verify the version with php artisan --version.

Configuring .env for Dev

Set APP_ENV=local, APP_DEBUG=true, and configure database credentials. For API testing, add API_BASE_URL=http://localhost:8000.

Running php artisan dev and npm run dev

php artisan dev
# or
npm run dev

The first command launches the multiplexer UI, automatically spawning the PHP dev server on localhost:8000, the Vite dev server, a queue listener (queue:listen), and the Pail log viewer. The second command only starts Vite; the multiplexer handles the rest.

Core Artisan Commands

php artisan serve vs dev

Use php artisan serve for quick, single‑process debugging. php artisan dev is the full‑stack equivalent, offering tabs for each process and auto‑restart on crash.

queue:listen & queue workers

In dev mode, queue:listen --tries=1 --timeout=0 listens for jobs. Production uses queue:work with supervisor. Artisan’s queue:pause --all and queue:resume --all provide global control during maintenance windows.

pail & dev:list for debugging

Run php artisan pail --timeout=0 to view logs in a browser interface. php artisan dev:list prints all registered processes without launching them, useful for verifying DevCommands registrations.

Custom dev commands via DevCommands

In AppServiceProvider, register a custom process:

use DevCommands;
public function boot()
{
 DevCommands::artisan('run:my-script', 'my-script')
 ->green()
 ->withTimestamps();
}

Now php artisan dev will include my-script in the tabbed UI.

Advanced Features & Tools

Laravel Horizon & Reverb

Horizon offers a dashboard for queue metrics. Register it in dev mode with DevCommands::artisan('horizon', 'queue'). Reverb provides a real‑time broadcasting server; launch it via DevCommands::artisan('reverb:start', 'reverb')->purple().

Laravel Multiplex & Vite

Multiplex replaces concurrently and offers a terminal UI with search, per‑tab restart, and auto‑restart. Vite powers the frontend build; Artisan automatically runs npm run dev with the detected package manager.

Stripe CLI & Laravel OpenAPI CLI

Integrate Stripe webhooks in dev with:

DevCommands::register('stripe listen --forward-to '.config('app.url').'/stripe/webhook', 'stripe')->orange();

For OpenAPI, install spatie/laravel-openapi-cli and register the spec: OpenApiCli::register('https://api.example.com/openapi.yaml'). Generated commands like php artisan acme:get-orders let you hit your API from the terminal.

TypeScript support with tsc

Run the TypeScript compiler in watch mode with:

DevCommands::nodeExec('tsc --noEmit --watch --preserveWatchOutput', 'types')->yellow();

Logs appear in the multiplexer, and the compiler halts on type errors.

Real‑World Tradeoffs & Performance

Development vs Production Mode

In dev, php artisan dev runs processes in the foreground, making debugging easier. Production uses php-fpm and supervisor to manage workers, ensuring isolation and resilience. Switching between modes requires minimal changes to .env flags.

Resource Footprint of dev command

Running dev consumes roughly 200 MB of RAM on a typical laptop, a modest footprint compared to Docker‑based stacks. The multiplexer’s UI adds negligible overhead. On headless servers, launching dev is not recommended; instead, use queue:work and php-fpm.

Handling Large Queues in Production

For high‑volume queues, turn off queue:listen and use queue:work --daemon. The global pause commands allow you to halt all queues during database migrations or maintenance, preventing new jobs from queuing.

Best Practices & Configuration Tips

Optimizing dev command with concurrently

While multiplex is the default, some teams still prefer concurrently for simplicity. Use npx concurrently "php artisan serve" "npm run dev" if you need a lightweight alternative.

Using pnpm/Yarn/Bun for faster builds

The NodePackageManager helper detects the lockfile and selects the appropriate package manager. pnpm and bun reduce install time and disk usage, especially on CI pipelines.

Securing Artisan in shared hosting

On shared hosts like Hostinger, restrict Artisan access to the public directory by setting APP_DEBUG=false and using .htaccess rules. For Windows, avoid Pail and use the built‑in log tailing.

Common Pitfalls & Troubleshooting

Dev command hangs on Ubuntu

Ubuntu users may encounter a hang if pcntl_fork is disabled. Enable the extension in php.ini or install the php-pcntl package.

Queue worker errors with PHP 8.2

Certain queue drivers emit deprecation warnings. Update queue:listen --tries=1 --timeout=0 to use the new --retry syntax in Laravel 13.25.

Missing Pail logs in local

Verify that php artisan pail --timeout=0 is registered in DevCommands. If not, add DevCommands::artisan('pail', 'logs')->blue();

Resolving 'artisan dev:list' errors

Ensure that the DevCommands service provider is registered in config/app.php. If the provider fails, Artisan will not display the registered processes.

Who Should Use Laravel Artisan? Persona Table