write-append

Call the obsidian-router append_to_file MCP tool with arguments parsed from $ARGUMENTS.

Arguments

Required:

• path — file path relative to vault root.
• content — markdown to append.

Optional:

• vault — vault name. Omit for default.
• requireExisting — if true, fail when the file does not exist. Default false (auto-create).

Argument parsing from $ARGUMENTS

• if the slash line has only a path, ask the user for the content to append
• path=X content="..." for one-shot
• --require-existing or requireExisting=true → set the flag

Use cases

• Daily journals, logs, running notes, captures
• For surgical edits under a specific heading or block, prefer write-patch instead

On failure — remediate, NEVER fall back to filesystem writes

If the call fails, do NOT silently redo it with direct-filesystem tools (Read/Edit/Write on the vault's real path):

• Connection error (ECONNREFUSED, timeout) → vault closed; list_vaults, then ask the user to open it via the openUri link and wait.
• Validation / API error (HTTP 4xx) → fix the arguments, or use a coarser router tool (write_file).

Rationale + message template: the default-vault-health-check convention (canonical source).

Output

After the append, report vault, path, bytesAppended.