No longer able to chat with codebase on Windows

Support Bug Reports
1

My codebase is fully indexed and synced. In the past week whenever I’ve tried to chat with the codebase either through pressing Ctrl + Enter or manually clicking the button, it will say that it’s reading the files but obviously it doesn’t since no files are listed as having been read, and I get an instant response that has nothing to do with the codebase. I’m not sure what to do here as I’ve already tried uninstalling and reinstalling Cursor to no avail. I’ve also tried manually @ing Codebase in my question but still that doesn’t work.

EDIT: So I just tested it out with a different (though significantly smaller codebase) and it works fine with that one. Could it have something to do with the size of the codebase? I don’t think that’s the case because I’ve been working on that codebase with Cursor for a year now with no problems at all.

EDIT 2: Tried cloning my codebase to another folder and letting Cursor index that one all over again but I get the same problem of the codebase not being used as a context. I’m able to use individual files as context but not the whole codebase.

4

I’m able to access https://repo42.cursor.sh/ from my computer.

image
image780×254 7.93 KB

And this is the output I get when I try to chat with codebase.

6

These are the logs I get when I resync my index:

2024-10-17 03:09:58.748 [info] Setting indexing intent to should-index
2024-10-17 03:09:58.749 [info] Creating merkle client.
2024-10-17 03:09:58.750 [info] Done creating merkle client.
2024-10-17 03:09:58.750 [info] Doing a startup handshake.
2024-10-17 03:09:59.583 [info] Finished initializing merkle tree in 828.2601000000141 ms.
2024-10-17 03:09:59.585 [info] Doing the initial handshake with hash: d80e860fdb7162dadf97b40301ed289d3622c122529dacb07175788a187d5739
2024-10-17 03:09:59.585 [info] Handshake start
2024-10-17 03:09:59.748 [info] Handshake timing: 163.30139999999665
2024-10-17 03:09:59.749 [info] Handshake result: {"status":"STATUS_UP_TO_DATE","repoName":"00048e5b-36c5-472b-b0ce-6d4fa9e7a243"}
2024-10-17 03:09:59.750 [info] Starting fast remote sync.
2024-10-17 03:09:59.752 [info] Total num embeddable files: 3091
2024-10-17 03:09:59.752 [info] Root hash: d80e860fdb7162dadf97b40301ed289d3622c122529dacb07175788a187d5739
2024-10-17 03:09:59.753 [info] Finished indexing repository.
2024-10-17 03:09:59.753 [info] Indexing job successfully done or aborted.
7

Hi @kabahaly

It’s possible that your codebase contains many packages, like node_modules and similar. Restrict access to those from your project, and to anything else you think is necessary.

8

I tried to do that but either I didn’t get the syntax right for how to restrict access or something went wrong. I’ll try again later and report back. My question is, how come size wasn’t a problem before?

9

Unfortunately this worked. I say unfortunately because I’d much rather it be able to index the entire codebase as it was before. Hopefully there is a fix for this if it isn’t intentional.