What happens when the server needs the actual source code, not just its embedding?
The embedding is enough to find which chunk of code is relevant to a query, but not enough to answer a question about its contents. When the server determines a specific chunk (identified only by an obfuscated ID) is needed, it requests that chunk from the client, which sends the corresponding source over an encrypted channel. The server decrypts it for that one request and discards it again afterward — the code exists on the server only for the duration of that specific operation.
Answered in
How Cursor Indexes Your Entire Codebase Without Ever Storing Your CodeCursor's semantic search runs on embeddings, not source. The server never persists a line, and a Merkle tree keeps the index in sync as you type.
Read the full analysisOther questions this article answers
- How can Cursor answer questions about an entire codebase without storing the code?
- If embeddings are stored instead of source code, can the original code be reconstructed from them?
- Why does Cursor use a Merkle tree to keep the index synchronized instead of just re-scanning changed files?
- Why encrypt code locally before sending it, if the connection to the server is already secure?
More how ai actually works questions
- How many new researchers can receive the next OpenAI grant?
- When do applications open?
- Does the classifier make a final decision about an image?
- Can any developer call the classifier?
- How can Cursor answer questions about an entire codebase without storing the code?
- If embeddings are stored instead of source code, can the original code be reconstructed from them?
- Why does Cursor use a Merkle tree to keep the index synchronized instead of just re-scanning changed files?
- Why encrypt code locally before sending it, if the connection to the server is already secure?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the How AI Actually Works beat.