When running IntelliJ IDEs from Windows and opening projects that are in a WSL folder Cody doesn’t seem to be able to fetch context beyond the active, open file. Other code assistants seem to handle this use case fine. Is this expected behaviour from Cody?
WSL filesystems aren’t always fully integrated with Windows-native applications. Some code assistants handle this by mirroring the WSL environment or accessing files over a network path (like \\wsl$), so Cody’s implementation may need adjustments for full WSL compatibility.
1 Like
Hello @krippakrull
If you put the @-repo chip in the chat box, Cody will not fetch relevant files inferred from your prompt, right?
Which version of Cody and IntelliJ are you using?
Do you have some example prompts to share?
Thank you
As for you first question, absolutely right! Though I’d say it isn’t able to access any files beyond the one that is active in the IDE editor window.
If I choose “Files” in the context menu that pops up when typing “@” It doesn’t find any of the files in my current repo/project.
If I choose “Current Repository” it does seem like I can choose it, but when asking the LLM about the project there is no context attached and I get answers that have nothing to do about the current project.
“Current File” works kind of as expected, but there is no additional context fetched beyond that specific file.
I am using latest nightly of Cody (7.0.19) and IntelliJ IDEA 2024.2.4. I did try Cody stable before that as well and there were no difference.
Example prompt:
