A thread is a conversation about one point: a question, a problem, or a decision to make. Each thread belongs to a project or an initiative. Builders raise threads from their coding agents when the plan is unclear. You answer them in Grove.
Where threads live
Each project and initiative has a Threads page. Click Threads in its sidebar. The number next to it is how many threads are open.
Use the menu at the top of the page to show:
Waiting on you: threads where it's your turn.
Open: every open thread.
Closed: threads that are done.
All: every thread.
Sort the list by Recent activity, Waiting longest, Newest, or Opened by.
Start a thread
A thread can be about the whole project or initiative, one document, or one passage in a document.
On a passage: select the text in the document, then click Start a thread in the toolbar, or press Cmd+Shift+M (Ctrl+Shift+M on Windows).
On a document, project, or initiative: click Start a thread at the top of the page.
Type your point, and click Submit.
Some passages can't hold a thread, such as text inside a code block. Then the thread goes on the whole document, and Grove tells you so. If someone later edits a passage that has a thread, the thread shows Passage changed.
Reply and close
Click a thread to open it.
Type in Write a reply..., and send it.
When the point is settled, click Close thread. The last reply is the answer.
To open it again, click Reopen thread, or reply to it.
Posts can't be edited or deleted. To correct a point, add another reply.
Anyone in the workspace can start, reply to, close, and reopen threads.
Whose turn is it?
Each thread shows whose turn it is, from your point of view:
Label | What it means |
Your turn | You're in the thread, and someone else posted last. |
Waiting on a name | You posted last. |
Unanswered | You lead this project or initiative, and only the person who raised the thread has posted. |
Being discussed | You lead this project or initiative, others have replied, and you haven't. |
Threads that say Your turn or Unanswered also appear on your Queue.
Threads from builders
A builder's coding agent raises a thread when the plan doesn't answer something. Grove doesn't send a notification. Instead:
You see the thread on your Queue, and on the project's Threads page, as Unanswered.
A post written by a coding agent shows who it's for, such as "Claude (on behalf of Sam)."
When you reply, the builder's agent can read your answer. If the answer changes the plan, change the plan document too, so the next builder sees it.