Cursor's stack as a mental model

You can't isolate a bug if you don't know what the layers are. Before touching anything, place the failure on a map of Cursor's stack.

This is the concept layer, so slow down before the drill. Name the mechanism first, then tie it to the role's daily decisions: what changes, what can fail and what proof would make a teammate trust the answer.

Cursor is a VS Code fork running on Electron - a desktop client with extensions and language servers, like the editor you already know. What makes it AI-native is the rest: the client talks to model backends over the network, streams LLM output back into the editor live and feeds those models context retrieved from an embedded index of your codebase. Each of those is a place bugs live and each has different evidence and a different owner.