You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c040ccc
Browse filesBrowse the repository at this point in the historyBrowse files
feat(views): standalone .view files — leaf, embeds, agent-writable, out of the index
Views become files, not fences in notes, when kept on their own. A `.view`
file holds exactly a fence's body (optional frontmatter, then HTML) and is
bound to a FileView that fills the pane; it re-renders when the file changes
on disk, follows renames and deletes like any file view, and — since
Obsidian has no editor for the extension — carries a minimal source mode of
its own (textarea, save/cancel, Cmd/Ctrl-S) behind a header action.
`![[Name.view]]` embeds and hover previews render through the embed
registry the `.chat` previews already use.
The chat toolbar's "save as note" and "open as view" collapse into one:
save as a `.view` file, which opens it. The corner button on fences in
notes and the note-index targeting (ordinal + title) go away with the
note-backed leaf they served.
Why a file: a fence in a note put its HTML and JavaScript into Obsidian's
search and, worse, the plugin's retrieval index; a `.view` file is indexed
by neither. Fences in notes stay for inline use, and their bodies are now
replaced by a `(view: <title>)` marker before indexing so a note that holds
a dashboard is still findable by name without its code becoming chunks.
`manage_notes` accepts `.view` paths so the agent creates and revises views
through the same staged review as notes.
Co-Authored-By: Claude <noreply@anthropic.com>
0 commit comments