Codebase does not add any files to my context

I try to add the Codebase but it is not adding any files to the context. I have checked the index and my project is indexed and yet any time I use @codebase it doesn’t add any files. Note that I use the OPENAI API key and I cannot use the reasoning step feature because I do not have access to GPT4-32k (as most people with API access do not have access to). I have tried many queries and it never adds any files to context. If I manually add the files the contextually accurate ansers are provided. This is the similar issue to: How to fix? [The model gpt-3.5-turbo does not work with your current plan or api key]

When I delete the index the code base search works fine.

I suspect that this issue is related to the models for which I have access to with OpenAI as my “reasoning” function also does not work. I suspect that these modes use models I do not have access to and fail without error.

Edit: Also, another datapoint is that OpenAI cut-off access to a bunch of models today. This feature was working on this OpenAI account yesterday but my work account it did not. Today it does not work on either account.

Any chance that this can be looked at? I’ve seen two people with two different accounts with the same issue. I suspect that no-one usint OpenAI key can do codebase references anymore. So, it should be easy to reproduce. I can delete the index and it works, sort of, but the quality really sucks. I want to roll out cursor for our company and chat with codebase is like the key selling feature. So, it would be really nice to get this working.

Same, would be super appreciated. And I don’t use my own OpenAI Api key! I did at one point, but cannot get rid of this issue for the life of me :<

Thanks for the report! Would you be able to send screenshots/screen recordings of what happens when you use @codebase? That would help us debug.

When I use indexing and request codebase I get no files in my context. Example below:
Indexed:

Output:

When I delete the index and do it again, I get a file search (which isn’t as good as the index method when looking over large, complex code bases).

Not indexed:

Output

OK… I should note that this issue was with the main release of cursor:

Version: 0.22.1
VSCode Version: 1.85.1
Commit: 20d6b2fe0f43a91764e828b77e985d1380d3ca20
Date: 2024-01-08T23:25:28.010Z
Electron: 25.9.7
ElectronBuildId: undefined
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621

When I try with the nightly release it seems it works:

Version: 0.22.0-nightly
VSCode Version: 1.85.1
Commit: ab96ed4313943a80cb4902b09b259e5b0fd001e9
Date: 2024-01-07T18:46:08.723Z
Electron: 25.9.7
ElectronBuildId: undefined
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621

I’m wondering when can I expect the fixed version to be released in a main release? If I’m doing a company wide release of an IDE, I really want to do that with the main release.

Hmmm, interesting… It doesn’t look like anything relevant to codebase indexing changed between those two releases. Perhaps it is a statefulness problem.

@arvid220u it seems to be a WSL issue. When I run the codebase reference in WSL then it doesn’t work. However, when I run it outside WSL then it works. It worked in the nightly because I couldn’t get WSL working due to some version conflict on the VS code WSL server. So, I tried it outside WSL. When I try it outside WSL with the main version it works.

Ohhh. Thank you so much for pinning it down for us!! We will put this down as a bug report and try to fix it.

1 Like

@jpoline77 Update 0.22.1-nightly fixes codebase search in WSL. Does it work for you now?

I can’t seem to run the nightly version and the regular version. I get an error when trying to start WSL with the nightly version: “Failed to connect to the remote extension host server (Error: Connection error: Client refused: version mismatch: renderer: 21465c04a600d8c53e5440723959c4715f7fd089 !== server: ecfbaf72d176819d122080bc0b8bcd76cc586e10)”

@Jakob any hints on how to get WSL working on nightly and regular at the same time?

@Jakob I tried nightly:
Version: 0.22.1-nightly
VSCode Version: 1.85.1
Commit: 21465c04a600d8c53e5440723959c4715f7fd089
Date: 2024-01-16T07:08:02.762Z
Electron: 25.9.7
ElectronBuildId: undefined
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621

I had to uninstall cursor, run "Fix WSL script " and then I could run WSL in nightly.

Even with nightly, indexing does not work still.

No, it still seems completely broken in WSL for me in version 0.32.8.