Grove

Product Introduction

1. Definition: Grove is an AI-native macOS script runner and terminal process manager. It is a developer tool that functions as a unified control plane for terminal scripts, integrating a native macOS menu bar application, a Command Line Interface (CLI), and a built-in Model Context Protocol (MCP) server.
2. Core Value Proposition: Grove exists to unify and streamline the development workflow by allowing both the human developer and their AI coding assistant (agent) to observe and control the same live terminal processes. Its primary value is eliminating context switching and process duplication between the user's local terminal and their AI agent's environment.

Main Features

1. Zero-Configuration Script Discovery: Grove automatically scans connected project folders for supported manifest files and scripts without requiring a dedicated configuration file. It parses package.json, pyproject.toml, Cargo.toml, deno.json, go.mod, Makefile, and optional .grove/scripts.json files, intelligently separating scripts by their ecosystem (e.g., Node.js, Python, Rust).
2. Multi-Terminal Dashboard with Live Logs: The application provides a visual dashboard where users can run and monitor up to four terminal processes simultaneously in real-time. Logs retain their original ANSI color formatting, detected localhost ports are automatically converted into clickable hyperlinks, and failed process states are persistently highlighted until acknowledged.
3. On-Device Log Explanation with Privacy: Integrated directly with Apple's on-device AI models, Grove can generate concise summaries of terminal output, specifically focusing on error causes. Before processing, it performs a privacy scrub, removing strings that resemble secrets, API tokens, or passwords, ensuring sensitive data never leaves the local machine.
4. MCP Server for AI Agent Integration: Grove runs a local Model Context Protocol (MCP) server, enabling AI coding agents (like those in Cursor or Claude Desktop) to interact with the same terminal processes visible in the user's menu bar. Communication occurs over a local Unix socket, allowing the agent to start, stop, and read logs from processes, creating a shared state.
5. Native Pseudo-Terminal (PTY) Execution: Unlike simple command spawners, Grove executes every script in a full pseudo-terminal (PTY), ensuring authentic terminal behavior. This guarantees correct handling of interactive prompts, progress bars, control sequences (like Ctrl+C for SIGINT), and shell signal propagation.
6. Process Group Management: Grove manages entire process groups (PGIDs). When a user or agent stops a script, Grove terminates the entire process tree, preventing orphaned child processes (like lingering dev servers or background workers) and cleaning up resources like network ports.
7. Persistent Shell Environment Caching: To maintain compatibility with shell version managers (e.g., nvm, rbenv, pyenv) without incurring startup latency, Grove resolves and caches the user's complete interactive shell environment once at launch, then reuses this environment for all subsequent script executions.

Problems Solved

1. Pain Point: Disconnected workflows between developers and AI assistants. Traditionally, an AI agent might spin up its own isolated process, invisible to the developer, leading to port conflicts, duplicated resource consumption, and an inability for the developer to inspect or debug the agent's work in real time.
2. Target Audience: macOS-based software engineers, full-stack developers, and DevOps practitioners working in polyglot or monorepo environments. It is particularly valuable for developers who regularly use AI pair-programming tools and need to integrate them into their local development loop.
3. Use Cases: A developer asks their AI agent to "start the dev server and run tests." With Grove, the agent starts the processes via the MCP server, and both the developer and the agent can see the same live logs. The developer can then visually identify a test failure in the dashboard, use the "Explain" feature to get a quick AI summary of the error, and then stop all related processes cleanly with one action.

Unique Advantages

1. Differentiation: Unlike traditional terminal multiplexers (tmux, screen) or process managers (PM2, Foreman), Grove is designed from the ground up for bidirectional human-AI collaboration. Unlike IDE-based terminals, it is project-agnostic and provides a persistent, centralized process management layer outside any single editor.
2. Key Innovation: The integration of a fully functional MCP server directly into a native desktop terminal manager is its core innovation. This transforms the AI agent from a passive code generator into an active participant that can operate within the developer's own, visible runtime environment, creating a truly shared workspace.

Frequently Asked Questions (FAQ)

1. Is Grove a replacement for my terminal or iTerm2? No, Grove is a complementary process manager and orchestration tool. You would still use your primary terminal (iTerm2, Warp, Terminal.app) for exploratory work and one-off commands. Grove is for managing long-running project scripts (dev servers, tests, builds) that you or your AI agent need to monitor and control centrally.
2. How does Grove handle environment variables and shell configurations? Grove launches a one-time instance of your default interactive shell (e.g., zsh, bash), loads all your profile/rc files to capture the complete environment (including those from tools like nvm or direnv), and caches this environment. All subsequent scripts run with this cached environment, ensuring compatibility without the overhead of sourcing your shell for every command.
3. Is my terminal log data sent to the cloud for the "Explain" feature? Absolutely not. The log explanation feature uses Apple's private, on-device AI models (like those powering system-wide features in macOS). Grove performs local sanitization to remove potential secrets before the log text is sent to the local model, ensuring complete data privacy.
4. Can I use Grove with any AI coding assistant? Grove works with any AI agent or IDE that supports the open Model Context Protocol (MCP). This includes popular platforms like Cursor, Claude Desktop, and any other tool that can connect to a local MCP server. You connect your agent to Grove's local socket endpoint.
5. What happens if I quit the Grove menu bar app? All processes managed by Grove are terminated, as they are children of its service. The Grove CLI and MCP server also become unavailable. Grove is designed as a persistent manager for active development sessions.