Michael Naumov136 downloadsQuick switcher that resolves aliases in every path segment, folder notes included.
You gave a note an alias so you could find it by the name you actually call it, and you gave its folder one too. Obsidian's quick switcher honours neither the moment you type a path: Echo finds the note, but Alpha/Delta/Echo finds nothing, because the built-in matches your query against the path or against an alias and never against a mixture of the two. This plugin matches segment by segment, where each segment may be satisfied by a real name or by an alias — the note's own, or the alias on a folder's folder note.
The documentation is a demo vault. Every feature has a note that explains what it does, with a worked example you can search yourself.
Start reading here — it is plain markdown, so it works on GitHub with nothing installed.
A copy of the vault ships with every release. You can access it via any of the following:
Alias Quick Switcher: Open demo vault command.alias-quick-switcher-demo-vault.zip from the Releases. It unzips into a single alias-quick-switcher-demo-vault-<version> folder.demo-vault/ in this repository.Take Alpha/Bravo/Charlie.md, where Charlie is aliased Echo and the Bravo folder's folder note is aliased Delta. Obsidian's own switcher finds it from the first four queries and from none of the last three:
| Query | Built-in | This plugin |
|---|---|---|
Alpha/Bravo/Charlie |
✅ | ✅ |
Alpha Bravo Charlie |
✅ | ✅ |
Bravo Charlie |
✅ | ✅ |
Echo |
✅ | ✅ |
Alpha/Bravo/Echo |
❌ | ✅ |
Alpha/Delta/Charlie |
❌ | ✅ |
Alpha/Delta/Echo |
❌ | ✅ |
Folder aliases are the half nothing else does. A folder has no frontmatter, so its alias lives on its folder note — and no switcher consults it. That matters most in the vaults where it is most needed: if your folder notes all share one name, the built-in cannot reach any of them by name at all, and their aliases are the only handle you have.
It reads your existing folder-note setup rather than inventing another one. If the Folder notes plugin is installed, its live configuration decides which note belongs to a folder — including a custom name and whether the note sits inside the folder or beside it. Nothing is copied into this plugin's settings, so reconfiguring that plugin needs no migration here.
Every row tells you why it matched, in the switcher's own visual language. A hit reached through a folder alias is rendered as what you typed — Alpha/Delta/Echo — with the real path, Alpha/Bravo/Charlie, underneath it and the same alias marker Obsidian already puts on an alias hit. A row matched by real names alone shows one line, because there is nothing to explain. And a plain alias on the note itself looks exactly as it does in the built-in switcher, because it is the same row — this plugin extends that shape to the rest of the path rather than inventing a second one to learn.
A name that is not an alias says so. Turn on the Titles module of Advanced Metadata Cache and the value of each frontmatter property it lists — title by default — becomes another name a note answers to, ranked and rendered exactly as an alias is. The list lives in that plugin rather than in this one, so every plugin that reads titles agrees on it and you type title in one place. The marker on the row is what tells them apart, using Obsidian's own property icons: the alias arrow for aliases, the text glyph for a property, with the property's key in the tooltip. A row reached through both carries both markers, in the order the names appear in the path. (On a phone, touch and hold a marker for a second to see its tooltip.)
A note is found by what other notes call it, too. If a link to Bravo.md is written [Alpha](Bravo.md) or [[Bravo|Alpha]], typing Alpha finds Bravo, though nobody added Alpha to its aliases. An attachment is found the same way by the text of its embeds, such as a caption on an image, once non-markdown files are offered. These texts come from the Link texts module of Advanced Metadata Cache (version 2.4.0 or later), which is on by default. They rank below every alias and title, and the row carries a link marker with Link text in its tooltip. A setting turns them off.
Real names outrank aliases. A result matched entirely by real names ranks above one that needed an alias, so the plugin never reorders the matches you already get today. That is the default ranking; the other one treats an alias as just another name and orders purely by how well the query matched, which surfaces alias hits sooner and gives that guarantee up. Both are a setting, as is whether a segment has to match as one unbroken run or only as characters in order.
This plugin requires Advanced Metadata Cache: it loads nothing until that plugin is installed and enabled, says why, and installs it in one click. It is required rather than optional because this switcher's whole design is a lookup index, and that plugin exists to keep the vault's metadata lookups indexed. Its Titles module is off until you turn it on. Its Link texts module is on by default, so from version 2.4.0 a note is also found by the texts of the links pointing at it; an older version leaves link texts out and everything else works as before.
An Extra label property you configured in an earlier version is not lost. It is kept, and offered to Advanced Metadata Cache (version 1.1.0 or later) the next time both are loaded; you approve it in that plugin's own dialog. If you cancel, it stays kept and is offered again next time.
Assign a hotkey to Alias Quick Switcher: Open quick switcher and type a path. Obsidian's own quick switcher and its Ctrl+O are left exactly as they are — this plugin patches nothing, so you decide which of the two your muscle memory opens.
Segments are separated by / or by spaces, and a partial path works: Delta/Echo is enough.
Run Alias Quick Switcher: Add alias... on any open note, in an editor or in Reading view, or pick Add alias... from a note's menu in the file explorer. Type the alias and it is added to the note's aliases property. When text is selected in the note's editor, the prompt starts with that text. An empty value, the note's own name and an alias the note already has are refused.
Type a property term in core Search's own syntax to list the notes whose frontmatter holds a value: [isoCode:uk] finds the note with isoCode: uk, so a code never has to become an alias to be findable. Path text beside the term narrows the list: [isoCode:uk] Reference.
The same term works in a link. Type [[ and then the term, as in [[[iataCode:KBP], pick the note, and an ordinary link to it is inserted: [[Boryspil]], in your usual link format. The term itself is never written into the note, so the link keeps working in a vault that does not have this plugin. Any other link text goes to Obsidian's own link suggestions as before.
While you type a value, the values that property already holds across the vault are offered first; picking one completes the term.
| Term | Finds notes where |
|---|---|
[isoCode:uk] |
isoCode contains uk: uk, UKR |
[isoCode:"uk"] |
isoCode holds the whole word uk, not UKR |
[city:"San Miguel de Allende"] |
a value with spaces, quoted |
["birth place":Kyiv] |
a key with a space, : or ] in it, quoted (an unquoted key with a space works too) |
[quote:"say \"hi\""] |
a value with a quote in it, escaped with \ |
[langs:uk] |
any element of a list holds uk |
[location:Київ] |
a link value points to a note whose name, alias or title is Київ |
[isoCode] |
the property is there |
[empty:null] |
the property is there and empty |
[status:Draft OR Published] |
either value; parentheses group |
[status:Draft] OR [isoCode:uk] |
either term; two terms side by side must both hold |
[isoCode:/^uk$/] |
a regular expression, for a key or a value |
Matching is case-insensitive, and an unquoted key or value matches part of a word, as in core Search. Every row of this table was checked against core Search in a real Obsidian, and the plugin's test suite repeats that check on every run. The one difference is link values: core Search matches only a link's raw text ([location:Kyiv] finds [[Kyiv City]]), while this plugin also matches the names of the note the link points to. Like core Search, a term does not look inside a nested property such as address: { city: Lviv }. Two things core Search has are not supported here: parentheses around whole terms, and negating a term with -.
| Plugin | Features | How Alias Quick Switcher differs |
|---|---|---|
Another Quick Switcher |
Configurable switchers; filename/alias matches; literal folder-path text | Different matching: aliases can represent folders and appear after folder segments |
Lemons Search |
Fuzzy finder; preview; separate path and name/alias searches | Different matching: combines paths and aliases segment by segment |
Omnisearch |
Ranked full-text search; notes, PDFs and images | Different target: file paths and aliases rather than document contents |
Quick Switcher++ |
Extended switcher modes; headings, symbols, tabs and commands; property titles | Narrower switcher focus: alias-aware matching in every path segment |
Last searched for similar plugins on 2026-10-26.
The plugin is available in the official Community Plugins repository.
To install the latest beta release of this plugin (regardless if it is available in the official Community Plugins repository or not), follow these steps:
Add plugin button once and wait a few seconds for the plugin to install.By default, debug messages for this plugin (id: alias-quick-switcher) are hidden.
If you need to enable them refer to the documentation.
All notable changes to this project will be documented in the CHANGELOG.
Contributions are welcome — see CONTRIBUTING to get set up.
Open issues through the issue forms, not as blank issues.
To report a bug from inside Obsidian, run the Alias Quick Switcher: Report a bug command. It opens the bug form with the plugin version, the Obsidian version and your operating system already filled in.
Filing from the CLI or the API (gh issue create --body, or an AI agent filing for you) skips the form, and gh issue create --template cannot load an issue form. In that case, open the matching form in .github/ISSUE_TEMPLATE/, copy every field as a ### <label> heading in the form's order, and fill in each one. Always state the plugin version, the Obsidian version and your operating system.