The AI plugins all read your vault. None of them know anything you didn’t type.

Smart Connections, Copilot, Smart Second Brain — the good ones are search, retrieval and agents working over notes you already sat down and wrote. They make a vault easier to use. What none of them can do is bring in something that was never in it: the thread where you promised your mother a document, the mail about a renewal on Friday, the plan four people settled in a group chat last Tuesday.

We make one of the tools below. Brownie is ours, so read this the way you would read any comparison written by someone with a stake in it. Everything structural here comes from Obsidian’s own community plugin registry and from each project’s repository, both of which you can check yourself; where a tool has a paid tier we have linked to its pricing rather than quoted a number we would not keep current.

The split nobody names

A second brain has two halves. The plugins are all on one of them.

Working the vault

Search it by meaning, chat with it, surface related notes, run an agent across it. This half is crowded and genuinely good — Smart Connections builds its embeddings locally with no key at all, Copilot runs Claude Code and Codex inside the vault, Smart Second Brain does the whole thing over Ollama. All of them assume the vault is already full.

Filling the vault

Getting what happened into Markdown without you transcribing it. This half is nearly empty. Obsidian’s own Importer moves notes across from another notes app. A couple of plugins copy WhatsApp in as a transcript. Past that, the registry runs out — and the sources that hold most of your life are the ones missing.

Here is the clearest way to see it. On 1 November 2026 Obsidian’s community registry held 9,759 plugins. Searching every name, id and description in it for “iMessage” returns zero. Telegram has around twenty, mostly bots you forward things to on purpose. WhatsApp has a handful, and two of those are the same idea twice. The place where most people’s commitments actually get made has no road into the vault at all.

That is not an oversight by plugin authors. A plugin is JavaScript running inside Obsidian, and reading the Messages database means asking macOS for Full Disk Access and then parsing a SQLite file that Apple can change in a point release. It is the wrong shape of thing to put in a plugin. It wants to be a separate Mac application that writes into a folder — which is all an Obsidian vault has ever been.

Side by side

Where each one gets its material.

Tool	What it does	Where the content comes from	Runs unattended	Licence & price
Smart Connections	Related notes while you write, plus semantic search over the vault	Notes you already wrote	Indexes on its own; you still ask	Core free, source-available
Copilot	Runs agents — Claude Code, Codex, OpenCode — inside the vault; chat and multi-step edits	Notes you already wrote, plus your prompts	No — you drive it	AGPL-3.0 front end, paid Plus tier
Smart Second Brain	Chat with an agent that knows your notes, search by meaning, topic graph; runs on Ollama	Notes you already wrote	No — you ask	Free, open source (MIT)
Text Generator	Generates text into a note from templates and prompts	Prompts you write	No	Free, open source (MIT)
Obsidian Importer	Official. Converts another app’s export into Markdown in your vault	Notes you wrote in Notion, Evernote, Apple Notes, Roam, Keep, OneNote	No — one import at a time	Free, open source (MIT)
WhatsApp Local Sync	Reads the WhatsApp Desktop database and mirrors chats in as one transcript note per conversation	WhatsApp, read locally	Yes, incrementally	Free, open source (MIT)
WhatsApp backup importer	Turns a WhatsApp chat export (.zip) into Markdown, attachments included	A WhatsApp export you make by hand	No — manual, per chat	Free, open source (MIT)
Brownie	A Mac app, not a plugin. Reads overnight on your own GPU and writes a synthesis: one note per person, group and plan	iMessage, WhatsApp, Telegram, IMAP mail, Apple Notes, Calendar, files, Slack	Yes — nightly, while you sleep	Free, open source (AGPL-3.0)

Checked 1 November 2026 against Obsidian’s community plugin registry and each project’s repository. Licences are the ones GitHub reports; Smart Connections ships under its own Smart Plugins License rather than an OSI one, which is why it is described as source-available. Tiers move, so paid plans link out instead of carrying a number. Correct something by opening an issue.

The part that gets missed

A transcript is not a note.

The two plugins that do bring messages in bring them as transcripts: one note per conversation, every line of it, in order. That is the honest thing for them to do and it is useful if what you want is an archive you can grep.

But it makes the other half worse. Semantic search over forty thousand lines of “ok”, “haha” and “sent” returns forty thousand lines of noise, and every embedding plugin you have installed now has to index all of it. A fuller vault is not automatically a better one. Past a point it is a worse one, and the plugins that were working well over two hundred notes you wrote by hand start returning chat chaff instead.

What is actually useful in a vault is one note per person rather than per conversation: where things stand with them today, what is open in both directions, the standing facts worth knowing before you next speak. That is a summary, and writing it means reading everything and throwing nearly all of it away — which is the one thing a model on your own machine is very good at, and the one thing no plugin is positioned to do.

Where Brownie fits

It writes the vault. You keep it.

At an hour you choose, your Mac wakes itself and a four-billion-parameter model on your own GPU reads everything new since the last run — messages, mail, notes, files, calendar. Almost all of it is discarded. What survives is written as plain Markdown: one note per person, per group, per plan, with [[wikilinks]] that resolve, aliases and heading links that resolve, and YAML front-matter where any key you add yourself is kept verbatim and in order. Open the folder in Obsidian and graph view, backlinks and search all work, because there is nothing proprietary about it — it is a directory of .md files.

Raw messages never leave the machine. Only short summaries go to whichever model you chose, and the app shows every byte that left, kept thirty days. Choose “This Mac only” and the figure is zero: no key, no account, nothing out. Anything the reader marks sensitive — an ID number, a card, a diagnosis — is dropped whole and never reaches a note at all.

It cannot trample your edits

Each run is built in a staging copy and swapped in atomically, so the vault is never written in place and never half-written. Before the swap, Brownie re-checks a fingerprint of every file in the live vault; if you edited anything while the run was going, it abandons the swap and tries again tomorrow. A note whose body no longer hashes to what Brownie last wrote is marked as yours, wherever you edited it.

It is built to stay small

The target is eighty to a hundred and twenty notes, not thousands. There is a cap of ten root folders, the file tools refuse a ninth note in a topic folder, they refuse near-duplicate titles, and they will not delete anything under People/ or Groups/. A nightly pass keeps each note in shape so a year of runs cannot bloat it into something you stop opening.

It is a second vault, by design

Brownie writes to ~/Brownie Knowledge Base and never touches the vault you already have. Point Open folder as vault at it and you have both, side by side. That is deliberate: a tool that writes unattended every night should not have a path into ten years of your own notes.

Your other tools can read it

Edit a note in Obsidian and Brownie re-indexes within seconds — the watcher is on the folder, not on the app. Run Brownie mcp and Claude Desktop, Cursor or any MCP client can read the notes too, on that Mac only, with a log of what they asked for. Delete Brownie and the Markdown stays where it is.

Download the beta for macOS Read the vault specification macOS 14 or later · Apple silicon · AGPL-3.0

Questions

The ones people actually ask.

Is there an Obsidian plugin that reads my iMessage?

No. On 1 November 2026 the community registry held 9,759 plugins and a search across every name, id and description for “iMessage” returned none. WhatsApp has a few and Telegram has around twenty, mostly bots you forward things to. The reason is that a plugin is JavaScript inside Obsidian, and reading the Messages database means asking macOS for Full Disk Access, which an Obsidian plugin is a poor place to do. It takes a separate Mac application. Brownie is one.

Can AI write notes into my Obsidian vault automatically?

The plugins can write files, but only out of what is already in the vault plus what you type into them — an agent composing from your own notes. Writing in something that was never in the vault is a different job, because it needs access to the source. Brownie does that: it reads WhatsApp, iMessage, Telegram, IMAP mail, Apple Notes, Calendar and your files on your own Mac at an hour you choose, and writes plain Markdown notes with wikilinks, unattended, every night.

Will it overwrite notes I have edited myself?

No, and this is enforced rather than promised. Brownie hashes each note’s body, so a note that no longer matches what it last wrote reads as yours — edited in Obsidian, on your phone, anywhere. Every run is built in a staging copy and swapped into place atomically, and before the swap it re-checks a fingerprint of every file in the live vault. If anything changed while the run was going, the swap is abandoned and your vault is left exactly as it was. There is no half-written state, because the vault is never written in place.

Does Brownie write into my existing Obsidian vault?

No. It keeps its own vault, a folder called Brownie Knowledge Base in your home directory, and that is a deliberate choice rather than a limitation we have not got to — it means nothing Brownie does can reach the vault you have spent years on. Open the folder in Obsidian with Open folder as vault and you have a second vault alongside your own, with working wikilinks, graph view and search. If you later delete Brownie the Markdown stays where it is and remains yours.

If you are weighing this against the wider category rather than against plugins, we wrote that one down too: local AI assistants for Mac, where the same split appears as model runners versus things that read your machine. For what these notes are actually for, what did I promise? And against the assistant already built into your Mac, Apple Intelligence vs Brownie.

Give it one night.

Tonight it reads. Tomorrow there is a vault that knows what you were promised, what you owe, and where each thing stands — written while you slept, in Markdown you own.

Download the beta for macOS macOS 14 or later · Apple silicon · AGPL-3.0 · free, and no account

Home Privacy Terms GitHub Security