How to Build an AI Second Brain in Google Drive (So Every Chat Starts With Context)
This week's shortcut is the reason I never have to explain my own business to an AI twice.
If you use AI for real work, you know the tax I'm talking about. Every new chat starts from zero.
You re-explain your business. Your offers. Your rules. What you're working on right now. And half your session is gone before the actual work starts.
It gets worse if you use more than one AI tool, because whatever one tool "remembers" about you is locked inside that tool. Switch tools and you start over:
- Your context lives in a memory feature you can't read, edit, or export
- Your best decisions are scattered across old chats you'll never find again
- Every project update means re-briefing the AI like a new hire, every time
Losing context between AI chats was never a memory problem. It's an ownership problem.
Why I built my second brain in Google Drive instead of Obsidian
I kept hearing people talk about building a "second brain" in Obsidian. A folder of notes their AI reads for context.
I loved the idea. I did not love the tool.
Obsidian keeps everything on one device, and I'm on my phone, my desktop, and my laptop all day. A second brain I can only reach from one machine isn't a second brain. It's a filing cabinet in one room of the house.
Everything I run is cloud-based, so I built mine in Google Drive instead. It's a folder of small markdown files I call my AI Vault: who I am, the rules every AI has to follow when it works with me, and what's currently in motion.
Both Claude and ChatGPT read it through the Google Drive connector. Same files, either tool.
If a better AI shows up next year, my entire history comes with me.
That's the part I want you to sit with. Memory features are convenient, but they're also a lock-in play. Context you can't read, edit, or move was never really yours.
One distinction before you run off and build one: this is not a replacement for your AI skills. Skills are your repeatable processes, the things you run over and over (I wrote about organizing your AI skills if that's new to you). The vault is the context layer underneath them, and it doubles as a backup home for those skills so they're not trapped in one tool either.
What actually changes when your AI has a second brain
❌ Before
- ❌ Every chat starts coldre-explaining your business again
- ❌ Context trapped in one toolswitch tools, lose everything
- ❌ Decisions scatteredwhat did we decide last week?
✅ After
- ✅ One vault, always currentevery chat reads it first
- ✅ Works in any AI toolthe files are yours, not theirs
- ✅ Chats write backeach session updates the next
The loop is the magic. Every real work chat starts by reading the vault, and ends by writing a short recap back into it: what we decided, what we created, what's still open.
So every conversation inherits the last one. Monday's chat knows exactly what Friday's chat finished.
Where to start with your own AI vault
- A cloud folderI use Google Drive. Dropbox or Notion work too. So does a plain folder you copy-paste from. The structure is the system, not the integration.
- The AI tool you already use mostIdeally one that can connect to your folder, but pasting your files into a chat gets you most of the benefit on day one.
- Your AI tool's settings panel, openThis is the step most people skip. Without instructions in your settings, the vault is just a folder you have to remember to mention.
- About 20 minutesNot to write anything. The prompt below pulls what your AI already knows about you and just asks about the gaps.
Build your starter vault in one sitting
Run this in the AI tool you use most. It builds the files from what your account already knows about you.
Copy and paste
I want to create a portable 'second brain' folder in [Google Drive] that any AI chat can read for context about me and my business. You already have context about me from this account (my profile, memory, and past chats), so pull from that first and only ask clarifying questions about anything genuinely missing. Draft three markdown files: (1) About Me: who I am, my business, my offers, who I serve; (2) Working Rules: how I want AI to behave with me, including [e.g. draft never send, ask before assuming, tone rules]; (3) Current Projects: what's active right now with status and next steps. Keep each file under one page with plain headers and a 'last updated' date. Show me all three for review and let me correct anything before creating them.
The takeaway
Your context should live in files you own, not in any tool's memory. Three small files and one settings block, and every chat you have from now on starts warm.
The full breakdown is inside The Shortcut
The prompt above builds the vault. Members get the system that keeps it alive.
- The settings instructions block that makes every future chat read the vault automatically, without you asking
- Prompt 2, the end-of-session recap that makes every chat inherit the last one
- Prompt 3, the scheduled maintenance tasks: the daily catch-up, the weekly cleanup pass, and the compression step that stops old recaps from piling up
- The full folder structure I actually use, beyond the three starter files
- How to back up your AI skills into the vault so your processes are portable too
- The privacy fence rules that keep personal life out of business content automatically
- The audio walkthrough and the full tool-by-tool setup
Let's be real about what a second brain needs to stay useful
A second brain rots if nothing maintains it.
Files go stale. Strays pile up. And an AI reading a vault full of outdated decisions is worse than an AI reading nothing, because it will act on last month's plan with full confidence.
So don't treat this as a build-it-once project. Treat it like any folder that matters: something has to refile the strays and flag what's gone stale, on a schedule, or you end up with a junk drawer instead of a brain.
The other honest caveat: the vault only works if the recaps actually get written. Skip the end-of-session habit for two weeks and your "current projects" file is fiction. Inside The Shortcut I share the prompts that automate both, but even done by hand, the habit is the system.
Common questions
What is an AI second brain?
An AI second brain is a folder of plain text or markdown files that holds your standing context: who you are, how you work, and what's currently active. AI chats read it at the start of a conversation so they begin with full context instead of zero, and update it at the end so the next conversation picks up where this one left off.
Do I need Obsidian to build a second brain?
No. Obsidian is one viewer for markdown files, but the system is the files themselves, and they can live anywhere. A cloud folder like Google Drive works better than a local vault if you work across multiple devices or want automated tasks to reach it, since local folders can only be accessed from one machine.
Can Claude and ChatGPT read files from Google Drive?
Yes. Both Claude and ChatGPT offer a Google Drive connector that lets a chat read files directly from your Drive folders. That means one set of context files can serve either tool, and switching tools mid-project doesn't cost you your history. If you don't connect anything, you can still paste the files into a chat manually.
Does a second brain replace AI memory features?
It replaces your dependence on them. Built-in memory is convenient but tool-locked: you can't fully read it, edit it, or take it with you. A file-based second brain gives you the same continuity in a format you own, so any AI tool, now or in the future, can pick up your context.
How is this different from custom instructions?
Custom instructions and the vault work together. The instructions block in your AI tool's settings is short and points at the vault: it tells every new chat to go read your files. The vault holds the actual content, which can grow far beyond what a settings field allows and stays editable as plain files.
Recommended Resources 🛠️
The tools behind this shortcut:
