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
The Asset Browser (#68) and Scene Tree (#69) each get a local filter. There is no single place to find an asset, a node, a setting or an editor command.
Tasks
One search box (keyboard shortcut) across assets, scene nodes, components, project settings and menu commands
Providers are pluggable, so Gaya plugins add their own result kinds
Query filters (t:texture, c:Light, ref:<asset> for "what uses this") and fuzzy matching
Results act in place: open, select, ping in the browser, run the command
Acceptance Criteria
Typing part of an asset name and pressing Enter opens it; typing a command name runs it.
Gaya already has a command palette (Workbench.Chrome.cs, CommandRegistry, Shortcuts.cs, covered by GayaChromeTests). This issue is therefore about extending it into the global quick search with pluggable result providers, not creating a palette. Guinevere #109 describes the same control from the toolkit side; implement the Gaya side here and add a reusable Guinevere control only if one is needed.
Activity
brmassa commentedon Oct 13, 2026
Gaya already has a command palette (
Workbench.Chrome.cs,CommandRegistry,Shortcuts.cs, covered byGayaChromeTests). This issue is therefore about extending it into the global quick search with pluggable result providers, not creating a palette. Guinevere #109 describes the same control from the toolkit side; implement the Gaya side here and add a reusable Guinevere control only if one is needed.