The terminal workspace manager for AI coding agents. Spin up a forest of isolated agent workspaces. Reach any of them asynchronously from your terminal, your browser, or another agent.
Grove in the terminal and the browser, and on your phone. One agent, one worktree, one window.
Grove runs several AI coding agents at once, each in its own isolated workspace: a dedicated git worktree on its own branch, paired with a tmux session and a window. The rule is one agent, one worktree, one window. Agents are productive in parallel but chaotic in the same folder, where they overwrite each other's files and collide on the same branch. Grove gives each one its own bench.
Every workspace is reachable asynchronously, from the terminal TUI, the CLI, the web dashboard on any device, or another agent over MCP. The same isolated-workspace primitive backs human and agent orchestration alike. Through all of it your git history stays yours: Grove never commits, never pushes, and never touches a remote branch.
|
Reach the whole fleet over your network. A composer starts a workspace from a prompt, and the live, repo-grouped grid shows every agent. Pair a device once; the daemon stays loopback. |
|
|
A split view shows the agent's transcript next to its live terminal. Read the conversation, send a follow-up, and answer the agent's structured questions inline. Watch the work happen at the same time. |
|
|
Grove ships an MCP server. Claude Code, Codex, OpenCode, and other orchestrators use its tools to create workspaces, dispatch tasks, send follow-ups, and steer the fleet. Your agents manage work at the scale of a whole project. |
|
|
Grove is a terminal program first. Run |
|
Also in the box:
- Branch-aware lifecycle. Create, pause, resume, respawn, and kill. Pause keeps the branch and drops the worktree. Kill deletes only branches Grove created, never remotes.
- Configuration cascade. A committed
.grove/config.jsonsets the team baseline. Six layers let each developer override locally without touching it. - Ticket providers. Branch-aware Gitea, GitHub, and Linear context, surfaced next to the workspace.
- Push notifications. Get pinged when an agent finishes a turn or needs you.
Grove needs git and tmux, and installs to your PATH as grove straight from the repo. With uv:
uv tool install "grove[daemon] @ git+https://github.com/bearlike/Grove"
cd path/to/your/repo
grove config init # scaffold .grove/config.json
grove # launch the TUI
uv tool upgrade grove # update laterNo uv? Use pipx install "grove[daemon] @ git+https://github.com/bearlike/Grove" or plain pip install --user. See Get Started for prerequisites and every install path.
🤖 Let an AI agent configure Grove for you
Configuration has a few layers and many knobs, so you do not have to write it by hand. Hand the prompt below to Claude Code, Codex, or any coding agent; it reads Grove's config skill and sets things up with you, verifying every field against your installed version.
Read https://raw.githubusercontent.com/bearlike/Grove/current/.claude/skills/configuring-grove/SKILL.md. It is the skill for configuring Grove, a terminal workspace manager for AI coding agents. Help me write my Grove user and project config, and verify every field against my installed version with `grove config schema --stdout`.
Full documentation lives at https://bearlike.github.io/Grove/latest/.
| Section | Covers |
|---|---|
| Get Started | Install, prerequisites, first run, verify. |
| Configure | Project setup, agents, init scripts, configuration reference. |
| Use | TUI tour, CLI, web dashboard, authentication, daily workflow. |
| Capabilities | Lifecycle, branch provenance, live activity, status semantics, configuration cascade. |
| Develop | Architecture, public API, engineering principles, contributing, design system. |
| Troubleshooting | Symptom → cause → fix for common failures. |
Bugs and feature requests on the issue tracker. For development setup, lint/test commands, and PR conventions, see the contributing guide and CLAUDE.md.
MIT © Krishnakanth Alagiri.