Use Obsidian Agent Client as an Obsidian front end for local agents
Run ACP-compatible agents such as Claude Code, Codex, Gemini CLI, OpenCode, and custom agents from inside Obsidian notes and vault context.
npx skills add agentskillexchange/skills --skill use-obsidian-agent-client-as-an-obsidian-front-end-for-local-agents
Use Obsidian Agent Client when an operator wants to run local ACP-compatible agents from inside Obsidian, mention notes as context, launch chats in sidebars, editor tabs, floating windows, or embedded note blocks, review visible note edits, and handle permission prompts without copy-pasting vault content into a separate agent UI. Invoke it instead of using the agent product normally when the task depends on Obsidian vault context, note-local prompts, saved chat history, embedded agent blocks, or side-by-side agent sessions tied to notes and folders. The scope boundary is the Obsidian desktop plugin workflow for local ACP agent sessions and vault-aware note operations; it is not a generic Obsidian product listing, coding-agent framework, SDK, or cloud automation platform.
What this skill actually does
Inputs and prerequisites: Obsidian desktop app, Obsidian Agent Client plugin, a locally installed ACP-compatible agent such as Claude Code, Codex, Gemini CLI, OpenCode, Kiro, Hermes Agent, or a custom ACP agent.
Setup notes: Install from Obsidian Settings > Community Plugins > Browse by searching for Agent Client, then enable the plugin. Install and authenticate the desired agent, open Settings > Agent Client, confirm the agent path through auto-detect or manual configuration, then start a chat from the Obsidian ribbon or an embedded agent-client code block.
Source and verification boundary: use https://rait-09.github.io/obsidian-agent-client/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.