Obsidian CLI Use the CLI only for behavior that depends on Obsidian’s running application, indexes, settings, command registry, or developer runtime. Use normal shell filesystem tools for ordinary file reads, writes, directory listing, and text search. Capability probe and fallback Copilot exposes the terminal-capable executable from the running Obsidian installation as COPILOT_OBSIDIAN_CLI when it can resolve one. Prefer that exact path over obsidian from PATH, and always invoke it as a quoted executable rather than constructing a command string.

Callouts reference Folding and nesting > [!faq]- Collapsed by default > Hidden until expanded. > [!faq]+ Expanded by default > Visible but collapsible. > [!question] Outer > > [!note] Inner > > Nested content. Built-in types Type Aliases note — abstract summary, tldr info — todo — tip hint, important success check, done question help, faq warning caution, attention failure fail, missing danger error bug — example — quote cite

Embeds reference ![[Note Name]] ![[Note Name#Heading]] ![[Note Name#^block-id]] ![[image.png]] ![[image.png|640x480]] ![[image.png|300]] ![[audio.mp3]] ![[video.mp4]] ![[document.pdf]] ![[document.pdf#page=3]] ![[document.pdf#height=400]] A list embed needs a block ID after the list. An embedded search uses an Obsidian query block: ~~~query tag:#project status:done ~~~

Properties reference Properties are YAML frontmatter at the very start of a note. Property type Example Text title: My title Number rating: 4.5 Checkbox completed: true Date date: 2026-07-21 Date and time due: 2026-07-21T14:30:00 List tags: [one, two] or a YAML list Link related: “[[Other Note]]" Obsidian reserves tags, aliases, and cssclasses for their built-in behaviors. Tags may contain letters, numbers (not as the first character), underscores, hyphens, and forward slashes.

Obsidian Markdown Use Obsidian-specific syntax accurately. Do not spend tokens explaining ordinary CommonMark or GFM unless the user asks. Workflow Preserve existing frontmatter keys and formatting when editing a note. Use wikilinks for vault notes and Markdown links for external URLs. Use embeds, callouts, properties, tags, comments, and block references only when they improve the requested note. Check link targets, YAML validity, and block IDs after editing. Read the focused reference file when the task needs more syntax detail.

Publish Markdown to Symposium Require one existing Markdown source file. When the user asks to delete, remove, or withdraw its current Symposium page, do not generate HTML. Run the host wrapper with only the vault-relative source-note path. Obsidian reads the note’s current identity and opens its existing management modal; the user alone chooses Update or Delete. Never tell the user to delete the page at its public URL. For publishing or updating, finish a complete, self-contained, passive HTML document before asking Obsidian to review it.