Stop bookmarking things your AI will never see.
I believe most of you have already heard of Obsidian knowledge bases for LLMs. I used it that way for a long time, but I got tired of the "work about work." Keeping my context and my AI up to date manually was a second job I didn't want.
Now, I’ve automated the entire loop. Everything I consume on X, I just bookmark. At the end of every day, my Codex automatically pulls those bookmarks and consumes them as permanent memory. I don’t do anything. It’s all automatic.
The Problem: Context Debt
Most people treat knowledge like a filing cabinet they save it, then forget it. AI has the same problem. Every new chat starts cold because your AI doesn't know your history. Re-explaining your stack and goals every morning is a tax on your productivity.
The bottleneck isn't the model. It’s Context Debt.
We’re moving away from the "Chat Window" and into a Persistent Knowledge Layer. Your Obsidian vault shouldn't be a library; it should be the Brain of your personal assistant.
The 5 Layer Neural Structure
To make this work, we stop organizing for humans and start organizing for the machine. I use a Flat Architecture that Codex navigates like a mental map:
- AGENTS.md: This is the master file Codex reads first. It’s the "Global Variable" of your life. It tells the AI exactly who you are, what your 2026 goals look like, and your non-negotiable rules like "Never give me boilerplate" or "Always check my /notes before suggesting anything."
- inbox/: The staging area. Every article, technical doc, or voice note lands here first. No manual filing, no tagging, no friction. This is the "Raw RAM" of your system.
- notes/: This is your personal Wikipedia. Once information is processed, it lives here as interlinked facts API schemas, framework deep-dives, and research papers. This is the "Source of Truth."
- ideas/: This is the most important part. It’s your original thinking and your "vibe." Storing your unique logic here is what prevents Codex from giving you generic AI answers and forces it to solve problems the way *you* would.
- projects/: Where the work happens. Because your projects sit next to your notes, Codex can grab an insight from a paper you read three months ago and apply it to the code you are shipping right now.
This 5-layer structure is your Day One baseline. To make it work, I use Obsidian as the local 'Brain' and a custom Codex Skill I built to bridge the gap between my notes and the LLM
The Rule of Constant Refinement
Don't be afraid to break the structure. The moment you hit a new domain or a complex concept that doesn't fit, tell your agent to carve out a new space for it.
- Create New Contexts: If you’re deep diving into a new framework or a specific niche like "Local LLM Fine-tuning," spin up a dedicated folder for it immediately.
- Force the Update: Don't just move files around. Every time you change the structure, go back to your AGENTS.md or your master system prompt and tell your agents: *"The map has changed. Here is the new logic for how we store and retrieve this specific data."*
Building a 24/7 Intelligence Assistant
The number one reason knowledge systems fail is Capture Friction. I built a "Passive Ingest" system so I don't "do" the work; the pipes do.
Instead of manual bookmarking, we use Browser-use or Computer Use in Codex to scrape your digital highlights once per day. This ensures that you don't need to start a new habit and still able to extract all your knowledges.
The X (Twitter) Extraction Prompt
The YouTube Knowledge Prompt
The Daily Evolution Prompt
The Weekly Self-Management Prompt
Now you have successfully implemented a system that grows on its own.
You aren't just filing transcripts and bookmarks; you are feeding an organism. Because of these daily and weekly audits, your Codex doesn't just "have" information it *uses* it to sharpen its own tools.
The Freshman Rule: Accuracy Over Ego
As your vault grows, agents get "cocky." They take shortcuts. To fix this, I enforce the Freshman Rule:
- Cite the Source: Tell your agent it isn't allowed to make a technical decision unless it can link back to a specific file in your /notes. If the info isn't in the vault, the agent has to admit it's guessing.
- The "Plan-First" Checkpoint: Never let an agent just start typing code. Force it to write a 3-sentence "Battle Plan" based on your current AGENTS.md before it touches the keyboard.
- Kill the Assumptions: If a task contradicts a note you saved three months ago, the agent shouldn't try to be "clever." It needs to stop and ask you for the tie-breaker.
Enjoy your fully Autonomously agent that get smarter everyday
This is the end of the "Cold Start."
By the time I sit down at my M4 Mac Mini, my Codex has already spent the night scraping my bookmarks and updating its internal logic. I don’t wake up to a blank screen; I wake up to a Jarvis-style briefing from a partner that’s been working while I slept.
I've stopped "using" AI. I’ve started directing it. Treat it like a partner. Give it the keys to your office.
Follow @ziwenxu_ for the more tips, guide workflows, and weekly synthesis prompts behind this system. I'm posting every day.
