What Obsidian is for

Obsidian is a thinking tool, and a great one. Linked notes, a graph of your ideas, a plugin for anything you can imagine. If you live in markdown, you probably already live there. Stet doesn't replace it and doesn't try.

The gap

Obsidian was built for you to edit your own files. Then agents showed up. Now people point Claude Code at their vault and let it write. The plugins that add AI all share one assumption: the agent edits the file, and you find out by reading.

Some plugins are adding approval buttons. But an approval feature bolted onto one plugin only covers that plugin. Run a different agent, or a script, or Claude Code from the terminal, and the edits land silently again.

What Stet adds

Stet watches the folder itself. Every change, from any agent or any tool, is captured as a proposal before it touches your document. You review the change, see exactly what moved, and accept or reject it. The file on disk never contains words you haven't signed off on. And the history of who wrote what stays with the file, for as long as the file exists.

Use both

Same files, no migration, no lock-in. Obsidian is where you think. Stet is where you build: the spec that ships, the brief the agent acts on, the SOW that gets signed. Point Stet at that folder inside your vault and keep everything else exactly as it is.

Part of Where Stet fits, the map of the markdown neighborhood.