Skip to content

Fuzzy file search does not work correctly on Windows #1374

Closed

Description

@klonuo

Hi,

if I run version of opencode under WSL in Windows Terminal, everything is as expected, i.e.:

Image

but when I use Powershell, fuzzy search doesn't find any file in the same project location:

Image

Maybe it's because of backslash as path separator under Windows, maybe something else.

BTW fzf under Windows works as expected (rg --files | fzf):

Image

Activity

  1. raffaelemancuso commented on Aug 4, 2025

    @raffaelemancuso

    but under Windows Powershell,

    Are you using the modern terminal like WezTerm and Lacritty as the documentation suggest?

  2. klonuo commented on Aug 4, 2025

    @klonuo
    Author

    @raffaem No, it's Windows Terminal, and it's same in wezterm (it's not realistic to insist on using specific terminal). Just noticed your issue today posted #1583

    When I type@ key, I see this file listing, but if I type any letter I get "no matching results".
    If I manually type the path, for example as in my case reported above @src\utils\conn.py the model understands the location, and can read the file

  3. adirizka7 commented on Sep 27, 2025

    @adirizka7

    similar case on my windows machine, there is only @agent available.

    Image
  4. klonuo commented on Oct 2, 2025

    @klonuo
    Author

    @adamdotdevin This is now fixed as of 0.14

  5. klonuo commented on Oct 2, 2025

    @klonuo
    Author

    However just listing works but it can't read the file path afterwards as reported here: #1583

  6. rekram1-node commented on Oct 2, 2025

    @rekram1-node
    Collaborator

    I think @itsrainingmani is working on a fix

  7. itsrainingmani commented on Oct 3, 2025

    @itsrainingmani
    Contributor

    ^ Yes with the new ripgrep & file search update, I'm working on retesting & re-implementing my prior fix. Should be done hopefully by tomorrow 🫡

  8. giansalex commented on Oct 4, 2025

    @giansalex

    I got same error in powershell, git bash and alacritty.

    it tries to find path:
    /C:/Users/USER/Documents/..., but valid path should be:
    /C/Users/USER/Documents/... (removed :)

  9. itsrainingmani commented on Oct 5, 2025

    @itsrainingmani
    Contributor

    On the latest build, I don't notice any fuzzy search issues anymore. Are you on the latest version?

  10. giansalex commented on Oct 5, 2025

    @giansalex

    using v14.0.3 , i got this error #1583 , does not use a correct path to read the file

  11. itsrainingmani commented on Oct 5, 2025

    @itsrainingmani
    Contributor

    gotcha. we just merged a PR addressing that. should be fixed in the next release hopefully!

  12. klonuo commented on Oct 7, 2025

    @klonuo
    Author

    works in 14.0.4!

  13. rekram1-node commented on Oct 7, 2025

    @rekram1-node
    Collaborator

    good to close then?

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

Metadata

Metadata

Assignees

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