Engineering
Grokbase: shared git repo of cited summaries from Notion, Drive, X
Agent memory scattered across chats does not compound.
What hurt
Sravan Jayanthi (@sravanjay) gave his Grok Bot agents Grokbase — a shared git repo of cited, theme-grouped summaries from Notion, Drive, and X. Weekly ingest, nightly chat summaries, one commit per run with rollback, and it reinforces the info back to him to amplify learning. Not affiliated with xAI.
What to install or create
Shared git memory. Cited summaries. Weekly ingest + nightly chat summary + single commit/rollback.
Bots
Grokbase curator
Weekly ingest + nightly summaries; one commit per run; rollback-ready.
Plugins
GitHub
Required
Notion
Optional
Files
Grokbase repo. Theme-grouped, cited summaries. One commit per ingest/summary run.
Routines
Weekly ingest. Weekly. Pull Notion/Drive/X into cited summaries.
Nightly chat summary. Nightly. Summarize chats into Grokbase; reinforce to you.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/sravanjay/status/2110152789980741834 (credit @sravanjay).
- 2Create a private git repo for Grokbase summaries.
- 3Tell a curator bot: weekly ingest from Notion/Drive/X into cited theme groups; nightly chat summary; one commit per run; keep rollback easy.
- 4Connect the sources it should read.
- 5Review one week's commits before widening sources.
Approval fence
Commits to the memory repo only. No production deploys from ingest.
What to tweak
Steal cited shared repo + one-commit-per-run. Memory you can roll back.
Source
Sravan Jayanthi @sravanjay · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.