Havemind
Self-hosted, real-time sync for Obsidian, built for two or three people sharing one vault. Everyone keeps a normal local copy; a server you own passes the changes around and remembers who wrote what. AI agents can join as members too.
Write on the laptop, it is on the phone about a second later. The Havemind mark spins while it sends and turns green when done.
Who it is for
A small group, two or three people, sharing one vault. Everyone keeps a normal local copy, every edit has an author, nothing is overwritten silently, and the data stays on a server you run. If you also run Claude, MCP or another local agent in that vault, its edits land in the same history.
What you can do with it
- Share one vault across people and devices. Mac, Windows, Linux, iPhone and Android; notes, images, PDFs, themes and hotkeys.
- Never lose an edit. Edits that do not overlap merge on their own. When two people change the same lines, both versions survive and a copy lands in a conflicts folder.
- See who wrote what. The Activity panel shows every change with its author; any note's history can be compared and restored.
- Add AI agents as members. Background agents (inbox sorter, daily summary, link gardener and more) join in yellow, each with a task note, and their edits land in the same history as everyone else's.
- Add a device with a phone call. The new device shows six digits; the owner types in what they hear.
Inside Obsidian
The Havemind pane has three tabs. Status shows the connection and what is waiting to send.
Activity lists every change with its author. Here, background agents sorted the inbox, wrote a daily summary and turned meeting notes into tasks.
People shows the members, their devices and the agents, and is where you add an agent with one click.
The same pane works on the phone.
How it is built
- TypeScript Obsidian plugin plus a small server you host yourself with one command; there is no Havemind cloud.
- The server stores revisions and authorship; merging happens on the devices, and the server never computes diffs.
- The author of each change comes from the server, never from what a client claims.
- No end-to-end encryption: whoever runs the server can read the vault, and the README says so up front.
- A two-week pilot on two devices lost no data, including through three real incidents.