The @docs feature is great (at lest once you figure out how to use it), but how exactly is it working with regards to where the “documentation information” is being stored after indexing and also regarding the resource usage for obtaining it?
Are we using our own credits for this or is it, as I assume, and independent crawler outside of “AI stuff” doing the work at no additional cost for us as customers?
Is the information obtained stored locally on the computer where the indexing takes place?
Have not been able to find this mentioned in the docs but if I have missed it, please link to it.
Thanks.
Hey, that’s right, there are no additional costs. The documents are stored in a cached form on our servers.
1 Like
Hi, dearnie
I have one more question about the @docs
Since docs is always changing, will Cursor updates no mater built-in doc or the docs added by user, to make these docs always up to date ?
When you click on reindexing documents, they are automatically updated to the current versions.
1 Like
Is that per user/customer it is cached then? Like if we choose to index an internal but still available on the Internet API during development , we would not want that to show up for everyone etc.
Users don’t see it, it only works when the user has a specific URL.
1 Like