Ehsan Bagherzadegan
Back to articles
7 min read

Laravel Herd 2.0: Herd Studio, Workspaces, and Cloud Deploy

Laravel Herd 2.0 adds a browser-based AI development environment, copy-on-write workspaces for parallel feature work, and one-click deployment to Laravel Cloud — all running locally.

Laravel Herd 2.0 shipped on November 5, 2026, and it fundamentally changes how you interact with your local development environment. What started as a zero-config PHP server manager has grown into a full local development platform with AI agents, parallel workspaces, and one-click cloud deployment — all without leaving your machine.

Herd Studio: Agents Inside Your Browser

The headline feature is Herd Studio, a browser-based development environment that runs entirely on your local machine. It sits next to your .test sites and gives you an agent chat, code editor, terminal, logs, queue monitor, Tinker REPL, and a deploy button — all talking to the actual files on disk.

You don't need a separate AI subscription. Herd includes free models via opencode, and you can also connect Claude Code, Codex, OpenCode, Cursor, or any CLI agent you already use.

The entry point is an "Edit with Herd" badge that Herd automatically injects into every page of every .test site it serves. Click it and Studio opens for that specific site. You can also reach it at https://my-app.test/herd-studio, run herd studio from your project directory, or open it from the new Applications window.

Inside Studio you get:

  • Agent chat — conversational coding with full repository context
  • Code editor — file browser with PHP autocomplete, search, and diff review
  • Changes panel — reviews agent edits, auto-initializes git if needed
  • Terminal — project-scoped shell, one keystroke away
  • Dev server — watches php artisan dev (Laravel 13.25+) or Vite processes
  • Logs, Queue, Tinker, Insights — the usual Herd tools, now in-browser
  • Expose & Deploy — share a public URL or push to Laravel Cloud

This isn't a remote environment. The agent reads and writes your actual files. The terminal runs on your machine. The dev server serves your actual code. When the agent makes a change, you see it instantly in the live preview pane.

Workspaces: Parallel Development Without the Friction

Herd 2.0 introduces workspaces — isolated copies of a site on their own git branch and subdomain. Run herd workspace feature-auth inside ~/Herd/shop and you get feature-auth.shop.test served instantly, on its own branch, with its own database if you want.

On macOS, workspaces use APFS copy-on-write clones. They take zero extra disk space until you modify files. Windows falls back to full copies. Herd also detects existing git worktrees and can serve them as workspaces.

The database strategy is configurable per workspace:

Mode Behavior
shared (default) Uses the parent database — fast, but migrations affect all workspaces
clone Creates a new database and copies all data via mysqldump/pg_dump/file copy
empty Creates a fresh database and runs php artisan migrate
# Create a workspace with a cloned database
herd workspace feature-auth --database=clone

# List workspaces
herd workspaces

# Switch into a workspace directory
herd workspace:switch feature-auth

# Open in browser
herd workspace:open feature-auth

# Merge back to parent branch
herd workspace:merge feature-auth

# Delete workspace (keeps the git branch)
herd workspace:delete feature-auth

Each workspace automatically updates its .env — APP_URL, SESSION_DOMAIN, DB_DATABASE, and related keys — so cookies and sessions work across the parent domain (.shop.test) without extra config.

This means you can spin up a workspace, hand it to an agent with a prompt, and come back to a completed feature on a clean branch. Or run three agents in parallel on three different workspaces. The parent site keeps running undisturbed.

Applications Window: From Prompt to Running App

The new Applications window (tray icon → Applications) is your dashboard for creating and managing sites. At the top, a composer lets you describe an application in plain English, pick a starter kit (Livewire, React, Vue, Svelte, or none), choose an AI model, and hit Build.

Herd scaffolds the Laravel app, starts an agent, and builds your idea in the background. You can close the window and later open Herd Studio to watch progress or take over.

For existing sites, the inspector pane has a "Build with AI" field. Enter a prompt, check Run in a new workspace, choose your database mode, and Herd creates the workspace, starts the agent, and opens Studio — all in one flow.

The window also lists all your workspaces per site with open/delete actions, so you can clean up without touching the CLI.

One-Click Deploy to Laravel Cloud

When a feature is ready, deploy it from Herd Studio or the Applications window. Herd detects Laravel Cloud projects by their GitHub origin remote, so your repo must be on GitHub with the Laravel Cloud GitHub App installed.

The deploy flow:

  1. Select the site → Deploy to Laravel Cloud
  2. If the app doesn't exist on Cloud yet, Herd creates it
  3. Herd runs the Laravel Cloud CLI and streams three stages:
    • Prepare — configuration and validation
    • Build — compiling assets, installing dependencies
    • Release — rolling out to production
  4. Click Show output for the full CLI log
  5. On success, Herd shows the live URL

This is the same pipeline you'd get running cloud deploy manually, but without leaving your local workflow. Forge deployments are also supported as an alternative.

What This Means for Your Daily Workflow

Herd 2.0 removes several context switches that used to be routine:

  • No more git checkout -b + php artisan migrate + new terminal tab to start a feature. One command or one click gives you a live URL on a clean branch with a migrated database.
  • No more copying code between editor and AI chat. The agent works in your actual repository with your actual runtime.
  • No more git push → wait for CI → check Cloud dashboard to verify a deploy. The deploy button is next to the code editor.
  • No more "which port is Vite on?" The dev server panel shows every process with its URL.

The mental model shifts from "manage servers and processes" to "describe what you want, review the result, ship it."

Gotchas and Limitations

  • Windows users don't get copy-on-write clones. Workspaces still work, but they consume disk space immediately.
  • Shared database mode is the default. If you run migrations in a workspace without --database=clone or --database=empty, they affect the parent site. Get in the habit of specifying the mode.
  • Cloud deploy requires a GitHub origin remote with Laravel Cloud app access. If your repo is on GitLab or Bitbucket, or the Cloud app isn't installed, the deploy button won't work.
  • Herd Studio requires a modern browser. It uses WebSockets for the live preview and agent communication.
  • Free opencode models are rate-limited. For heavy agent usage, connect your own provider (Anthropic, OpenAI, etc.) in Settings → AI.

When to Reach for Herd 2.0

If you already use Herd, upgrading is a no-brainer — you get Studio and workspaces for free. If you're on Valet, Sail, or a manual PHP setup, Herd 2.0 is worth a look if:

  • You want AI agents that can actually run and test your code locally
  • You frequently context-switch between features and want cleaner isolation
  • You deploy to Laravel Cloud and want a shorter path from "done" to "live"
  • You pair-program or hand off work to teammates and want a shareable, live environment

It's less compelling if you're happy with your current editor + terminal workflow, don't use AI coding agents, or deploy elsewhere.

A Concrete Example

Here's what a typical session looks like now:

# Start a new feature in a workspace with a clean database
cd ~/Herd/shop
herd workspace add-to-cart --database=empty

Herd creates add-to-cart.shop.test, checks out a new branch, creates a fresh database, runs migrations, and updates .env. Open the URL, click "Edit with Herd," and you're in Studio.

In the agent chat:

"Add a 'Add to Cart' button to the product card component. Use the existing Cart Livewire component. Write a Pest test for the button."

The agent finds the component, adds the button, wires the action, writes the test, runs it — you watch the terminal output in the Terminal panel. If it passes, click Deploy to Laravel Cloud in Studio. Three stages later, the feature is live.

No git commands. No manual migrations. No context switches. Just code, review, ship.

Sources