Share one Obsidian memory across Grok Bot and other coding agents
Users report connecting Grok Bot and other coding agents to the same Obsidian vault, so they all read the same notes and rules instead of starting from scratch.
Last verified: Oct 17, 2026
The problem
Each coding agent you use keeps its own memory, so you explain the same rules over and over.
How the bot does it
Users report:
- @207_studio says he uses Codex, Claude, and Grok Bot together, and now they all read the same memory. He connects his bot over a Tailscale plugin to an Obsidian vault on a Mac mini.
- @joeleboube points to an open-source obsidian-second-brain project.
- Anything in the shared vault is visible to every agent, so keep secrets and passwords out of it.
Setup steps
- 1Pick one Obsidian vault folder for shared notes and rules.
- 2Connect each agent to it. One user uses a Tailscale plugin to reach a Mac mini.
- 3Agree on a simple note format: date, agent, what changed.
- 4Keep passwords and secrets out of the vault.
Example prompt
Before each task, read the notes in [vault folder] for our project rules and recent decisions. When you finish, add a short dated note of what you did and anything other agents should know. Don't delete or rewrite other notes.
The result
Every agent works from the same notes and rules. These are users' own setups.
Results are the user's own claim. We haven't checked them.
Sources
Want new ones in your inbox?
Pick what you're into. We'll send the best new prompts and templates, plus the weekly robot show.
Related prompts
Keep your help center in sync with code changes
xAI's support post says its bot reviews code changes and suggests matching updates to the help center, so articles don't drift out of date.
Each day, review merged changes in [repo]. List any help center articles that are now out of date and draft the updates. Don't publish anything: I review and publish.
Look into a slowdown after a release
The xAI docs show a bot looking into a slowdown after a release. It reads dashboards and traces and writes up the likely cause, keeping facts apart from guesses, before an engineer digs in.
Investigate the checkout latency increase since yesterday's release. Use our dashboards and traces, separate facts from hypotheses, and link the evidence for each. Don't change alerts or production settings. Change nothing.
Design a 3D-printable replacement part from a photo
Users report sending a photo and a short description of a broken part and getting a CAD design, an STL file, and slicer settings back. You need your own 3D printer.
Here's a photo of [broken part] and its measurements. Draft a CAD design, export an STL I can 3D print, and suggest slicer settings. Tell me what to check for fit and strength. Change nothing else.