| ▲ | bangaladore 8 hours ago | ||||||||||||||||||||||
Nitpick: Cursor for Files makes approximately zero sense to me given what I see here. Feedback: Supporting an enterprise air gapped solution of this clearly has huge value. It really doesn't matter where the data is stored if the indexing / embedding is happening on your infrastructure. Enterprises with compliance requirements are quite likely the types of clients looking for ways to save time searching through petabytes of data. | |||||||||||||||||||||||
| ▲ | aabhay 8 hours ago | parent [-] | ||||||||||||||||||||||
I think the phrase is apt, actually, but it's not perfect: 1. We have an embedded agent that can read, edit, organize, and take actions on your files. This means it can read almost any media type, which is why it's "cursor for files" even though "isn't _cursor_, cursor for files?". In other words, Cursor is "Poly for text" :) 2. We provide you with an "IDE", I.e. a file browser. However, unlike Cursor we actually built our engine rather than relying on an existing open source one like VS Code Lastly, agree about the enterprise solution. All in due time for sure! | |||||||||||||||||||||||
| |||||||||||||||||||||||