Agents embedded in Obsidian
Developer Het demonstrated agentic AI running inside an Obsidian vault to speed brainstorming, architecture drafting and gap‑finding — a clear glimpse of how agents will sit inside PKM workflows. (x.com)
Het’s clip matches an existing Obsidian plugin, Agent Client, which embeds ACP‑compatible coding agents (Claude Code, Codex, Gemini CLI) into a right‑side panel inside a vault. (rait-09.github.io) The Agent Client GitHub repository shows active maintenance and community interest, with roughly 1.3k stars and a recent version bump to 0.9.1 in the project history. (github.com/rait-09/obsidian-agent-client) A different approach, the Vault Agent plugin, explicitly embeds terminals and an “agent‑aware” execution surface into Obsidian to let external agents run commands with vault context. (github.com/liuyixin-louis/obsidian-vault-agent) The underlying interoperability that makes these demos feasible is the Agent Client Protocol (ACP), an open JSON‑RPC standard led by Zed (with JetBrains participation) that standardizes editor↔agent communication. (zed.dev/acp) Projects targeting deeper automation inside vaults advertise richer capabilities—Obsilo Agent promotes “46+ tools,” multi‑agent workflows and persistent memory to let a vault act as a long‑lived agent workspace. (obsilo.ai) Developer docs for in‑vault agents already document UX primitives used in Het’s clip, including @notename file mentions, slash commands, multi‑agent switching, and terminal/command execution hooks. (rait-09.github.io)
