v1.9.0
MCP resources & subscriptions, tool annotations, and a workspace that
remembers its view.
Added
- Notes are MCP resources. Every note is listed as a resource
(vellum://note/{path},text/markdown) with a URI template for
arbitrary paths, so MCP clients can attach notes as context without a
tool call. Clients can subscribe to a note and receive
notifications/resources/updatedwhenever it changes — through any door
(MCP tools or the web editor). The resource list re-announces only on
create/delete/title change, not on every keystroke autosave. - Tool annotations and titles. All 21 tools now carry
readOnlyHint/destructiveHint/idempotentHint/
openWorldHint: falseplus a human-readable title, so clients can
auto-allow reads and warn only on genuinely destructive calls
(delete_note,write_noteoverwrite,patch_note). - Server instructions. The MCP handshake now includes a short guide to
the vault conventions (inbox flow,expected_hashconcurrency,
wikilinks, task statuses, resource URIs) — agents no longer have to
discover them by trial and error. - Filters live in the URL. The selected folder, active tags and the
type/status filters persist as query parameters
(?dir=…&tags=a,b&type=task&status=done): a refresh keeps the view and
a filtered view can be bookmarked or shared. Opening notes keeps the
filters; Back still steps between notes, not filter clicks. - UI preferences survive a refresh. Theme (initialised from the OS
prefers-color-scheme, applied before first paint — no white flash),
the editor view mode (edit/split/preview, now also stable across note
switches), the Projects group expansion and the tag-list "Show all"
state are stored inlocalStorage.
Fixed
- The last second of typing no longer dies with the tab. Autosave is
debounced at 1 s; a refresh or tab close inside that window used to drop
the keystrokes. The dirty draft is now flushed with akeepalive
request when the page hides. - The MCP server no longer advertises the
loggingcapability it never
used.
Docs
- New docs/mcp.md — the full MCP reference (transports,
handshake, every tool with annotations, resources, subscriptions,
client setup) — and docs/workspace.md — the web
UI reference (URL scheme, storage keys, autosave/conflict/flush,
self-sync). The e2e checklist gained persistence & resources
scenarios.