Understanding Cursor CLI Indexing for Large Codebases

Discussions
1

Hi everyone,

I’m starting to use the Cursor CLI to automate some tasks on a very large codebase. I have a few questions about how it handles context and indexing, as this is crucial for it to be effective.

I’d really appreciate it if someone could clarify:

  1. Does the Cursor CLI use the existing index created by the Cursor IDE? Or does it generate its own index when it runs?

  2. If the CLI doesn’t use indexing, how effective is it at finding bugs or handling feature requests in a large repository? I’m concerned it might lack the necessary context.

  3. If indexing isn’t a built-in feature of the CLI, are there any recommended open-source tools or workflows to help provide that deep codebase context?

Thanks for your help!

1 Like