Share one Obsidian-style memory across Grok Bot, Codex and Claude over Tailscale
A builder used Grok Bot's new Tailscale plugin to open his Obsidian-style second brain on his Mac mini to his bots. Codex, Claude and Grok Bot now read the same memory, and rules and permissions set in one place apply to all of them.
Source
@207_studio on X · 2026-10-17
Written in our own words. Credit to the original author. Link checked 2026-10-22.
What they did
A builder used Grok Bot's new Tailscale plugin to open his Obsidian-style second brain on his Mac mini to his bots. Codex, Claude and Grok Bot now read the same memory, and rules and permissions set in one place apply to all of them.
Result (as claimed)
One memory and one set of rules for every agent.
Tools they used
Cost: Grok Bot: from $30/mo; OpenAI Codex: free plan, paid from $8/mo.
Set it up
Define the job
Say exactly what you want done and what the agent may and may not do on your behalf.
Share only what is needed
Give Grok Bot the minimum files or access required. Avoid sharing passwords in chat when a safer login flow exists.
Review the plan
Ask the agent to show its plan or draft before it acts, and approve each step that has real consequences.
Check the result
Confirm the outcome yourself (order placed, request sent, document understood) and keep a record.
Copy the full setup prompt
Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.
You are helping me set up this AI use case end to end in Claude Code. Goal: Share one Obsidian-style memory across Grok Bot, Codex and Claude over Tailscale What the original author did: A builder used Grok Bot's new Tailscale plugin to open his Obsidian-style second brain on his Mac mini to his bots. Codex, Claude and Grok Bot now read the same memory, and rules and permissions set in one place apply to all of them. Reported result (as claimed by the author): One memory and one set of rules for every agent. Source: https://x.com/207_studio/status/2111292440053465482 Tools they used: Grok Bot, OpenAI Codex, Claude, Tailscale, Obsidian Category: Personal & life Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Codex. Goal: Share one Obsidian-style memory across Grok Bot, Codex and Claude over Tailscale What the original author did: A builder used Grok Bot's new Tailscale plugin to open his Obsidian-style second brain on his Mac mini to his bots. Codex, Claude and Grok Bot now read the same memory, and rules and permissions set in one place apply to all of them. Reported result (as claimed by the author): One memory and one set of rules for every agent. Source: https://x.com/207_studio/status/2111292440053465482 Tools they used: Grok Bot, OpenAI Codex, Claude, Tailscale, Obsidian Category: Personal & life Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Grok Bot. Goal: Share one Obsidian-style memory across Grok Bot, Codex and Claude over Tailscale What the original author did: A builder used Grok Bot's new Tailscale plugin to open his Obsidian-style second brain on his Mac mini to his bots. Codex, Claude and Grok Bot now read the same memory, and rules and permissions set in one place apply to all of them. Reported result (as claimed by the author): One memory and one set of rules for every agent. Source: https://x.com/207_studio/status/2111292440053465482 Tools they used: Grok Bot, OpenAI Codex, Claude, Tailscale, Obsidian Category: Personal & life Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
The Daily 5
Get five new use cases tomorrow morning
Free. Real sources. Unsubscribe any time.
Guides for this use case
How to build an AI second brain and personal wiki · How to self-host AI agents on a Raspberry Pi, Mac mini or homelab · How to use AI agents with Obsidian and your notes · How to set up Grok Bot agents for real work
Related use cases
Use one Obsidian vault as shared memory for eight AI agents
Claude Code, Codex, Grok Bot and five more agents share one Obsidian vault as memory. Every night an agent fixes outdated facts and links loose notes.
Use Grok Bot with your Obsidian vault instead of Notion
A builder uses Grok Bot every day with Obsidian, where it operates on his vaults through the miyo MCP, keeping data ownership and file-over-app.
Build a Karpathy-style second brain in one folder on Grok Bot's computer
Following Andrej Karpathy's second-brain idea, a user gives Grok Bot one folder on its cloud computer and feeds it notes, links and documents so it maintains an organized knowledge base.
Sync your Obsidian vault through GitHub so Grok Bot works as chief of staff
Put the vault in a private GitHub repo so the bot can pull and push it, and keep a map note so it knows where everything lives; the bot then knows your projects without re-explaining.