| name | obsidian-desktop |
| description | Use when the user asks Innate Desktop to work with their connected Obsidian vault — "save this as a note", "add to my Obsidian", "find my notes on X", "what did I write about Y". Here the vault is NOT the working directory; it lives at the absolute path given in your system prompt. Read and write notes (Markdown files) under that path, preserving Obsidian conventions. |
| license | MIT |
| metadata | {"category":"obsidian-routing","primary-interface":"file tools by absolute path (+ obsidian CLI if available)"} |
| triggers | ["Obsidian","vault","note","notes","save as note","daily note","笔记","知识库","保存为笔记"] |
Obsidian vault from Innate Desktop
You are in Innate Desktop, not inside Obsidian. The user has connected a vault,
and its absolute path is stated in your system prompt (e.g. "an Obsidian
vault at /Users/.../MyVault"). That path is not your working directory — you
reach the vault by absolute path.
Every note is a Markdown (.md) file under the vault root, organized in folders.
To act on the vault:
- Your normal file tools, by absolute path — this is the primary interface.
Read existing notes by joining the vault path with the note's relative path;
create a note by writing a
.md file under the vault root; edit a note by
editing its file. Always build paths from the vault root in the system prompt;
never assume the vault is the current directory.
- The official
obsidian CLI — only if it is on PATH. It gives vault-aware
actions (search, daily note, backlinks, properties, command-palette actions).
If a quick obsidian help works, prefer it for search and daily-note actions;
otherwise fall back to file tools.
Finding and searching
- To find/search ("my notes on X", "where did I write about Y"): if the
obsidian CLI is available, obsidian search "<text>"; otherwise grep the
.md files under the vault root. Don't read many files one by one to simulate
a search.
- There is no "active note" here — Innate Desktop isn't attached to a note.
If the user says "this note" without naming one, ask which note they mean.
Preserve the user's conventions
Notes use Obsidian-native syntax that must survive your edits — keep them intact:
- Wikilinks
[[Note]] / [[Note|alias]], embeds ![[Note]].
- Tags
#tag / #nested/tag.
- Frontmatter — a YAML block at the very top between
--- fences.
- Callouts
> [!note], tasks - [ ] / - [x].
When asked for a small change, make the small change — don't reformat a whole
note. After saving, confirm in ~1 line; don't re-paste the note back.
Saving research / answers as a note
A common ask is "look this up and save it as an Obsidian note." Do the work
(search the web, summarize), then write a clean Markdown note under the vault
root — a sensible filename, a # Title, the content, and any wikilinks/tags
that fit the user's vault. Tell the user the path you wrote.
