Cursor Autocomplete Is Slow
Quick Answer
Cursor sends requests to cloud AI for completions. Network latency, large project indexing, or too many active features cause delays. Start with "Switch to a faster model" before making broader code changes.
You're in the right place if...
- !Tab completions appear after you've typed past them
- !Noticeable lag when typing
- !IDE feels sluggish
Why this happens
Cursor sends requests to cloud AI for completions. Network latency, large project indexing, or too many active features cause delays.
Fix
Switch to a faster model
Settings → Features → Copilot++ → Change model to 'cursor-fast'. This trades some quality for much better latency.
Disable unused features
Settings → Beta → disable features you don't actively use. Each feature adds background processing.
Prevent this next time
Use .cursorignore to exclude node_modules, .git, dist, and build directories from indexing.
Frequently Asked Questions
cursor-fast for completions. GPT-4o-mini for chat. Reserve Claude for complex Composer tasks.
Yes. Add a .cursorignore file to exclude large directories.
Related fixes
Weekly Newsletter
Get next week's fix before you need it.
Join developers getting weekly vibe coding tips, error fixes, and tool updates.
Subscribe on Substack →