I am excited about the new version 0.50 since it seems to support indexing a multi-root workspace. However, when I really try this function, I do not observe any changes in the “Codebase Indexing” setting page after I added another folder to the current workspace. The number of synced files is unchanged. Neither “resync” nor “delete+sync” helps.
if you ask it to search for a file thats in the second repo does it work? Curious if this is a bug in indexing, or a bug in the indexing UI
Yes, I found that AI is aware of all the folders after this update. Maybe that’s a bug in the UI.
We still needed to enable it for all users in the backend, and we just did that. So your indexing UI should now reflect all your workspaces. Let us know if it doesn’t.
1 Like
I’m still seeing Cursor Agent incorrectly use the first folder path in “folders” when attempting to read files in other folders in the multi-root workspace. I’ve tried a few different “folders” layouts, and they all end up reading from the first folder path in the folders array
Are you on version 50?
Well done. In the 0.50.2 version, the codebase indexing can be observed to be functioning properly, and it gives the correct file number.
I would like to put forward a further suggestion. In the page of codebase indexing, it would be more convenient to list all the root folders that have been indexed (similar to what Augment Code does).
In Cursor:
In Augment Code:
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.