grove

Quickstart

A five-minute tour: open a repo, spawn a task, review the agent's diff, leave a comment, get a reply.

1. Open a workspace

Launch Grove and pick a git repository as your workspace. Grove writes its metadata under <workspace>/.grove/ — this is gitignored automatically.

2. Read code

The center pane is a Monaco-based file viewer with tree-sitter syntax and LSP for every language Grove ships. Cmd+P opens the file palette; Cmd+Shift+F opens project search. You can edit code by hand whenever you want — Grove is just optimized for reading and reviewing, since most writing is done by agents.

3. Take notes

Markdown files open in a WYSIWYG editor with [[wikilinks]], backlinks, Mermaid, and live :grove-* panels. Write a note, link it to a function with [[fn:someFunction]], drop a task board into your daily log. See Markdown editor and Directives.

4. Spawn a task

Right-click anything in the workspace tree — a file, a folder, the repo root — and pick New task (or promote an existing notes folder). Creating a task is instant and nearly free: Grove makes a branch (task/<slug>-<hash>) off your base and a lazy worktree with no files in it yet.

Hover the task and start a chat with the agent of your choice — Claude Code, Codex, or opencode. The worktree materializes the moment the agent spawns (and your repo's setup script runs, so node_modules and .env are there too).

Tell the agent what to do. As it works, Grove polls the worktree's diff and updates the overlay live.

5. Review the diff

The Diff view renders the agent's changes inside the actual file, tinted in the task's color, with full surrounding context. Select lines and leave a comment. The comment is anchored to content, not a line number — it survives rewrites.

6. Get a reply

The agent has an MCP tool surface that lets it list pending comments, reply, and resolve them. Ask it in chat to address your comments — replies appear threaded in the Comments panel.

7. Ship it

The task's PR button opens GitHub's compare page for the branch; once the PR exists, the same button opens it, shows CI status, and can squash-merge it — see GitHub PR review. Or archive the task: uncommitted work is captured, the branch is kept, and you can revive it later exactly where you left off.

Where to go from here