A personal OS in Obsidian

If your notes are already an Obsidian vault, you have the half of this that is genuinely hard to get back later. What you are missing is the half that decides whether the system is still true next month, and you can add it without leaving.

What you already have, and why it matters more than it seems

Obsidian's vault is a folder of markdown files on your disk. Not an export of your notes, not a sync of them: the files are the notes. You can open them in any text editor, grep them, back them up, and read them in ten years with Obsidian uninstalled. That property is close to impossible to acquire later, because a decade of records inside a product's database does not become portable just because you decide it should be.

It also means an assistant can read and write your notes directly, which is the thing that makes everything below possible. Nothing has to be integrated. The files are already there.

What Obsidian does not do

It does not file anything. It is an editor and a viewer over a folder, and a very good one, but every note in your vault got there because you put it there. There is no native layer that reads your email, decides which project a thread belongs to, and updates that project's file. The plugin ecosystem is large and some of it is excellent, but the honest description is that AI in Obsidian is something you assemble rather than something that arrives, which is the trade laid out in an AI second brain in Obsidian.

Laying out the vault

Use folders, not tags, for the four things that carry the system. Tags are good for the long tail and bad as load-bearing structure, because a tag scheme is a judgment you make on every single note forever.

  Vault/
    Projects/     one folder per project, an index note plus its sources
    People/       one note per person: history, what is owed either way
    Decisions/    what was chosen and why, dated
    Reference/    what you read, filed by the question it answers
    Routines/     the weekly review, the daily brief, written once

Two Obsidian-specific notes. Keep the daily note as a capture surface only, not as the record: things written there should end up in a project file, or they are lost in a stream nobody rereads. And resist the temptation to make the graph view the point. It is a lovely picture and it is not a system. The tool-agnostic version of this layout is at the template.

Adding the missing half without leaving Obsidian

Because a vault is just a folder, an assistant with file access can work on it alongside you. Obsidian stays open and stays your editor and reader. The assistant handles the part Obsidian was never built for: reading a meeting transcript and updating the project it belongs to, moving a finished project to an archive because you said it closed, writing the reasoning into a decision note as you talk through the decision.

Nothing gets migrated and nothing gets converted, which is the practical reason this route is easier than switching apps. You keep the vault. You add something that writes to it. The tooling side of that is at a personal OS built with Claude Code, and the reason a chat window is not sufficient for it is there too.

If you are considering leaving Obsidian instead

Worth checking that the reason is real. If it is that Obsidian has no AI, the layer above solves that without a migration. If it is that you want relations and structured databases, that is a genuine reason and the comparison is at Obsidian versus Notion AI. If it is that the vault has become a graveyard, moving it to a different app will produce a graveyard in a nicer typeface, which is the argument at why second brain systems fail. The wider field is at Obsidian alternatives.