Build a source-linked second brain with Obsidian and Codex

Keep originals separate from summaries

Obsidian provides a vault of local notes; Codex works with the same folder. The demonstration uses a fictional workshop, so you can follow the process without copying private business data into a test.

The folder structure separates raw material from derived pages. A project summary should make it easier to find the original evidence, rather than silently replace it.

Set up the shared workspace

No separate Obsidian plugin is required for the route in the video. Only use information you are comfortable sharing with your AI service.

1. Install Obsidian and create a vault.
2. Set up Codex and open that same vault folder.
3. Ask Codex to read a specific note and check it found the right source.
4. Organise raw notes, wiki summaries and AGENTS.md instructions.
5. Add the fictional workshop notes and build a project page linking to them.

Use and maintain the project page

Ask a question across the notes, then follow the answer’s links back to the originals. If a decision is missing, keep it visibly missing: a suggestion is not an agreed decision.

The demonstration updates the plan when a decision changes, then starts a fresh task to pick up the work. Check that the new task reads the maintained files, rather than relying on a previous conversation’s memory.

1. Ask a project question and check the cited notes.
2. Record a missing decision separately from proposed answers.
3. Update the plan when a real decision changes.
4. Start a fresh task and verify the current project state.

The takeaway

Maintain a small source-linked project page, keep the raw notes intact, and check important answers against the originals.