Grove reads your code to plan better and to check what shipped. It never changes your code. This article explains what Grove can access, and how to control it.
Only workspace admins can connect, change, or disconnect GitHub. They do it in Settings › GitHub.
What the Grove GitHub app can access
GitHub permission | Access | Why Grove needs it |
Contents | Read | To read your code. |
Metadata | Read | To list your repositories. |
Commit statuses | Read | To see the status of your commits. |
Pull requests | Read | To link pull requests to projects, and check them when they merge. |
Issues | Read and write | To create or comment on GitHub issues, when someone asks Grove to. |
Grove has no write access to your code. It can't push, commit, or merge.
Which repositories
Grove reads only the repositories you pick when you connect GitHub. To change them, click Manage on GitHub in Settings › GitHub.
Pick only the repositories you want Grove to see. Grove's access token covers the whole GitHub app installation, so limit the installation to those repositories in GitHub.
Where Grove reads your code
Each workspace has its own private sandbox: a separate, isolated computer in the cloud.
Grove keeps a read-only copy of your picked repositories in that sandbox. It updates the copy as your code changes.
When you remove a repository, Grove deletes its copy the next time it updates.
When the sandbox isn't in use, it pauses.
How Grove reads it
Grove's agent can only read files and run read-only git commands, such as viewing history. It can't commit, push, merge, pull, or check out branches.
Grove gets a short-lived GitHub token, about one hour long, each time it needs one. Grove's servers create it. Grove doesn't keep long-lived secrets in the sandbox.
Web research and AI model calls go through Grove's servers. Their keys aren't stored in the sandbox.
What Grove does with your code
While planning: Grove searches your code to see what already exists, how big a change looks, and what it touches. It tells your product lead in plain terms. See What Grove knows about your product.
For mockups: Grove copies your product's look from your code, or uses your component kit. See Set up a component kit for realistic mockups.
When work ships: Grove reads the merged code to check each outcome. See How Grove checks what shipped.
Disconnect GitHub
Go to Settings › GitHub.
Click Disconnect.
Type your GitHub organization's name to confirm.
Grove stops reading your repositories, and deletes its copies. The Grove app stays installed on GitHub. To remove it there too, click Uninstall on GitHub.
If the connection breaks, the page shows Needs reconnection. Click Reconnect on GitHub.