Beyond the News
Sign in
Web DevelopmentFrameworksDeveloper Tools Active dossier

Laravel Herd 2 brings coding agents, isolated database workspaces and deployment into local PHP development

Herd 2 adds visual coding-agent control, copy-on-write app and optional database clones, and Laravel Cloud deployment. Parallel agents can work with less shared-state collision, but production changes still need review.

Reviewed and published by Lars Jansen Updated 3 min read
Comment
First published

Key details

  1. Announced 5 November 2026.
  2. Herd Studio combines CLI coding agents and live previews.
  3. Workspaces can clone app state and databases.
  4. Built-in deployment to Laravel Cloud.
  5. Optional AI features and some Herd Pro-only context features.

What builders should take away

  1. Use separate local workspaces for parallel agents.
  2. Clone development databases where mutable state matters.
  3. Review permissions, migrations and deployment credentials.
  4. Check Herd Pro feature boundaries and supported agent compatibility.

What changed

On November 5, 2026, Laravel introduced Herd 2 with Herd Studio, visual annotations for existing CLI coding agents, live app previews, copy-on-write workspaces with optional database clones and a path to commit, push and deploy to Laravel Cloud. AI functions can be switched off.

Why it matters

Parallel agents sharing files and development databases risk conflicting edits and state. Independent workspaces and database copies improve workflow separation, while visual UI selection reduces ambiguity. Deployment remains a separate trust boundary and requires review.

Visual agent workflow

Herd Studio presents an app preview beside a developer-selected CLI agent, supporting pointing and annotations. Laravel says Claude Code, Codex, OpenCode and Cursor can be used; Herd does not provide its own model. Laravel Boost adds project context, with additional runtime context through Herd Pro.

Parallel local workspaces

Copy-on-write workspaces have separate local domains and may clone databases. They go beyond a plain Git worktree but do not automatically sandbox an agent from all host resources or secrets.

Deployment and review

The interface can commit, push and deploy to Laravel Cloud. Developers must still check generated changes, migrations, secrets and rollback readiness before production.

Evidence limits

The first-party announcement establishes available features on macOS and Windows, not independent reliability or security testing. Subscription and database compatibility boundaries need validation.

What to watch next

  • Independent workspace and database cloning tests.
  • Deployment failure handling and rollback guidance.
  • Herd Pro pricing and agent integration changes.

Still unclear

  • No independent hands-on testing established.
  • Vendor adoption claims not independently reproduced.
  • Exact security isolation guarantees are not established.

Sources

Direct reading behind this dossier.

2 sources
Laravel Herd 2
Laravel News secondary

Ecosystem radar and release context.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment
Continue reading
Artificial Intelligence

Laravel is replacing issue-first bug reports with AI-assisted pull requests across most packages

The change moves maintenance work earlier in the contribution funnel: instead of filing a report and waiting for a maintainer to reproduce it, package users are being asked to arrive with an executable patch candidate. It is a real workflow experiment, but Otwell's prediction that this becomes the norm should remain a founder/maintainer view rather than an industry fact.