¶CLI reference

Every command speaks to the daemon over local IPC and accepts a global --json flag for machine-readable output.

grove <command> [args] [--json]

¶Lifecycle

¶Sites

¶Dev processes

Grove runs a site's long-running dev processes for you — typically the Vite dev server (HMR) and a queue worker, plus anything else the application declares — with the site's own Node/PHP. No artisan serve needed (Grove already serves). Output goes to the Logs panel (dev-<site>-*.log). In the GUI it's the ⚡ toggle per site.

On Laravel 13.16+, Grove asks the application what to run via php artisan dev:list --json --except-vendor, so processes you register with DevCommands are supervised too:

use Illuminate\Foundation\Console\DevCommands;

DevCommands::artisan('reverb:start', 'reverb')->orange();
DevCommands::register('stripe listen --forward-to '.config('app.url'))->green();

Two entries are deliberately skipped: server (Grove already serves the site over FPM on its .test domain) and logs (grove logs tails the app log already). Vendor-registered processes are excluded so an arbitrary Composer package can't start processes inside the daemon.

Each process writes to dev-<site>-<name>.log in Grove's log directory, listed by grove logs. php and the Node package manager are resolved to the versions the site pins, not whatever is on your PATH.

Grove falls back to a Vite dev server plus a queue worker for non-Laravel sites and Laravel versions without dev:list.

Run grove dev instead of php artisan dev, not alongside it. Both supervise the same processes, so running both gives you two Vite servers fighting over port 5173 and two queue workers competing for the same jobs. grove dev start warns when it sees a php artisan dev process running. The check can't tell which project that process belongs to, so it is a warning rather than an error.

¶Debugging (Xdebug)

See DEBUGGING.md. Grove's fully-static PHP can't load Xdebug — register a PHP that has it (grove php register).

¶PHP

¶Node.js

¶Services

¶Reproducible environments (grove.toml)

Commit a grove.toml to a project so a teammate can go from git clone to a running, identical environment in one command.

# grove.toml
name = "myapp"
php = "8.4"
node = "22"
secure = true
services = ["mysql", "redis"]
dev = true

¶Reproducible bundles

Package a whole project environment — grove.toml, .env, and its database — into one shareable file, and restore it with a single command. Reproducible dev environments without Docker; ideal for onboarding a teammate.

¶Team secrets (Grove Teams)

End-to-end encrypted .env sync for your team. Secrets are encrypted on your machine (age / X25519) to members' public keys; the backend only stores ciphertext. Requires an active Teams license (grove license activate).

The backend URL defaults to https://teams.elyracode.com (GROVE_TEAMS_SERVER overrides it).

¶License (Grove Pro / Teams)

Activate a purchased license to unlock Pro/Teams features. Verified offline (Ed25519) — no connection required. The free, open-source core is never gated.

Also available in the desktop app under Settings → License.

¶Request timeline

Grove proxies every *.test site, so it records a live, framework-agnostic log of recent requests — method, path, status, duration — with zero setup. Also shown in the desktop app's Requests panel.

¶Causal chain

With grove sql-capture on, Grove turns on MySQL's general query log and reads it back to build a per-request causal chain: expand a request in the desktop app's Requests panel (or via the MCP grove_request_chain tool / grove requests --json) to see the SQL it issued and the mail it sent within its time window, plus derived metrics (duration, query count). A toolbar toggle turns SQL capture on/off. Grove sits in front of every request and captures mail centrally, so this needs zero app instrumentation.

In the desktop app, click any request to see its headers and body, replay it, or copy it as a curl command, a .http file, or a Pest test — a framework-agnostic way to re-run a failed request (or turn it into a regression test) while you fix the code.

¶AI tools (MCP)

Expose your local environment to AI clients (Claude, Cursor) over the Model Context Protocol — read-only, local-only. See MCP.md for client setup.

¶Webhooks

Grove captures any request to /__grove/hooks/<bucket> on a site and answers 200 — a local webhook.site. Expose it publicly with grove share <site> and point Stripe, GitHub, etc. at https://<public-url>/__grove/hooks/<bucket>. Inspect each delivery and re-deliver it to your app while you fix the handler.

Also available as the Webhooks panel in the desktop app, where you can inspect payloads and copy any delivery as a curl/.http/Pest test.

¶Database snapshots

Looking to browse or edit data? That's the Database panel in the desktop app (auto-connects from each site's .env) — see DATABASE.md. The commands below are for point-in-time snapshots.

Point-in-time snapshots of Grove's bundled MySQL / PostgreSQL — snapshot before a risky migration and roll back in one command. Stored as SQL under $GROVE_HOME/snapshots/.

¶Toolchain on your PATH

Expose Grove's bundled php, composer, node, npm, npx and laravel, auto-switching to whatever version each project pins (grove isolate / grove node use) — so you can drop Herd/Valet entirely.

¶Docker / OrbStack

Running containers are discovered automatically and served as <name>.test with trusted HTTPS — no command needed. They appear in grove list with the proxy driver, and can be started/stopped from the GUI. Toggle with [general].docker. See DOCKER.md.

¶GUI-only tools

The desktop app's Tools panel adds actions without a CLI equivalent: Restart daemon, Migrate MySQL from Herd, Convert database (MySQL/PostgreSQL/SQLite), and the Xdebug toggle.

¶Mail

¶Logs

¶TLS / CA