← ObsidianCONTENT HISTORY
WHAT CHANGED
Update to Obsidian
Snapshot Nov 18, 2026 · 06:20 UTC · version 1.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Obsidian and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.",
"included_files": [],
"name": "obsidian-cli",
"skill_md_contents": "---\nname: obsidian-cli\ndescription: Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.\n---\n\n# Obsidian CLI\n\nUse the `obsidian` CLI to interact with a running Obsidian instance. Requires Obsidian to be open.\n\n## Before using the CLI\n\nRun `obsidian help` to check availability. If the command is missing, explain how to turn on the CLI using https://help.obsidian.md/cli. The `obsidian` command ships with the Obsidian installer; don't install the unrelated npm package `obsidian-cli`. If it can't find Obsidian, ask the user to open the desktop app, then retry. In a sandboxed shell the same message can mean the sandbox blocked the CLI's local socket.\n\nOn WSL, run `Obsidian.com` from the Windows install folder, not `Obsidian.exe`. `Obsidian.com` is the console wrapper that prints the output; `Obsidian.exe` exits without printing anything.\n\nThe CLI exits with status 0 even when a command fails, so read its output before reporting that a command succeeded.\n\nQuote parameters for the current shell, and pass note text as literal argument data, never as executable shell syntax.\n\n## Command reference\n\nRun `obsidian help` to see all available commands. This is always up to date. Full docs: https://help.obsidian.md/cli\n\n## Syntax\n\n**Parameters** take a value with `=`. Quote values with spaces:\n\n```bash\nobsidian create name=\"My Note\" content=\"Hello world\"\n```\n\n**Flags** are boolean switches with no value:\n\n```bash\nobsidian create name=\"My Note\" open overwrite\n```\n\nUse `overwrite` only when replacing an existing file is intended.\n\nOpening is opt-in: pass `open` to open the file, and add `newtab` to open it in a new tab. There is no `silent` flag.\n\nIn `content=`, `\\n` becomes a newline and `\\t` a tab. Every `\\n` and `\\t` is converted and there's no escape, so text such as the LaTeX `\\theta` or the path `C:\\notes` is corrupted. Write content that contains backslashes, or is longer than about 4 KB, directly to the note's file instead.\n\nA dot in a file name is read as the start of an extension. When a name contains a dot, include the extension: `create name=\"Meeting 2026.11.06.md\"`, `rename name=\"v1.2 notes.md\"`, `move to=\"Archive 2026.10/Note.md\"`.\n\n## File targeting\n\nMany commands accept `file` or `path` to target a file. Without either, the active file is used.\n\n- `file=<name>` — resolves like a wikilink (name only, no path needed). `.md` is optional; other file types need their extension, e.g. `file=\"Projects.base\"`. Aliases don't resolve.\n- `path=<path>` — exact path from vault root, e.g. `folder/note.md`\n\n## Vault targeting\n\nWithout `vault=`, commands target the vault that contains the current directory, then the most recently focused vault. `vault=<name>` only works as the first parameter; anywhere else it's ignored:\n\n```bash\nobsidian vault=\"My Vault\" search query=\"test\"\n```\n\nUse `vault=` when the user has selected a vault. If the target is unclear and the user has several vaults, ask which one before changing files.\n\n## Common patterns\n\n```bash\nobsidian read file=\"My Note\"\nobsidian create name=\"New Note\" template=\"Template\" # a template replaces content=\nobsidian create name=\"New Note\" content=\"# Hello\" open # also open in Obsidian\nobsidian append file=\"My Note\" content=\"New line\"\nobsidian rename path=\"folder/note.md\" name=\"New name\"\nobsidian move path=\"folder/note.md\" to=\"archive/\"\nobsidian delete path=\"folder/note.md\"\nobsidian search query=\"search term\" limit=10\nobsidian daily:read\nobsidian daily:append content=\"- [ ] New task\"\nobsidian property:set name=\"status\" value=\"done\" file=\"My Note\"\nobsidian tasks daily todo\nobsidian tags sort=count counts\nobsidian backlinks file=\"My Note\"\n```\n\nUse `rename` and `move`, not filesystem `mv` or `obsidian eval`, so Obsidian can update links to the file. If other notes link to it and Settings → Files and links → Automatically update internal links is off, Obsidian asks in a dialog and the command waits until someone answers. `delete` moves the file to the trash; don't pass `permanent` unless the user asks for it. Prefer `create` and `append` over `eval` for writing note bodies.\n\nUse `total` on list commands to get a count.\n\n**Output options placement:** `--copy`, `--json`, `--md`, `--tsv`, and `--csv` only work **after** the command name. Putting them before the command (or before `vault=`) fails — often as `Command \"--copy\" not found` — because the first token is treated as the command. Prefer `vault=` first when used; put double-dash options last:\n\n```bash\nobsidian tasks todo total --copy\nobsidian vault=\"My Vault\" search query=\"TODO\" --copy\nobsidian tasks todo format=json # many list commands also accept format=\n# Wrong: obsidian --copy vault=\"My Vault\" tasks todo\n```\n\n## Plugin development\n\n### Develop/test cycle\n\nTurn on console capture once with `obsidian dev:debug on`, so messages from the reload are kept. After making code changes to a plugin or theme, follow this workflow:\n\n1. **Reload** the plugin to pick up changes:\n ```bash\n obsidian plugin:reload id=my-plugin\n ```\n2. **Check for errors** — if errors appear, fix and repeat from step 1:\n ```bash\n obsidian dev:errors\n ```\n3. **Verify visually** with a screenshot or DOM inspection:\n ```bash\n obsidian dev:screenshot\n obsidian dev:dom selector=\".workspace-leaf\" text\n ```\n4. **Check console output** for warnings or unexpected logs:\n ```bash\n obsidian dev:console level=error\n ```\n\n`dev:screenshot` saves to a temporary file and prints its path. A relative `path=` saves inside the vault.\n\n### Additional developer commands\n\nRun JavaScript in the app context (prefer dedicated commands like `rename`, `move`, `create`, and `append` for vault mutations):\n\n```bash\nobsidian eval code=\"app.vault.getFiles().length\"\n```\n\nInspect CSS values:\n\n```bash\nobsidian dev:css selector=\".workspace-leaf\" prop=background-color\n```\n\nToggle mobile emulation:\n\n```bash\nobsidian dev:mobile on\n```\n\nRun `obsidian help` to see additional developer commands including CDP and debugger controls.\n"
}SHA-256 of public snapshot: add8b1e78e0831cbc4ea4a626cdfea14e2017ed78385c6de8a7ea3f9a044cc27