Skip to content

From Grok to Obsidian: owning my AI memory

Published:
2 min read

I asked for my AI history. I got my tweets and media, but not my Grok conversations.

That annoyed me enough to build an exit hatch.

The workflow is simple:

Grok on X -> capture conversation data -> Markdown -> Obsidian

From there, my local private agent can use the knowledge directly. Not through a platform memory feature I cannot inspect. Not through a black box that may or may not remember the right thing. Just files. Markdown. Local search. Git if I want it.

The first run moved 1,174 conversations into local/private notes.

That number is less important than the principle. AI chat history is becoming real personal infrastructure. It contains ideas, decisions, half-written plans, code discussions, debugging sessions, and sometimes the only explanation of why something was done a certain way.

Leaving all of that trapped inside a platform is a bad default.

I want a memory layer I control:

Obsidian is not magic here. Markdown is the important part. Obsidian is just a good interface over plain files.

The more I use AI tools, the more I think data portability should be treated as a basic feature. If a system helps me think, build, and decide, I should be able to take that history with me.

Platform memory is convenient. Owning your memory is better.


Edit on GitHub