Vault appearance and search — themes, wiki links, and finding a note
How the vault looks and how you find a note in it — the colour and theme options, the sidebar you can hide, wiki-link autocomplete as you type, the unified search modal, and the quick-switcher for jumping straight to a note by name.
On this page
What it is
This page covers two things that go together in practice: what the vault looks like, and how you get to the note you want — autocomplete as you type a link, the search modal, and the quick-switcher.
Where to find it
The Vault panel. Search is opened from within it, the quick-switcher is a keyboard shortcut, and the appearance options are in Settings under the vault's own section.
How it behaves
Softer default colours (Glassmorphism · Dark)
On the default theme — Glassmorphism · Dark — the note editor used to render a near-black page under near-white text, with a bright periwinkle accent and code blocks that blended into the background. That maximum contrast read as harsh for a text-heavy editor. The default now uses a gentler palette: a soft charcoal reading surface instead of stark black, eased-off body text (still crisp, just not glaring) with headings kept a touch brighter so the hierarchy stays clear, a calmer accent for links and the active note, and a faint visible container around code blocks so fenced code reads as a distinct block.
This refines the default only. It is scoped to the Glassmorphism · Dark theme, so every other visual theme and Light mode are unchanged, and you can still switch the Vault to any theme you like in the app's Appearance settings. The glassmorphism look itself — the blur, the drifting gradient glow behind the notes, the indigo identity — is untouched; only the surface and text tones are softened, in both the in-app Vault panel and the pop-out Vault window.
Custom theme options (appearance)
The Vault can carry its own look, chosen independently of the rest of Omniscio — a visual theme (any of Omniscio's 14 built-in themes OR one of your imported custom .theme.json themes), its own light / dark mode, and editor reading options. Everything defaults to "follow the app", so the Vault looks exactly as before until you opt in. Set it under Settings → Features → Vault → Vault appearance (the Visual theme and Light / dark rows are the first two in the card, and Settings search finds them as "Vault visual theme" and "Vault light / dark mode"), or use the toolbar gear icon (between Ask AI and Bookmark) for quick-access text size and light/dark toggles without leaving the editor.
- Visual theme — a preview-card grid (the same one Settings → Appearance uses) with a "Follow app theme" card first, then the 14 built-ins, then your custom themes. Picking one re-skins the Vault only — the editor panel AND its file-tree sidebar AND the pop-out window — while the rest of Omniscio keeps the global theme. (
nothariVisualTheme, default'app'.) - Light / dark — Follow app / Light / Dark for the Vault specifically, so you can run a light reading vault inside a dark app. (
nothariColorMode, default'system'.) - Editor font — Default (sans) / Serif / Monospace, applied to the note content. (
nothariEditorFont, default'sans'.) - Editor text size — Small / Medium / Large / Extra Large, applied to the note content. (
nothariEditorFontSize, default'md'.) - Editor width — Narrow / Normal / Wide / Full reading column.
'normal'(≈48rem, ~75ch) is the default so a fresh note gets a readable measure out of the box;'full'(edge-to-edge, no max-width) is opt-in for wide / table-heavy notes. (nothariEditorWidth, default'normal'.) - Page background — Follow theme / Paper / Sepia. Paper and Sepia force a warm, dark-text reading surface independent of the theme (readable even on a dark theme). (
nothariEditorBackground, default'theme'.) - File tree side — Left (default) / Right. Moves the KMS file list — and its Files|Sessions tab strip + collapse handle — to the right of the editor, in both the in-app panel AND the pop-out window. Vault-scoped and independent of the global app sidebar position; default Left is byte-identical to today's layout. (
nothariSidebarPosition, default'left'.) Full contract: kms-sidebar-position-contract.md.
Crossing off checklist items is always on. Checked task-list items (- [x]) show a strikethrough and dimmed text, and unchecking restores them. The setting behind it (nothariChecklistStrikethrough, default true) is read by the editor, but no control in the card writes it, so it cannot be turned off yet.
How it works (repo detail). A scoped wrapper element carries a mode class (dark/light) + a visual-theme class (theme-<id> / theme-custom-<id>) on the Vault roots (KmsView.tsx + KmsSubSidebar.tsx) — the same scoped mechanism the Mind Map uses — so the class-based CSS vars cascade onto the Vault subtree only. The resolver is shared with the Mind Map (scoped-theme.ts); the KMS wiring is useKmsTheme.ts. Because the global theme-store only injects a CUSTOM theme's CSS when it is the GLOBAL theme, the Vault injects its own selected custom theme into a separate #kms-custom-theme-css element (kms-theme.ts) so a custom Vault theme is styled even when the app runs a built-in. Editor font / font size / width / background ride data-kms-* attributes on the panel root → CSS targeting .kms-prose .ProseMirror in globals.css. The standalone window still adopts the base theme via useWindowThemeBootstrap. v1 gaps: portaled overlays (unified search / command palette / image lightbox) follow the APP theme; the mobile Vault sidebar isn't wrapped. Full contract: kms-theme-override-contract.md.
Hidden panel (Phase 3 Sub-PR 3f-2)
The right-pane panel stack carries a Hidden entry — collapsed by default — listing every note in the active vault whose hidden_at is non-null, sorted with most-recently-hidden first. The panel mirrors Bookmarks: a filter input narrows by note title, a roving-focus listbox renders each row, and clicking a row opens that note in the editor (the same code path as the file tree's open-note action). On row hover the panel reveals two icon buttons:
- Unhide — fires
kms:unhide-notewith{ vaultId, noteId }. The handler clearshidden_aton the row, the file reappears in the tree on the next push, and the panel removes the row optimistically. No confirmation prompt — Unhide is non-destructive (the file never left disk). - Permanent Delete — opens a danger-variant
useConfirmDialog. On accept, fireskms:note-soft-deletewith{ vaultId, relativePath }. The handler moves the file into<vaultRoot>/.trash/<timestamp>__<basename>(the same trash semantics as the file-tree Delete action, restorable from the Trash panel until the retention sweep reaps it, default 30 days; see mobile and internals → Privacy + safety contract) and removes the row fromnothari_notes. The panel reconciles via the standardkms:note-changedpush event.
The panel uses the same push reconciliation contract as Bookmarks — every kms:note-changed for a matching vaultId triggers a 200ms debounced refetch of kms:list-hidden-notes, capped at KMS_HIDDEN_LIST_LIMIT = 500 rows. Epoch counter drops stale fetches; per-row mutation lock prevents concurrent Unhide / Delete on the same row.
The Hide affordance in the file-tree context menu is file-only — folders never gain a Hide row (folders have no hidden_at column). The action is tri-state-gated: a file row that hasn't been indexed yet (no noteId) also skips the Hide entry, because Hide needs a real row to stamp.
Tags panel — rename or delete a tag everywhere
The Tags entry in the side-panel drawer lists every tag in the vault with how many notes carry it. A filter box narrows the list, and clicking a tag opens the first note that carries it. Hovering a row reveals two icon buttons:
- Rename tag — asks for the new name, then rewrites that tag everywhere in the vault: every inline
#tagand every frontmattertags:entry, in every note that carries it. - Delete tag — asks first, naming how many notes it will touch, then removes every
#tagand every frontmattertags:entry for that tag from every note. The note files themselves are not deleted — only the tag references.
Both write straight to your note files and cannot be undone from the panel. The old text is not lost, though: every note a tag change rewrote keeps the text it replaced in its History panel, so open the note and restore the earlier version. A message afterwards reports what happened — how many notes and occurrences changed, and how many files could not be updated — and a large vault takes a few seconds.
Trash panel and Undo (Phase 1 Trust)
Deleting a note never destroys it. The file moves into the vault's .trash folder, and there are two ways back:
- Undo — every delete entry point (the file tree's single delete, a multi-select bulk delete, the Command Palette, and the Hidden panel) raises the same success toast with an Undo button for 8 seconds. Pressing it restores the note by its trash entry name; the same restore sits on the app undo stack, so <kbd>Ctrl</kbd>+<kbd>Z</kbd> works too. A bulk delete where any note failed offers no Undo, because a partial batch has nothing single to restore.
- The Trash panel — a Trash entry in the right-pane stack, collapsed by default, lists every trashed note with its folder and when it was deleted. Each row has a Restore button that puts the note back where it was. The list refetches on the
kms:note-changedpushes that can change its contents — a delete (removed) or a restore (added) — and skips theupdatedpush of a content autosave, so a delete or restore from anywhere updates it without re-reading every trashed note's version history on each save.
Erasing a trashed note for good. Each Trash row also has a Delete forever button, and the panel has an Empty Trash button above the list. Both ask first, in the danger style, and say the erase cannot be undone; on yes they remove the trashed file and its saved versions (kms:note-trash-purge, kms:note-trash-empty). An agent reaches the same actions through POST /kms/trash/purge and POST /kms/trash/empty, and each one waits for you to approve its card first. Moving a note to Trash also throws away its unsaved crash-recovery draft and takes down any public page published from it.
Trash keeps notes for 30 days — the shared retention window — after which the sweep reaps them. The panel and the toast both restore through kms:note-trash-restore with the trash entry name, never a path rebuilt by hand.
What a delete drops, and what Undo brings back. Deleting a note removes its bookmark and any project-context pin that fed it into new sessions, and neither comes back when you restore it — a restored note is no longer in Bookmarks, and it is no longer given to new sessions until you pin it again. Its tags and its saved versions do come back, and every one of those versions is kept beside the trashed file for the whole 30-day window (not just the note's last text), so a note restored on day 29 still has its full History.
Bookmarks panel — labels and order
Bookmarks are pinned notes: the bookmark button at the right edge of the editor toolbar toggles the note you have open, and the Bookmarks panel in the right pane lists the pinned notes of the vault. Hover a row to Rename its label, and drag a row to reorder the list — the new order is saved when you drop it. From an agent: GET /kms/bookmarks, POST /kms/bookmarks, PATCH /kms/bookmarks/:id for the label, and POST /kms/bookmarks/reorder.
Note history (versions and restore)
Every save that overwrites a note's body keeps the text it replaced as a version, so an edit you regret can be undone. The right-pane History panel lists those versions for the note you are reading; pick one to look at it, and restore it to put that body back. A restore is an ordinary edit — it writes the old body and keeps a version of what it replaced — so a restore can itself be undone.
Where it is. Open the side-panel drawer with Toggle side panel in the toolbar, then expand History — it is collapsed by default. It lists the versions of the note you have open, newest first, with when each was saved, its title and its size, and each row carries a Restore this version button. The Vault keeps the most recent 50 versions of each note; older ones fall off the end.
- What gets a version: the body a save overwrites, including an autosave, a rename's wiki-link rewrite and an AI summary writeback. A save that is about to replace text another program wrote stores that outside text first, so a sync tool's copy is never lost silently.
- History follows a trashed note. Deleting a note moves its versions into the vault's
.trashbeside the file; restoring the note re-attaches them, and the same retention sweep reaps them together when the window passes. - A delete and its Undo are a round trip. The same sidecar also carries what the note row held and what pointed at it: whether it was hidden, its creation and last-opened times, its summary state, its bookmark, and its project pins. Restoring puts all of them back, so undoing a delete of a hidden note returns it to the Hidden panel rather than the file tree, and a project it was pinned to as context starts receiving it again.
- From an agent:
GET /kms/notes/:id/versionslists them andPOST /kms/notes/:id/versions/:versionId/restorerestores one.
Invariants: the KMS note version history contract.
Smart Connections (Phase 3.2)
The Smart Connections panel shows notes that are semantically related to the one you're reading but not yet linked. It uses cosine similarity over note embeddings (the same on-device embeddings semantic search uses) to rank results.
- Panel location: Right-pane drawer, between Backlinks and Tags
- What it shows: Up to 20 related notes ranked by similarity, with title, folder path, and a body preview snippet
- Filtering: Already-linked notes (via
[[wiki-link]]) and hidden notes are excluded — you only see connections you haven't made yet - One-click link: Hover a row to reveal a Link button that inserts
[[Title]]at your cursor position - Dependency: the notes need an embedding on disk. The Vault makes them itself — the embedding model runs on this computer and a backfill fills the vault — so the Vault has no switch of its own. It shares the app's ONE on-device model with AI-Powered Search and AI Coaching, though: see the note in When it runs below. A note with no embedding yet (never embedded, an embed that failed, or embedding paused) simply has no connections.
- When it runs: embedding is background work that follows the Vault, not a control you press. While the Vault is on and the model is in demand, every note that has no vector yet is embedded after each re-index, and a note you save is re-embedded about two seconds later. It uses the local model on this computer's CPU and makes no paid call. The model only loads on demand: with Settings → Sessions → AI-Powered Search and AI Coaching BOTH switched off there is nothing asking for it, so Vault embedding pauses — new and edited notes get no vector (Related Notes stays empty for them, and semantic search degrades to keyword-only) until one of those two is switched back on and the backfill catches up. The same pause arrives without anyone touching a switch when the app itself turns AI-Powered Search off after repeated graphics-driver crashes on ONNX.
Live wiki links ([[Note]], [[Note|alias]], [[Note#Heading]])
A wiki link in a note is live: it reads as a link and opens the target note. Three forms are
understood — [[Note]], [[Note|alias]] (the note is what opens; the alias stays in the text, and
showing the alias alone in place of the brackets is not built yet) and [[Note#Heading]] (resolves
on the note and keeps the heading in the text; it opens the note but does not yet scroll to that
heading). A link naming a note that does not exist is drawn in the muted unresolved style with a
dashed underline, and one click creates that note through the same path the "Create new" row uses —
the new note opens and the link starts working.
Clicking a link opens the note in a tab (Ctrl/Cmd+click does the same, for the Obsidian habit), and
the editor consumes that click, so it does not also place your cursor in the note. Only the text
[[…]] is ever linked — a bracket run inside inline code stays literal, and a malformed run
([[, [[]], a stray nested bracket) is left as plain text. Picking a row from the [[ popover
with the mouse puts the caret back in the note, so you can keep typing straight away.
Resolution uses the vault's own note index, in the same order the backlink panel's resolver uses:
the target as a path (with or without .md, any letter case), then as a title, then the text before
a #, then an accent- and case-insensitive title match when exactly one note matches; two notes
sharing a title resolve to the lowest note id. Hidden notes and other vaults are never candidates.
Every one of those comparisons standardizes the accent form first (NFC), so a note whose filename
was written by macOS — where an accented letter is stored as a base letter plus a separate mark —
resolves against the same link a precomposed name does, and appears in Backlinks. A parity test runs
the real backend resolver and the editor's resolver over one fixture vault and asserts they agree,
so the two cannot drift apart.
The link is drawn as a decoration over the text, never as a document node — so the note's text is
never rewritten by this feature. (Known gap, not this layer: the editor's markdown writer currently
escapes [[ and ]] when it saves a block it rewrote, so a saved-and-reopened note can show
\[\[Note\]\] where a plain-text reader would see escaped brackets. That belongs to the note
minimal-diff save work.)
Two save-fidelity rules ride the same pass. A wiki link inside a table cell keeps its escaped pipe
([[Note\|alias]]), because un-escaping it splits the cell and leaves the whole note unsaveable —
so an aliased link in a table is now editable like any other text. And a & in a note is written
as &, never as &, except where the ampersand would begin a valid entity (<,
&, '), which stays escaped because un-escaping it would change what the note means when
it is reopened.
Wiki-link autocomplete ([[)
Typing [[ inside the editor opens a small popover below the caret listing notes in the active
vault, best match first, up to 8 rows. Typing keeps narrowing it, and the match is fuzzy: a
misspelt title still finds its note ("invoics" finds "Invoices"), a prefix or a word inside a title
matches, and an alias from a note's frontmatter finds that note — the row always inserts the
note's real title, never the alias. The list is searched locally from the notes the vault has
already loaded, so it does not wait on a round-trip per keystroke.
The popover is keyboard-driven: Up / Down moves the highlight, Enter / Tab picks it,
Esc dismisses without inserting, and hovering a row moves the highlight so a click lands where
you expect. Picking inserts exactly [[<Title>]].
Typing # after a note name narrows the list to that note's headings, in order, filtered as you
type; picking one writes exactly [[Note#Heading]]. The popover shows nothing for a [[ with no
characters typed yet, and nothing when a # names no existing note.
When the typed text names no existing note, a Create new: <Query> row appears at the bottom of
the list. Picking it creates a fresh note in the vault root through kms:note-create, opens it as a
new tab, AND inserts [[<Title>]] into the source note — both ends of the new link land in one step.
Arrow Up / Down cycle only over real matches, never over the Create new row, so a stray Enter on a
typo cannot create a junk note. The Create new row is not offered while a # heading query is open.
Linking an AI session (@)
Typing @ at the start of a word in a note opens a list of your sessions — best match first, up to eight, each showing its current status. Keep typing to narrow the list; Up / Down moves the highlight, Enter or Tab picks one, Esc closes without inserting anything.
Picking a session inserts a link carrying its name. Clicking that link in the editor opens the session it points at. The link is an ordinary Markdown link, so it is saved into the note and still opens the right session after a reload.
Wiki-link IPC surface
kms:note-read(reused) — read once per note, only after a#, to list that note's headings. The result is cached per vault, note and note version, so repeated keystrokes cost nothing and a different vault — or a note that changed since — is never served another note's headings.kms:note-create(reused) — fires from the "Create new" row (and from clicking an unresolved link) with{ vaultId, relativePath: '<Title>.md' }. The handler may canonicalize the path (e.g.Foo.md→Foo (1).mdon collision) and the returnednote.relativePathis what the renderer opens as a new tab.kms:search-notes-by-titleis no longer used by this popover — its callers are the Mind Map "link a Vault note" picker and the Quick Launch Find Note tab, and it ranks with the same shared title ranker the[[picker uses.
Hidden-panel IPC surface
kms:list-hidden-notes— input{ vaultId, query? }→ returns{ success: true, data: { notes } }. Each row is{ id, vaultId, relativePath, title, hiddenAt }, most recently hidden first, capped atKMS_HIDDEN_LIST_LIMIT(500);querynarrows the list by title and path.kms:hide-note— input{ vaultId, noteId }→ returns{ success: true, data: { publicLinkTakenDown, warning? } }; the change arrives as akms:note-changedpush withop: updated. Stampshidden_at = ISO8601 nowonnothari_notes.kms:unhide-note— input{ vaultId, noteId }→ returns{ success: true }; the samekms:note-changedpush carries the change. Clearshidden_attoNULL.kms:note-soft-delete(reused) — handles permanent-delete from the Hidden panel. Same input shape as the file-tree Delete path:{ vaultId, relativePath }.
Unified Search modal (Phase 3 Sub-PR 3h + Phase 5 Sub-PR 5h)
A vault-scoped Command-Palette-style search modal opens from the Vault command palette (Ctrl+P while the Vault panel has focus), and on a phone from the notes drawer's search action. It returns four ranked result lists in a single IPC round-trip:
- Notes — Files (top 8). LIKE-banded match against
title + relative_path, ranked by exact-match → prefix → fuzzy → contains. Hidden notes excluded. Filter-only and word-only queries are both served: with no words typed but a filter chip present, it lists the notes the chip matches, most recently edited first. - Notes — Content (top 12). FTS5-bm25 against the note body;
snippet()wraps each hit window with<mark>markers (32-token window). Skipped when the FTS5-sanitized query is empty. - Images (Phase 5 Sub-PR 5h — top 8). FTS5-bm25 against
nothari_images_fts, which indexes AI-derivedtitle + description + ocr_text + tags_json + categoryfor every analyzed image in the vault. With no words typed,kind:imagelists the vault's analyzed images, most recently analyzed first; with no words and nokind:image, the query is skipped. Each hit carries{ sha256, vaultId, title, relativePath, snippet, rank }. Clicking an image hit opens the existing ImageLightbox (the same surface the Gallery panel opens) — no separate viewer route. - Mind Maps (top 8,
KMS_UNIFIED_SEARCH_MAPS_LIMIT). Matches against a map's title and its node text, most recently updated first, with the matching node's text as the snippet. This list only runs while the Mind Map feature is on — it islabsstatus but on by default — and it is skipped on an empty query, whenever a note-only filter is present (tag:,file:,hidden:,since:), and whenever thekind:chip asks for notes or images.
Filter chips
The query bar accepts space-separated filter tokens that the renderer parses out before sending the residual text to FTS5. Recognized chips:
tag:foo— restrict notes to those tagged#foo.file:path/segment— restrict notes byrelative_pathsubstring.hidden:true/hidden:false— include / exclude hidden notes (default excludes).since:YYYY-MM-DD— only notes whoseupdated_atis on or after the date.kind:note(Phase 5 Sub-PR 5h) — only Notes Files + Notes Content run; the Images and Mind Maps queries are skipped entirely.kind:image(Phase 5 Sub-PR 5h) — only the Images query runs; both Note sub-queries and Mind Maps are skipped.kind:mindmap— only the Mind Maps query runs. The default (nokind:chip) runs all four panes, except that any note-only chip (tag:,file:,hidden:,since:) still drops Mind Maps.
The chip enum is intentionally closed (no kind:all) — absence already means "all four". The kind chip routes which sub-queries execute on the backend. A pane that comes back with no hits draws no heading at all, so the headings you see are the panes that ran and had matches; a pane the chip skipped is simply absent from the list.
What the finder opens on, and creating from it
With the query box empty the modal lists your recent notes instead of the syntax hint: up to eight of them, most recently opened first, and a note that has never been opened placed by its last edit. It reads the note list the Vault store already holds (treeNotes), so opening the finder costs no extra query, and the arrow keys and Enter behave exactly as they do over search results: Ctrl+P then Enter reopens the note you were last in. A vault with no notes yet still gets the filter-syntax hint.
When a query matches no note and the search has finished, the list ends with a Create note "<your text>" row. Enter on it creates the note at the vault root and opens it, using the same sanitised file stem as the wiki-link [[…]] creator (note-file-name.ts), so /, : and reserved Windows names behave identically in both places, and a name already taken is auto-numbered by the create handler. The row is offered only for real words: a filter-only query such as tag:design has no bare text to name a note with.
Empty-query handling
The Files list ALWAYS runs when notes are wanted. A filter-only query — chips typed, no words — is a browse, not "nothing to search": Files lists the notes the chips match (newest-edited first) and the filter is applied in SQL as usual; an empty query with no chips short-circuits to [] inside the helper. The Content list gates on escapeFts5Query(query).length > 0 — MATCH '' is an FTS5 syntax error, so an empty FTS5-sanitized query skips the SELECT entirely. The Images list takes the same FTS5 gate, except that kind:image with no words lists the vault's analyzed images instead of skipping. The Mind Maps list returns [] on an empty query the same way, before it touches the database.
IPC channel
kms:unified-search — input { vaultId, query, filters? } where filters is { tag?, file?, hidden?, since?, kind? } and kind is 'note' | 'image' | 'mindmap'. Returns { files, content, images, maps } regardless of which panes ran — the unused panes are empty arrays.
Find Note quick-switcher
A fast "jump to any note by title" switcher, surfaced as the Find Note tab inside the Quick Launch ("Control Space") modal plus a dedicated global hotkey, default Ctrl+Shift+Space — Omniscio's in-spirit port of the standalone Nothari app's Ctrl+Shift+Space Find tab (a slice of the deferred "Phase 7 Quick Compose" idea). Distinct from the Unified Search modal above: that is the in-panel, full-text search (titles + content + images, Ctrl+P while the Vault panel is focused); this is a lightweight, title-only fuzzy navigator you can fire from anywhere on your computer — even with Omniscio backgrounded or the Vault screen never opened.
- Open it. Press
Ctrl+Shift+Space(or click the Find Note tab if you've pinned it — it's opt-in / unpinned by default). The Control Space modal opens straight to the tab. - Find + jump. An empty box lists your most-recently-edited notes (top 20, from
KMS_NOTE_LISTwhich is alreadyupdated_at DESC); typing fuzzy-matches note titles + paths (server-ranked viaKMS_SEARCH_NOTES_BY_TITLE). Arrow keys move the highlight, Enter opens the note — in the standalone KMS window when you've popped one out, otherwise the main window's Vault panel (Omniscio foregrounds the target and the note opens — cold-mount safe even if the Vault wasn't open yet), Esc closes the modal. It only navigates — it never creates or edits. - Gated by
Enable Vault. Both the tab and the hotkey only appear / register when the Vault is on; an install with the Vault off never claims the system-wideCtrl+Shift+Space. - The hotkey is rebindable. It's a fixed global hotkey (a clone of the KMS-window hotkey, NOT a per-tab Quick Launch hotkey) — change or disable it at Settings → Keyboard Shortcuts ("KMS quick find" OS-level row, next to the KMS-window row).
Related
The vault itself is the KMS page, and writing in the editor is the editor. The AI tools built on top of the vault are AI, windows and sharing.
Last verified 2026-11-13