Grove
Give the agent eyes into your Grove local development environment — daemon state, PHP/Node runtimes, services, sites, logs, and
.envsync checks.
@elyracode/grove reads Grove's own files directly (config, service state, pid files, logs), so the agent understands your local environment without shelling out. Grove has no CLI — it is driven by the groved daemon and a config.toml — and this extension speaks to it natively.
Install
elyra install npm:@elyracode/grove
When a project is served by Grove (registered in Grove's config or under a parked path), Elyra detects it at startup and in /init output and offers to install this extension — skipped if it is already installed.
Tools
| Tool | Description |
|---|---|
grove_status |
Daemon state, installed PHP/Node runtimes (and which php-fpm is running), services with ports, TLS/domain settings, and which Grove site the current project maps to |
grove_sites |
All registered sites with domains, per-site PHP/Node overrides and TLS, plus parked paths |
grove_logs |
Recent entries from MySQL, Redis, php-fpm, per-site dev logs (vite, queue), and the project's Laravel log |
grove_env_sync |
Checks .env against the actual Grove environment: DB host/port, Redis host, and APP_URL against the site's real Grove domain and TLS setting |
Commands
| Command | Description |
|---|---|
/grove |
Grove dashboard — daemon, runtimes, services, current site |
/grove-logs |
Recent Grove logs for this project |
/grove-sync |
Check .env against the Grove environment |
Why use it
- Environment-aware answers — the agent knows which PHP/Node version and services actually back this site
- Diagnose "works on my machine" —
grove_env_synccatches.envdrift against Grove's real DB/Redis/domain - Faster debugging — pull the right logs (MySQL, Redis, php-fpm, Vite, queue, Laravel) without hunting for paths
- No shelling out — reads Grove's files directly, so it works even though Grove has no CLI