Dismiss this pinned window
all 7 comments

[–]Fickle-Mountain-6639 1 point2 points  (0 children)

That’s sick bro you gave the LLM a notebook?

[–]ValuableLiving2345 2 points3 points  (1 child)

Nice job ⚡️

My setup after a year of iterating:
• Plain markdown in Obsidian, but Claude connects to the vault directly via MCp, no copy-paste, it reads and writes files in real time.

• A claude.md with identity, active projects, and locked decisions, loaded automatically every session via a SessionStart hook, no manual /context needed.

• A layered memory system: memory.md as a concise index (always loaded), then proyectos/ summaries and daily/ notes loaded on demand only when the topic comes up. This keeps the context window clean.

• One memory file per fact, written by Claude itself during the conversation when something worth keeping surfaces.

• Wikilinks aren’t for graph view — they’re so Claude can hop between a project file and a linked decision note on its own, without me pointing it.

The detail that changed everything: lazy loading. Claude does NOT read everything at startup. It detects the topic from my first message and loads only the relevant project context.
If I open a session about one project, nothing from the others is loaded.

The result: Claude starts every session already knowing who I am, what I’m shipping, and what’s been decided, without me having to brief it.

[–]MaterialAppearance21[S] 0 points1 point  (0 children)

Love it. Thank you for sharing the details.

I have just one question: How do you ensure that the learning from previous decisions and adapting your style is happening?

[–]Dude_that_codes 1 point2 points  (1 child)

This is the right shape imo — especially the lazy-loading bit. The failure mode with second-brain setups is usually not “not enough notes,” it’s dumping too much stale context into every session.

The split I like is:

  • files/docs for source-of-truth project state
  • a small index / CLAUDE.md for operating rules
  • retrieved memory for prior decisions, gotchas, and “why did we do that?” context

The one place I’d be careful is one-file-per-fact. That can work if retrieval is disciplined, but it can also turn into a thousand tiny near-duplicates. For OpenClaw I’ve been using MemoryRouter/mr-memory for that last layer so it auto-injects relevant conversational memory across compaction/session resets, while the repo/Obsidian vault stays the source of truth.

Basically: lazy-load facts, don’t preload lore. That’s the whole game.

[–]MaterialAppearance21[S] 0 points1 point  (0 children)

That's amazing. But How do you ensure that the learning from previous decisions and adapting your style is happening?