Performance and Indexing
If Cursor feels slow after opening a large project, the codebase indexer is likely still building the semantic index. Check the status bar at the bottom of the editor for indexing progress. For very large repositories (100,000+ files), exclude generated directories like node_modules, dist, build, and .git from indexing in Settings > Codebase Indexing > Exclude Patterns.
Tab completion latency depends on network speed and model server load. Auto mode selects the fastest available model by default. If completions take more than 500ms consistently, check your internet connection and try disabling VPN or proxy configurations that might add routing overhead. On resource-constrained machines (under 8 GB RAM), close unused editor tabs and disable extensions you do not actively use.
Extensions and Compatibility
Cursor supports all VS Code extensions from the marketplace. If an extension fails to load, check that it is compatible with the current VS Code engine version (visible in Help > About). Some extensions that deeply modify the editor UI may conflict with Cursor's AI overlay panels. If you encounter rendering issues, disable extensions one at a time to isolate the conflict, then report it via the GitHub issue tracker.
Imported VS Code settings occasionally contain deprecated configuration keys. If settings import causes unexpected behavior, compare your settings.json in Cursor (open via Command Palette > Preferences: Open Settings JSON) with your VS Code configuration. Remove any keys flagged as unknown. The Cursor documentation lists Cursor-specific settings that extend the standard VS Code schema.