Search

Press ⌘K to search. (On Windows and Linux, read ⌘ as Ctrl.)

Search has two modes, toggled in the search bar:

• Local — instant full-text search over titles, bodies, tags, and transcripts.
• AI — semantic search: finds notes by meaning, not wording. “Places to eat in Lisbon” finds the note titled “Restaurantes em Alfama”.

Both run entirely offline. Semantic search uses the same local multilingual embedding model as auto-linking, so it works across 50+ languages — including queries in one language matching notes written in another.

Property filters

Notes can carry typed properties, and search understands them:

status:active
priority:>=3
due:<2026-08-01

Filters combine with regular query text, e.g. roadmap status:active.

Focus mode on results

Running a search dims the canvas to just the matching notes, so results appear in their spatial context instead of a flat list. The same highlighting works inside the Cortex view — matches glow, the rest of the graph recedes.

Searching inside a note

• ⌘F — find within the open note, with match count.
• ⌘⇧F — find and replace within the note.

Search vs. the command palette

⌘K finds notes. ⌘P opens the command palette, which finds actions — every command in the app, from “Insert template” to “Ask AI to revise”. If you’re ever unsure where a feature lives, the palette is the fastest way to it.

What’s indexed

Everything you can read, the search can too: note bodies, titles, tags, callouts, table contents, footnotes — and voice transcripts, so notes you dictated are as findable as notes you typed. Resolved annotation threads stop contributing to the index; unresolved ones count. Notes in the locked Confidential group are excluded while locked.