I built Grove because I kept losing track of project scripts across terminal tabs. Once I started working with coding agents, the problem got worse. An agent would start another dev server because it could not see the one I already had running.
Grove gives both of us control over the same processes.
Connect a folder and Grove finds scripts across Node, Deno, Python, Rust, Go, Make, and monorepos. Start them from the menu bar, CLI, or built-in MCP server. Every process has shared logs, detected ports, status, and a stop control that also terminates its children.
The scripts run in real pseudo-terminals, so colors, prompts, progress bars, signals, and shell environments work as expected.
Grove also integrates with Apple Intelligence. On a compatible Mac running macOS 26, you can press Explain after a script crashes. Grove removes anything shaped like a token or password before Apple's on-device model reads the end of the log and summarizes the failure.
I'd especially like feedback from developers using coding agents for local development. How are you handling shared dev servers and background processes today?
PH 用户
hello Rakesh, keeping tabs on everything running quietly in the background has worn me down more than I like to admit.
Having it all gathered in one calm spot would lift a real weight, and the part where my AI helper and I finally see the same thing is what stuck with me.
PH 用户
the shared-visibility problem is real and I've hit the exact same duplicate-dev-server thing. what happens when you and the agent both reach for the same process at the same moment though - say you restart it manually right as the agent sends a stop signal? is there any locking, or is it just "last command wins" and you sort out the mess after?
PH 用户
the agent booting a second dev server bcoz it cant see mine has happened to me more than once. built in MCP server is why im looking. nice launch rakesh
I built Grove because I kept losing track of project scripts across terminal tabs. Once I started working with coding agents, the problem got worse. An agent would start another dev server because it could not see the one I already had running.
Grove gives both of us control over the same processes.
Connect a folder and Grove finds scripts across Node, Deno, Python, Rust, Go, Make, and monorepos. Start them from the menu bar, CLI, or built-in MCP server. Every process has shared logs, detected ports, status, and a stop control that also terminates its children.
The scripts run in real pseudo-terminals, so colors, prompts, progress bars, signals, and shell environments work as expected.
Grove also integrates with Apple Intelligence. On a compatible Mac running macOS 26, you can press Explain after a script crashes. Grove removes anything shaped like a token or password before Apple's on-device model reads the end of the log and summarizes the failure.
I'd especially like feedback from developers using coding agents for local development. How are you handling shared dev servers and background processes today?
Having it all gathered in one calm spot would lift a real weight, and the part where my AI helper and I finally see the same thing is what stuck with me.