› cavi-ai/

/products/plugins · Plugin · docs v0.1.0

Stop wiring a separate Obsidian integration for every agent host you run.

Obsidian Agent packages one canonical capability registry and ships native provider packages for Claude, Codex, Gemini, and OpenCode, with AgentSkills as the portable fallback — all driven through the official Obsidian CLI instead of a bespoke integration per host.

Read the documentationView source (opens in new tab)

/why

Three ways per-host vault integration goes wrong

5 documented pages, one registry.

01

Every agent host wants its own vault integration

canonical registry

The registry defines each workflow once, and Claude, Codex, Gemini, OpenCode, and AgentSkills consume that same definition — instead of you writing and maintaining five separate integrations that each drift on their own schedule.

02

Per-host adapters quietly fork the real workflow

host adapters

Host adapters package or delegate to the canonical skill files under skills/. The docs are explicit that adapters must not fork workflow behavior or introduce host-specific vault semantics.

03

Agent writes can silently overwrite a note

preview-and-confirm

Writes stay preview-and-confirm, avoid silent overwrites, and reread changed notes afterward. Exact vault-root targets use path= rather than a fuzzy match, and the portable core does not use obsidian eval as an escape hatch.

/hosts

Native where it counts, portable everywhere else

Read operations go through explicit official Obsidian CLI arguments.

  • Claude — native provider package
  • Codex — native provider package
  • Gemini — native provider package
  • OpenCode — native provider package
  • AgentSkills — portable fallback, no native package required
Docs version
0.1.0
Release tag
v0.1.0
Release commit
b0b0cf03658b
Documented pages
5
Content hash
b9d24e448a47

/relationship

Distinct from Companion for Claude, on purpose

Two public projects, two repositories, one shared vault.

  • Obsidian Agent is independent of Companion for Claude and talks to the vault through the official Obsidian CLI, not Companion's optional MCP bridge.
  • Companion for Claude is the in-vault chat interface; Obsidian Agent is the portable skill registry that Companion's workflow can call into.
  • Companion for Claude →

/skills

30 skills across 6 categories

One registry, grouped by the job it does inside the vault.

/install

Install the provider for your host

Requires Obsidian 1.12.7 or newer and the official Obsidian CLI.

  • Install the provider package for the host you use from the providers/ directory, or install the complete repository through a supported marketplace.
  • Provider adapters delegate to the canonical workflows under skills/.
  • Validate an installation with the repository's registry and portability checks.
Read installationView repository (opens in new tab)

/provenance

What this page does and doesn't attest

Obsidian Agent has no catalog release manifest, so it carries no verification claim here.

  • The docs snapshot binds this page to release tag v0.1.0 and a content hash; it does not carry a source tarball hash, an exported symbol list, or provider compatibility evidence.
  • Repository tags and GitHub Release artifacts remain the authoritative release record — see the repository (opens in new tab).