A preview of the OpenHuman memory in Obsidian. Data from various sources (GMail, Slack, Whatsapp etc..) is organized as a memory tree.
+
OpenHuman's memory is not a black box. The same chunks the agent reasons over are written as plain `.md` files into a vault inside your workspace. You can open it in [Obsidian](https://obsidian.md), browse it, edit it, and link notes by hand — and the agent will see your edits.
The design is directly inspired by [Andrej Karpathy's obsidian-wiki workflow](https://x.com/karpathy/status/2039805659525644595): a personal wiki where every interesting thing in your life ends up as a linkable note.
@@ -35,9 +37,9 @@ Anything you put in `wiki/notes/` is fair game for ingest. The same pipeline tha
This means you can:
-- Drop a meeting note in `wiki/notes/2026-05-08-board-call.md` and the agent will know the context tomorrow.
-- Maintain a file per project, per person, per ticker — the topic tree treats your manual notes as just another source.
-- Bulk-import an existing Obsidian vault: drop the `.md` files in and trigger ingest.
+* Drop a meeting note in `wiki/notes/2026-05-08-board-call.md` and the agent will know the context tomorrow.
+* Maintain a file per project, per person, per ticker — the topic tree treats your manual notes as just another source.
+* Bulk-import an existing Obsidian vault: drop the `.md` files in and trigger ingest.
## Why this matters
@@ -47,5 +49,5 @@ It's also the cleanest possible export: stop using OpenHuman tomorrow and you ke
## See also
-- [Memory Tree](memory-tree.md) — the pipeline that produces the vault.
-- [Auto-fetch from Integrations](auto-fetch.md) — how the vault grows on its own.
+* [Memory Tree](memory-tree.md) — the pipeline that produces the vault.
+* [Auto-fetch from Integrations](auto-fetch.md) — how the vault grows on its own.