Previously, if indexing was unsuccessful, Cursor would use BM25 as a replacement for embedding. However, now, if I want to use @Codebase at chat box, I must successfully complete indexing and am required to use embedding in order to use the chat feature with @Codebase. Otherwise, I cannot use this feature.
Is it possible to use BM25 as a replacement for this requirement, like before, to chat with @Codebase?
There’s no way to use BM25 as a replacement for embeddings with @Codebase. The feature now requires successful indexing with embeddings to work properly
You can still use regular chat without indexing, but specifically for @Codebase queries, embeddings are required. This is different from the previous behavior where BM25 was used as a fallback
Check out Cursor – Codebase Indexing for more details about the current indexing requirements
@danperks Does it mean that if I don’t index my @Codebase, I can’t use this feature (@Codebase) ?
Yes, that is correct. Without a fully indexed codebase, codebase-wide features are unavailable, as they rely on the calculations that occur when indexing your code.