Bug: @ autocomplete for files with spaces requires file to be opened in VS Code first

[isCopyman]

What specific problem does this solve?

The @ file autocomplete feature does not show files with spaces in their names unless the file is first opened in a VS Code tab. This creates an inconsistent and frustrating user experience where users must manually open files before they can reference them with @.

Who is affected: All users working with files that have spaces in their names
Current behavior: Files with spaces don't appear in @ autocomplete until opened in VS Code
Expected behavior: Files with spaces should appear in @ autocomplete without requiring them to be opened first

Steps to Reproduce

1. Create a file with spaces in the name (e.g., "test file.md")
2. In Roo Code, type @test in the chat input
3. Observe that "test file.md" does not appear in the autocomplete suggestions
4. Open "test file.md" in a VS Code tab
5. Type @test again in Roo Code
6. Now "test file.md" appears in the autocomplete suggestions as "@test file.md"

Current vs Expected Behavior

Current: @ autocomplete only shows files with spaces if they are already opened in VS Code tabs
Expected: @ autocomplete should find and show files with spaces based on filename matching, regardless of whether they are opened

Related Issues

This appears to be a regression or incomplete fix related to:

• Issue Unable to add file to context if the file name has a space #2361: "Unable to add file to context if the file name has a space" (closed)
• PR bug: space in folder and file name #2767: "bug: space in folder and file name" (merged)

While the core functionality was fixed to handle spaces in filenames, the file discovery/indexing mechanism for autocomplete still seems to have limitations.

Technical Context

The issue suggests that:

• File indexing for autocomplete may prioritize or only include currently opened files
• The file discovery mechanism might not properly scan for files with spaces in project directories
• There may be a difference between the regex fixes for handling spaces and the file search/indexing logic

Impact

This forces users to adopt workarounds (opening files first) and breaks the natural workflow of referencing files directly through @.

[roomote]

I'm exploring a potential fix for the @ autocomplete issue with files containing spaces. I'll investigate why these files aren't appearing in autocomplete until they're opened in VS Code and will open a PR to share progress.

[roomote]

I've successfully implemented a fix for this issue! 🎉

Summary

The problem was that the fuzzy search algorithm in the file search functionality wasn't properly matching files with spaces when users typed partial names without spaces (e.g., typing "testfile" wouldn't match "test file with spaces.md").

Solution

I've enhanced the function to create multiple search string variations for better fuzzy matching:

• Original path and label
• Versions without spaces (for matching queries like "testfile" to "test file")
• Individual words from the path and label (for partial word matching)

Pull Request

PR #7273: #7273

The fix includes comprehensive unit tests and all CI checks are passing. Files with spaces should now appear in the @ autocomplete without needing to be opened first.

[daniel-lxs]

Hey @isCopyman Thank you for reporting this issue, unfortunately I'm unable to repro:

I'll close it for now but if you are able to reproduce it please let me know so I can reopen it.