Grove
One terminal for you and your AI agent
89 followers
One terminal for you and your AI agent
89 followers
Grove is an AI-native macOS script runner designed to unify your terminal experience with your AI coding agent. It allows both you and your agent to control the same terminal processes, streamlining development workflows. Upon connecting a folder, Grove automatically sets up a menu bar, CLI, and a MCP server to manage real terminal processes. You can start, inspect, and stop these processes seamlessly.
Free Options
Launch Team
Describe your app. Get clickable screens, flowcharts and mind maps.Free PRO account for life if you register before November 13
Promoted
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
@niveditha_patluri1 You got the point 💯. Thanks
Forgive me for oversimplifying but, any process that your agent starts goes thru this and you can see/manage them all in one place, correct? If yes then it's amazing
Feel free to ask anything!
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?
@galdayan No lock. Both commands go through the same actor, so there's no crash or corrupted state, but nothing tracks which command was chasing which process.
Most of the time that doesn't matter, since a duplicate stop just resends the same signal. The one bad case: if your restart already finished and a new process is up by the time the agent's stop message arrives, that stop kills the new one instead of doing nothing. It has no way to know the process underneath changed.
So it's not "last command wins" in a clean sense. It's "whichever command arrives last acts on whatever's running right now," and today there's no check for whether that's still the process it meant to touch.
@itsrakesh that stale-process case is the one that would actually bite someone in practice, not the duplicate-signal case. feels like the fix isn't even locking, just tagging each stop message with the pid or a generation counter it expects to kill, so a late stop can no-op instead of murdering whatever happens to be running now. curious if that's on your radar or if it's rare enough in practice not to bother yet
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.
@amine_aziz_alaoui Thanks Amine, that “worn me down more than I like to admit” feeling is exactly what pushed me to build this.