Grove gives Claude Code experience from your work, across Slack, GitHub, Calendar, Notion, Linear, conversations, and more.
Real, dated posts from people who watched their knowledge base die.
"Humans abandon wikis because the maintenance burden grows faster than the value."
gist.github.com/karpathy/442a6bf5 →"My browsing history, emails, chat logs, calendar, Readwise and Zotero highlights, this should form the 'digital brain' automatically. Manual gardening never happened."
forum.obsidian.md/t/108834 →"Organizing my notes is taking longer than actually writing them."
forum.obsidian.md/t/108820 →"Every attempt, over decades, from pen and paper to Obsidian to Notion, has ended in a mess that becomes unusable."
forum.zettelkasten.de/discussion/3034 →"I quit Obsidian after trying for YEARS to become a zettelkasten guy. Finally threw my hands up in the air."
forum.obsidian.md/t/80353 →"That's how every wiki I've ever built eventually died, under the weight of its own bookkeeping."
aaronfulkerson.com/2026/04/12 →Grove organizes your work the way your brain does. Typed nodes, real relationships. It updates itself in the background, cleans itself when facts conflict, and asks when it can't decide. All you see is the Claude Code terminal.
The sources are what you do all day. Slack, GitHub, calendar, your notes, your Claude sessions. You stop being its data-entry clerk.
Every fact has a shape. Ask "who owns what" and get a typed answer back.
Every claim traces to where it came from. If it can't be sourced, it doesn't get said.
Every fact carries its dates. Roll the graph back; grove answers as of that day.
Local database, local embeddings. We've been running grove on our own work every day. Your work stays your work.
What people say in standups vs what they actually shipped in GitHub. Discrepancies surface.
Yes. We've been running it on our own work for months. We're not packaging it for everyone yet, we want your thoughts first.
Obsidian gives Claude a markdown vault to search across. Grove gives Claude a typed graph: nodes have shape (decision, person, blocker, project, event) and real relationships between them. Claude can ask "who decided what and what's blocking it" and get a structured answer back, not a fuzzy match across .md files.
Vector search returns text chunks. Grove returns typed entities. A decision has when, why, source. A blocker has owner, status. Ask "what's blocked and by who" and get an answer, vector search can't.
Local-first. Everything runs on your machine: local database, local embeddings. Grove only reads what you connect (Slack, GitHub, calendars). Nothing leaves your machine.
Grove uses your Claude Code conversations out of the box, that's the baseline. To get the full picture (decisions from meetings, blockers from Slack threads, work that landed in PRs) you connect your other sources: Slack, GitHub, calendar, Linear. The more grove can read, the better the answers. Without those, it still works, it just sees less.
X-Arc. We build tools we want to use ourselves, then ship the ones that work. We've been running grove on our own work every day. Now we're seeing if it should exist for anyone else.
We've been running grove on our own work for months. Once 15 Claude Code users want it, we ship it for everyone.