The vault. Must allow writes (i.e. the server was started
with --enable-writes).
note_path, role, content are required. thread_title
is used only when creating a brand-new note from scratch.
The note's vault-relative path plus the 1-based line range of the appended message (for jumping the UI to it).
Append a message to a note's chat thread — note-tethered AI conversations persisted as markdown.
Creates the note (and the
## Chat: <title>parent heading) if absent. Messages are stored as third-level headings with role + ISO timestamp (### user · 2026-05-08T10:00Z). The format is human-readable, version- controllable via git, and feeds back into the vault's retrieval index — agents can search past threads by content like any other note.Appending always creates a fresh
### <role> · <timestamp>block, never mutates existing messages. Safe to call concurrently if note writes don't collide (last-write-wins on simultaneous appends to same note).