Grove 1.11.0: finding the one you were working on
Grove 1.11.0 adds a ⌘K palette that knows which project you were just working on, a filter for the Sites list, and moves ElyraSQL to 1.12.0 with its security fixes by itself.
Grove 1.11.0 adds a ⌘K palette that knows which project you were just working on, a filter for the Sites list, and moves ElyraSQL to 1.12.0 with its security fixes by itself.
Grove 1.10 tells you which route got slower, bisects to the commit that broke a request, replays writes against the same data, and runs another branch beside yours — without touching your checkout.
Grove 1.9 puts idle databases to sleep until the first connection arrives, gives every git branch its own data, and fixes three places where Grove reported success for things that hadn't quite happened.
Grove 1.8 hands socket binding to launchd and systemd, so the daemon that serves your local sites has never been root for a single instruction — plus a doctor that re-checks the invariants and a regression test for the CA name constraint.
Grove 1.7.0 adds one thing — ElyraSQL as a bundled, supervised service alongside PostgreSQL, MySQL and Redis. Installing it turned up a connection bug that had made a year-old documentation claim about Rust's sqlx false, and fixing that is most of this release.
Grove 1.6.0 stops reporting what it meant to do and starts reporting what happened: honest status and doctor, HTTP/2, HTTPS redirects, WebSocket passthrough, atomic state writes, orphan reaping — and Linux, in beta.
Laravel 13.16 shipped php artisan dev, and Grove's hardcoded two-process dev session became a limitation. Grove 1.3.0 reads dev:list from your app instead of guessing — plus a pre-existing orphaned-process bug that testing dragged into the light.
Grove 1.2.1 makes sandboxed writes legible: every agent-run migration or SQL statement now comes back with its blast radius — the SQL it ran, the mail it sent, and the metrics — so keeping or rolling back isn't a leap of faith.
Grove 1.1 turns grove mcp from a read-only window into a workshop: sandboxed writes with automatic rollback, a per-request causal chain linking requests to SQL and mail, and one-click 'explain this error' bundles. No app instrumentation required.
Grove 1.0 ships grove mcp — a read-only, local-only Model Context Protocol server that hands your AI assistant the context Grove already had: sites, requests, webhooks, logs, and each project's database. No copy-paste, no per-project setup.