Skip to content

bug: File explorer search appears to show no results and takes a very long time for any filter #228

Description

@JKGeovision

Hello,

The file explorer search ("Search filenames and contents…") appears to never match anything when a filter is entered. Results do eventually appear, but only after a very long delay, which makes it look like no file is ever found. I suspect this is because every keystroke triggers a full content search across the entire file tree instead of a fast filename-only match.

Steps to reproduce:

  1. Navigate to the file explorer.
  2. Click into the search field ("Search filenames and contents…").
  3. Type a single character (e.g. .).
  4. Observe that the file list below stays empty while the search is running. It looks as if nothing will ever match.
  5. Wait on a reasonably large directory tree, results only show up after a very long time (tens of seconds).
  6. Repeat with a full entry such as .claude: folders, files, and content snippets do eventually appear, but with the same long delay.

Expected behavior:
Filtering should respond almost instantly, ideally matching filenames first (or entirely client-side), with the heavier full-content search only as a secondary/explicit step.

Image Image

Thanks in advance for looking into this!

Best regards,
Joshua Krimmer

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions