Herdsidian
My coding agents already work from an Obsidian vault: agent briefs, standards, one note per project and a daily log the agents write back to. But the vault lived in another app, one window away from the terminals where the agents actually run. Herdsidian puts it next to them.
It is an add-on for the Herdr desktop app, which I created in 2026 and am still developing. It ships as a layout with seven JavaScript mods built on Herdr's gpui-kit mod API. The Notes sidebar browses, searches, reads and edits any folder of Markdown files (Obsidian is not required), with wikilinks that open the linked note and a save that never overwrites an edit an agent made in the meantime: it asks first, Reload or Overwrite.
The core idea is agent context. You link notes to an agent's space, or set a folder once in a note's frontmatter, and a local graph shows each note's neighbours one or two hops away: the standards it cites, the traps it warns about, the agents that use it. Send to agent pastes the linked paths into the agent's prompt (@path for Claude Code, the plain path for other agents) and never presses Enter, so you always read the prompt before it goes. The links live in a machine-local state file, never in the vault, and reach the agent by clipboard paste, a decision recorded as an ADR. A ⌘K palette searches notes, agents and commands in one popup, and sends the selected note to the agent the same way, without Enter.
The look is Graphite Glass: tinted transparent panels over a gradient of the theme, with terminals as solid cards, in eight themes (four dark, four light). A second ADR makes every colour in the mods derive from the active theme, and a lint script enforces it, along with byte-for-byte copies of the shared code in each mod. A node:test suite of 336 tests covers the logic.
It was built with a multi-agent pipeline (spec, plan, parallel implementers, then code and cleanup reviews), the same way I work on this site. It is MIT licensed and maintained in the open on GitHub. The screenshots use demo data only.