Grove Review (2026): Pricing, Features & Honest Verdict

Grove is a macOS script runner with a built-in MCP server, so you and your coding agent drive the same terminal processes instead of two copies. It costs $5 once, with a three-day trial and no account. Best for: developers whose agents keep starting a second dev server. Price: $5 one-time (free plan: no, 3-day trial). Rating: 7.5/10.

What is Grove?

Grove launched on Product Hunt on 3 September 2026 and finished thirteenth with 98 upvotes. It solves an irritating and specific problem: your coding agent runs npm run dev in its own shell, you already have one running, and now there are two servers fighting over a port and neither of you can see the other’s logs. Grove makes one process list that both of you control. It runs the scripts, the menu bar shows them, and the CLI and MCP server drive the same running app through a local unix socket.

It comes from Publish Studio, which describes itself as an independent product studio, with Rakesh Potnuru as the maker on the launch. The app is at version 0.3.1 and weighs 8 MB. That is small for a macOS app in 2026 and it shows in the positioning: Grove is not trying to be your terminal, your editor or your agent. It runs project scripts and makes them visible to two parties at once. We found the scope discipline more convincing than the marketing on most tools three times its price.

What are Grove’s key features?

It reads the project you already have

No config file, no list to maintain. Grove follows workspace globs and finds every supported manifest: package.json, deno.json, pyproject.toml, Cargo.toml, go.mod, Makefile and an optional .grove/scripts.json. It keeps packages from different ecosystems separate, so a monorepo with a Rust crate and three Node packages does not collapse into one flat list. The site’s example is one monorepo, seven packages and twenty-five scripts discovered with nothing configured, which is the right benchmark for this kind of tool.

Four live terminals, and they behave like terminals

You can put up to four running scripts side by side. Every script runs on a pseudo-terminal, so colours, progress bars, prompts and signals work the way they do in your shell rather than the way they do in an IDE’s output pane. Ports become clickable links, failures stay visible until you acknowledge them, and stopping a script stops its whole process group, which kills the orphaned dev server that is still holding port 3000. Grove resolves your interactive shell once and reuses it, so version managers work without paying their startup cost on every run.

An MCP server and CLI that drive the same processes you see

This is the reason Grove exists. The CLI and the built-in MCP server do not spawn their own processes: they control the running Grove app over a local unix socket. When your agent starts the dev server, it appears in your menu bar with the same logs, the same port and the same stop button. The tool surface is small and well chosen: grove_list_scripts, grove_run_script for things that finish, grove_start_script for things that keep running and returns once a URL is up, grove_get_logs with a cursor so the agent reads only new output, grove_status and grove_stop_script.

Explain, which summarises a failed log on device

Press Explain on a failed run and Apple’s on-device model summarises the tail of the log instead of making you read the last two hundred lines. Grove strips anything shaped like a token or a password before the model sees it, and nothing is uploaded. As a design decision this is right: log tails are exactly the wrong thing to ship to a cloud model, and a local summary of why the tests exited 1 is worth more than a remote one. There is a compatibility problem with it, covered below.

Does Grove’s Explain feature work on every Mac it advertises?

Probably not, and the site does not say so. Grove states its requirement as macOS 15 or later on Apple Silicon and Intel. That figure appears three times: under the download button, under the price, and in the page’s structured data, where operatingSystem is set to “macOS 15+”.

Apple’s on-device model that third-party apps can call is the Foundation Models framework, and it requires macOS 26 on a Mac with Apple Intelligence. No Intel Mac has Apple Intelligence. So the stated compatibility range and the Explain feature cannot both hold across the whole range: anyone on macOS 15, and everyone on an Intel Mac regardless of version, is buying an app whose headline AI feature will not run. The rest of Grove works fine on those machines, and at $5 nobody is being materially harmed. But a one-line caveat next to the Explain screenshot would cost nothing, and its absence is the clearest gap on an otherwise careful page.

A smaller version of the same carelessness sits in the onboarding document Grove tells your agent to read. It links a reinstall URL at github.com/RakeshPotnuru/grove, and that repository does not exist: the API returns 404 and the download link 404s with it. The working repository is grove-releases, which the homepage links correctly. So the document that exists to unstick a broken install contains a broken link.

How much does Grove cost?

Grove costs $5, once. Not per year, not per seat. That buys the app, the CLI and the built-in MCP server, use on up to three of your own Macs, and automatic updates that are signed and notarized. You can download it and use everything free for three days with no card and no account, then buy a licence through Dodo Payments if you keep it. The structured data on the page confirms the same figure, listing a single offer at 5 USD.

There is no free tier after the trial and no subscription at all, which in this category is close to unique. Warp’s paid individual tier is $20 per month, which is Grove’s lifetime price every ten days. Conductor’s Pro plan is $50 per month. Even allowing that both of those do considerably more, the comparison tells you what Grove is: a small paid utility priced like a small paid utility, from a studio that has decided not to run a billing relationship with you.

How much traction does Grove have?

Very little yet, and the numbers are public. The releases repository was created on 2 September 2026, two days before we looked, and carries zero stars. Across its three releases, v0.2.0, v0.3.0 and v0.3.1, the .dmg has been downloaded 32 times in total: fourteen, ten and eight. Those are launch-week figures rather than a verdict on the product, but they are the figures.

The honest counterpoint to a $5 one-time price is that it funds roughly nothing, so the maintenance question is real. A solo maker shipping three releases in three days is a good sign about pace and a weak one about durability. Anyone thinking about depending on Grove in a daily workflow should price in that the project is days old rather than months, and that there is no subscription revenue underwriting the next version.

Who is Grove best for?

Use Grove if you work in a monorepo with more scripts than you can remember and you have started letting a coding agent run them. The specific moment it pays for itself is when the agent starts a dev server, you cannot find it, and you spend four minutes hunting the terminal that is still listening on a port. It also suits anyone who wants agent process control without adopting a whole new terminal or a cloud sandbox, since Grove sits alongside the tools you already use rather than replacing any of them.

Skip Grove if you are not on macOS, because there is no other build and none is promised. Skip it if you bought it for Explain and you are on an Intel Mac or macOS 15, for the reason above. And skip it if you need a tool with a track record: a two-day-old repository with 32 downloads and a solo maker behind it is a reasonable $5 bet and an unreasonable dependency for a team of ten. Read the onboarding document before you buy, though, because it is the most quietly honest page on the site.

That document deserves the credit. It tells you plainly that making the MCP tools reachable will not make your agent use them, because tool descriptions are advisory and a strong prior says “start the dev server” means running a shell command. Then it hands you the exact markdown rule to paste into AGENTS.md or your global instructions file so the preference sticks. Most MCP products pretend this problem does not exist. Grove documents it and ships the fix.

Best Grove alternatives

Warp is the obvious upgrade path if you want agents and terminal in one product. The free plan is real, the paid individual tier is $20 per month, a high-usage tier runs $200 per month, and Business is $50 per user per month. It replaces your terminal entirely and bundles its own agent, so it does far more than Grove and asks you to change far more. It does not give an external agent a socket into your existing process list, which is the one thing Grove is for.

Conductor runs a fleet of coding agents in cloud sandboxes on isolated microVMs, free to start, $50 per month for Pro and $60 for Teams. It is the right tool if your problem is running many agents in parallel with pre-installed repos. It is the wrong tool if your problem is that one agent and one human keep starting the same dev server twice on one laptop.

mprocs and overmind are the free open-source answer. Both run multiple processes in one terminal view with real process management, both cost nothing, and both have been around long enough to trust. Neither exposes an MCP server, so your agent cannot see or control what they are running, which is the entire reason Grove charges $5.

Final verdict: is Grove worth it?

Yes, at $5, for the audience it is aimed at. Grove picks one narrow problem, solves it with real pseudo-terminals and proper process-group handling rather than a wrapper that leaks orphaned servers, and exposes it to your agent through a socket into the same app you are looking at. Discovery works from the manifests you already have. The tool surface is small and correctly split between commands that finish and commands that keep running. The onboarding document is more honest about the limits of MCP than most vendors’ entire documentation sets. And the price removes the usual objection entirely.

The gaps are all around the edges rather than in the product. The stated macOS 15 and Intel compatibility cannot be true for the Explain feature, and the page carries no caveat. The onboarding document links a repository that does not exist. The project is two days old with 32 downloads and one person behind it. Buy Grove if the duplicate dev server is a daily annoyance, because five dollars against that annoyance is an easy trade. Do not build a team workflow on it yet, and do not buy it for the on-device summaries unless you are on macOS 26 with Apple Intelligence.