I’m experiencing an issue with project indexing when switching between projects. While Cody can see the repository using the @ tag, it fails to retrieve any files within the project, even after forcing an update.
Specifically:
When I switch to a different project, Cody acknowledges the repository exists.
However, no files within the project are indexed or accessible to Cody.
This persists even after manually triggering an update.
This behavior is preventing me from effectively using Cody across multiple projects. Any assistance or insights into resolving this indexing problem would be greatly appreciated.
Thank you for your help!
Actually when I write “@ how many files do you see?” in chat, it responds with 2 files, but this is incorrect. There are actually more files in the project than what is shown in the limited context provided.
is not how Cody or LLMs work in general since Cody is not able to execute scripts/executables like the terminal command tree, ls or similar, Cody is not able to “count” the number of files or folders.
I mean from the chat, not as a terminal command. Usually, if the project repository is correctly indexed, Cody can see all the files in the repository, understand their context, and work with them. However, in this case, it seems not only to fail in indexing the files correctly but also to index files that don’t even exist in the project. In short, the context it provides when I open the project is completely incorrect, and I have to manually show it the relevant portions of the code each time.
