Grove plans better when it knows your product. It draws on five sources: your workspace, your strategy, your code, the web, and the files you share. This article explains each one, and what Grove can't see or change.
Your workspace
Grove reads the initiatives, projects, documents, and threads in your workspace. It also knows which page you have open, so a question like "is this ready to build?" is about the work in front of you.
Grove writes only to the plan documents: Opportunity and Solution, Scope, each project's outcomes and Requirements, the Scratchpad, and the strategy documents. It never archives work or restores an old version without asking you first.
The documents carry the plan from one chat to the next. When a decision matters, make sure it's written into the plan.
Your strategy
Grove reads your four strategy documents (Target Personas, Product Vision, Product Strategy, and Competitive Landscape) whenever it plans. It uses them to check that a new idea fits your strategy, and it tells you when it doesn't.
When you mention something during planning that applies to your whole product, such as a new type of user or a competitor, Grove adds it to the right strategy document. It tells you when it does.
Your code
When an admin connects GitHub, Grove gets a read-only copy of the repositories you picked. Grove searches the code when it scopes a project, sizes a piece of work, or checks whether something already exists. It then tells you what it found in product terms: what exists, how big a change looks, and what it touches. You don't need to read code.
Grove can't change your code. The Grove GitHub app has no write access to your repositories. Depending on how your workspace is connected, Grove can create or comment on GitHub issues when you ask it to.
The web
When it helps, Grove searches the web, reads web pages, and researches companies. It does this for competitor research, market questions, or when you ask it to look something up. Grove names its sources, so you can check them.
When Grove sets up your strategy, it asks what it may look at before it researches anything.
Files you share
Attach files to a message with + in the chat: notes, research, customer feedback, PDFs, or images. Grove reads them as part of that conversation. See Chat with Grove for the file types and size limits.
What Grove can't see
Other workspaces, even ones you belong to.
Tools that aren't connected to Grove, such as your other apps, unless you paste or attach their content.
Repositories you didn't pick when you connected GitHub.
Related articles
Connect GitHub
How Grove uses your code: permissions, sandbox, read-only access


