Skip to content

Studio: global search and command palette #175

Open

Description

@brmassa

Current State

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.

Related

#68, #69

Activity

  1. added
    c:editorEditor: Studio, Inspector, Scene Tree, Asset Browser
    p:mediumMedium priority — fix in next sprint
    size:M~3-5 days — moderate effort
    t:featureNew feature implementation
    on Sep 25, 2026
  2. brmassa commented on Oct 13, 2026

    @brmassa
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    c:editorEditor: Studio, Inspector, Scene Tree, Asset Browserp:mediumMedium priority — fix in next sprintsize:M~3-5 days — moderate effortt:featureNew feature implementation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions