To run parallel Claude Code agents on one Laravel repository without making them share a database or local site, give each Git worktree its own SQLite file and Herd site. Baptiste Bouillot’s Orca setup and archive scripts automate that lifecycle: setup prepares per-worktree resources, and archive attempts to remove them before the worktree is deleted. This is one author’s implementation, not a universal Orca or Laravel recipe.
Why isolate more than the Git branch?
A Git worktree gives an agent its own working directory and branch. But separate files alone do not isolate application state: agents can still interfere if they use the same database, local domain, or service port. Bouillot’s design addresses those shared resources by assigning each worktree a separate SQLite database file and Herd site, and by deriving a Reverb port when the project uses Laravel Reverb.
As an Amazon Associate I earn from qualifying purchases.
The convention is deliberately narrow: one SQLite file and one Herd site per worktree. It is a design choice described by the author, not a measured comparison against other approaches.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What the setup script does
The setup script prepares the worktree to run as a distinct local Laravel environment. It uses Orca-provided context where available and inspects project files to choose appropriate tooling.
#1 Best Overall
- Find the main checkout and configure the environment. The script uses
ORCA_ROOT_PATHwhen set; otherwise, it derives the main checkout path through Git. It copies the main checkout’s.envwhen present, or falls back to.env.example, then exports the loaded values for later commands. - Derive a worktree-specific site name. It uses
ORCA_WORKSPACE_NAMEor the current Git branch, sanitizes the value for a local site name, and shortens long names with a checksum suffix. The author says the length limit is intended to fit certificate common-name constraints. - Point Laravel at isolated local resources. The script sets
DB_CONNECTION=sqlite, usesdatabase/database.sqlitefor the database, setsAPP_URLto the derived HTTPS Herd domain, and changesMAIL_MAILERtolog. - Assign a Reverb port when applicable. If the project uses Laravel Reverb, the script derives a stable port from the site name and writes it to several environment keys. This is the author’s collision-avoidance approach; no collision-rate measurements are reported.
- Prepare the local site and project dependencies. It links and secures the Herd site, attempts to isolate the PHP version parsed from
composer.json, creates a fresh SQLite file, installs Composer dependencies, clears Laravel configuration, generates an application key, and runs migrations and seeds. - Handle optional project files and frontend tooling. The described script can link storage, copy
.mcp.jsonfrom the main checkout, conditionally handle private Composer authentication, and build the frontend using the package manager indicated by the project’s lockfile.
Secrets need a deliberate policy
Copying the main checkout’s .env is convenient, but Bouillot notes that it contains real secrets and API keys. A worktree is a separate directory, not automatically a separate trust boundary: any agent or process with access to that file may be able to use its credentials. Before adopting this pattern, decide which credentials an agent needs, whether development-only credentials can be supplied instead, and how copied environment files are protected and removed.
What the archive script removes—and what it can miss
The archive script reconstructs the worktree’s site name and checks for an empty workspace slug. It then attempts to unsecure, unisolate, and unlink the Herd site, deletes the worktree’s SQLite file, and restarts Herd.
Cleanup commands are best-effort, using || true so an individual failure does not prevent worktree deletion. That favors progress over guaranteed cleanup: if a command fails, Herd configuration or another local resource may remain. A practical workflow should provide a way to notice and remove leftovers rather than assuming that worktree deletion proves every resource was cleaned up.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Reuse the scripts across repositories
Instead of maintaining a full copy of each script in every Laravel project, Bouillot stores the shared implementations in ~/.scripts/laravel/. Each repository has short shim scripts that invoke the shared setup or archive script, and the repository’s Orca settings point to those shims. The arrangement centralizes changes while retaining a per-repository entry point.
Rank #3
When adapting it, check that the shim resolves the shared script for the user and environment running Orca, and that the scripts handle repositories with different PHP versions, lockfiles, optional services, or credential requirements. The author describes parsing PHP from composer.json and selecting frontend tooling from lockfiles, but the article does not report a compatibility matrix or test results across projects.
What the article does—and does not—establish
Baptiste Bouillot’s DEV Community article, published July 28, 2026, presents a first-person implementation for parallel Claude Code agents working on Laravel with Orca. It describes the resource-isolation convention and the scripts’ intended behavior; it does not provide benchmarks, a success rate, measured cost savings, or evidence that the approach fits every Laravel setup. Treat claims such as “zero manual setup” as qualitative framing rather than a measured result.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
