I have a problem for some times now with Cody. It fails to understand the projects I’m working on. It seems like it fails to properly fetch the context of these projects.
Here I’m in a very simple Nuxt.js project, when referencing the repository folder “booking-app”, Cody fetches no context for some reason and then tells me it is a Go CLI application for some reasons.
What am I doing wrong? Why is Cody not able to properly fetch the context of my app?
The main feature of Cody being that he is aware of the whole codebase of a given project, I don’t understand what is going on. Can someone explain to me why Cody is not working properly?
Your project needs to be initialized with a git repo to get indexed. Especially if they are public available.
As for the prompts you use, such general prompts are not working. The “legacy” models provided can’t execute shell commands to determine the file and folder structure of your project, nor does the prompt include symbols, like classes, functions, variables etc. to search for.
In comparison, the DeepCody model is availabel to utilize shell commands to exactly do what your prompt is likely to trigger. It will use the tree or ls -a command to look-up the project structure, finding a README file or other documentations.
Yes, I deleted the Readme file because you usually do not keep it up to date with everything going on in the project and the only reliable source of truth for that is the code itself. So I wanted to see if Cody was able to use that reliable source of truth to respond to my request
