Most of these are the built-in note properties, such as note.title, note.todo_completed, etc.
complemented with special properties such as note.isWatched, to know if a note is currently
opened in the external editor, and note.tags to get the list tags associated with the note.
The note.todoStatusText property is a localised description of the to-do status (e.g.
"to-do, incomplete"). If you include an <input type='checkbox' ... /> for to-do items that would
otherwise be unlabelled, consider adding note.todoStatusText as the checkbox's aria-label.
The item.* properties are specific to the rendered item. The most important being
item.selected, which you can use to display the selected note in a different way.
An array of at least one element and at most three elements.
What to search for: free text (embedded internally), or an existing note whose stored chunks are reused as the query — useful for "related notes", tag suggestions, and graph-style use cases without a second embedding pass.
Relevance preset for semantic search. Maps internally to model-specific
(k, minScore) tuning — the preset is the public contract so plugins keep
working when the bundled embedding model changes.
Where to look for matches.
all: every indexed note (default).note: a single note (rarely useful directly — mainly an internal
building block).folder: all notes in the given folder (a "notebook" in the UI).tag: all notes tagged with the given tag.Trashed and conflict notes are always excluded.
Role of a chat message.
systemmessages set the assistant's behaviour,usermessages come from the end user, andassistantmessages are model responses fed back as conversation history.