cursor-common-errors
Troubleshoot common Cursor IDE errors: authentication, completion, indexing, API, and performance issues. Triggers on "cursor error", "cursor not working", "cursor issue", "cursor problem", "fix cursor", "cursor crash".
Best use case
cursor-common-errors is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Troubleshoot common Cursor IDE errors: authentication, completion, indexing, API, and performance issues. Triggers on "cursor error", "cursor not working", "cursor issue", "cursor problem", "fix cursor", "cursor crash".
Teams using cursor-common-errors should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cursor-common-errors/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cursor-common-errors Compares
| Feature / Agent | cursor-common-errors | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Troubleshoot common Cursor IDE errors: authentication, completion, indexing, API, and performance issues. Triggers on "cursor error", "cursor not working", "cursor issue", "cursor problem", "fix cursor", "cursor crash".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Cursor Common Errors
Diagnostic and resolution guide for the most frequent Cursor IDE issues. Organized by error category with specific symptoms, causes, and fixes.
## Authentication Errors
### "Sign-in failed" / OAuth Loop
**Symptoms:** Browser opens for auth, redirects back, Cursor still shows "Sign In".
**Fix:**
1. Clear browser cookies for `cursor.com` and `auth.cursor.com`
2. Try incognito/private window for the OAuth flow
3. Check if browser is blocking popups from cursor.com
4. Try a different auth method (GitHub vs Google vs email)
### "License not found" / "No active subscription"
**Symptoms:** Signed in but AI features are disabled.
**Fix:**
1. Verify subscription at [cursor.com/settings](https://cursor.com/settings)
2. Confirm the email address matches your Cursor account
3. Sign out (`Cmd+Shift+P` > `Sign Out`) then sign back in
4. If on a team plan, ask admin to verify your seat is assigned
### "Session expired"
**Symptoms:** Features stop working mid-session.
**Fix:** `Cmd+Shift+P` > `Cursor: Sign Out` > Sign back in. This refreshes the auth token.
## AI Completion Errors
### Tab Suggestions Not Appearing
**Symptoms:** No ghost text while typing.
**Causes and fixes:**
| Cause | Fix |
|-------|-----|
| Tab completion disabled | `Cursor Settings` > `Tab` > enable |
| Conflicting extension (Copilot/TabNine) | Disable other completion extensions |
| File type not supported | Check file is a recognized language |
| Rate limited (Free plan) | Wait or upgrade to Pro |
| Large file (>10K lines) | Split file or use Cmd+K for specific sections |
### "Request failed" / "Model unavailable"
**Symptoms:** Chat or Composer returns an error instead of a response.
**Fix:**
1. Check [status.cursor.com](https://status.cursor.com) for outages
2. Switch to a different model (model dropdown in Chat/Composer)
3. If using BYOK, verify API key is valid and has credits
4. Try a shorter prompt (may have hit context limit)
### Poor Quality Suggestions
**Symptoms:** AI generates irrelevant, outdated, or incorrect code.
**Fix:**
1. Add context: use `@Files` to reference relevant code
2. Add project rules: create `.cursor/rules/*.mdc` with your patterns
3. Switch model: try Claude Opus or GPT-5 for complex tasks
4. Start a new chat: long conversations degrade quality
5. Be more specific: "Add Zod validation to the user endpoint" beats "fix validation"
## Indexing Errors
### "Indexing stuck" / Never Completes
**Symptoms:** Status bar shows "Indexing..." indefinitely.
**Fix:**
1. Check `.cursorignore` -- exclude `node_modules/`, `dist/`, large data files
2. `Cmd+Shift+P` > `Cursor: Resync Index`
3. Close and reopen the workspace
4. Delete index cache:
```
macOS: rm -rf ~/Library/Application\ Support/Cursor/Cache/
Linux: rm -rf ~/.config/Cursor/Cache/
```
5. Restart Cursor
### "@Codebase returns no results"
**Symptoms:** Codebase search finds nothing, even for known code.
**Fix:**
1. Wait for indexing to complete (check status bar)
2. Verify the file is not in `.cursorignore` or `.gitignore`
3. Resync the index
4. Check network connectivity (embeddings require API access)
## Performance Errors
### Cursor is Slow / Freezing
**Symptoms:** Editor lags, typing delays, UI freezes.
**Diagnosis and fixes:**
```
Step 1: Open Process Explorer
Cmd+Shift+P > "Developer: Open Process Explorer"
Identify which process uses most CPU/memory
Step 2: Extension audit
Disable extensions one-by-one to find the culprit
Common offenders: GitLens (large repos), Prettier (on save), ESLint
Step 3: Reduce indexed scope
Add large directories to .cursorignore
Step 4: Clear chat history
Long chat sessions consume memory. Start new chats frequently.
Step 5: Increase memory limit
settings.json: "files.maxMemoryForLargeFilesMB": 4096
```
### High CPU After Startup
**Symptoms:** CPU spikes for minutes after opening a project.
**Cause:** Initial indexing + extension loading.
**Fix:** Wait for indexing to complete. Add aggressive `.cursorignore` patterns. Close unused workspace folders.
## Extension Errors
### Extension Not Found / Install Failed
**Symptoms:** Extension from VS Code Marketplace not available.
**Cause:** Cursor uses Open VSX Registry, not Microsoft's marketplace.
**Fix:**
1. Search the extension on [open-vsx.org](https://open-vsx.org)
2. If not on Open VSX, download `.vsix` from VS Code Marketplace website
3. `Cmd+Shift+P` > `Extensions: Install from VSIX...`
### Extension Conflicts with AI Features
**Common conflicts:**
| Extension | Conflict | Resolution |
|-----------|----------|------------|
| GitHub Copilot | Duplicate Tab suggestions | Disable Copilot in Cursor |
| TabNine | Duplicate completions | Disable TabNine |
| IntelliCode | Suggestion conflicts | Disable IntelliCode |
| Vim | Ctrl+K/L/I conflicts | Remap AI shortcuts (see cursor-keybindings skill) |
## Network Errors
### "Connection refused" / "Timeout"
**Symptoms:** AI features fail but editor works fine.
**Fix:**
1. Check internet connectivity
2. Check if corporate firewall/proxy blocks `*.cursor.com`
3. Required domains to allowlist:
```
api.cursor.com
api2.cursor.com
auth.cursor.com
*.turbopuffer.com (for indexing)
```
4. If using VPN, try disconnecting temporarily
## Crash Recovery
### Cursor Won't Start
```bash
# Start with extensions disabled
cursor --disable-extensions
# Start with GPU disabled (Linux/Windows)
cursor --disable-gpu
# Reset to defaults (nuclear option -- backs up settings first)
# macOS:
cp -r ~/Library/Application\ Support/Cursor ~/cursor-backup
rm -rf ~/Library/Application\ Support/Cursor/Cache
rm -rf ~/Library/Application\ Support/Cursor/CachedData
```
### Recovering Unsaved Work
Cursor auto-saves by default. Check:
- `File` > `Open Recent` for recent files
- Hot exit preserves unsaved buffers between sessions
- Git reflog if changes were staged: `git reflog`
## Enterprise Considerations
- **Centralized troubleshooting**: Document common errors and fixes in team wiki
- **Proxy configuration**: Enterprise proxy settings via `settings.json`:
```json
{ "http.proxy": "http://proxy.corp.com:8080" }
```
- **Support escalation**: Business/Enterprise plans include priority support via Cursor dashboard
- **Telemetry for diagnostics**: Anonymous telemetry helps Cursor diagnose widespread issues (can be disabled)
## Resources
- [Cursor Status Page](https://status.cursor.com)
- [Cursor Community Forum](https://forum.cursor.com)
- [Cursor GitHub Issues](https://github.com/getcursor/cursor/issues)Related Skills
workhuman-common-errors
Workhuman common errors for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman common errors".
wispr-common-errors
Wispr Flow common errors for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr common errors".
windsurf-common-errors
Diagnose and fix common Windsurf IDE and Cascade errors. Use when Cascade stops working, Supercomplete fails, indexing hangs, or encountering Windsurf-specific issues. Trigger with phrases like "windsurf error", "fix windsurf", "windsurf not working", "cascade broken", "windsurf slow".
webflow-common-errors
Diagnose and fix Webflow Data API v2 errors — 400, 401, 403, 404, 409, 429, 500. Use when encountering Webflow API errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "webflow error", "fix webflow", "webflow not working", "debug webflow", "webflow 429", "webflow 401".
vercel-common-errors
Diagnose and fix common Vercel deployment and function errors. Use when encountering Vercel errors, debugging failed deployments, or troubleshooting serverless function issues. Trigger with phrases like "vercel error", "fix vercel", "vercel not working", "debug vercel", "vercel 500", "vercel build failed".
veeva-common-errors
Veeva Vault common errors for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva common errors".
vastai-common-errors
Diagnose and fix Vast.ai common errors and exceptions. Use when encountering Vast.ai errors, debugging failed instances, or troubleshooting GPU rental issues. Trigger with phrases like "vastai error", "fix vastai", "vastai not working", "debug vastai", "vastai instance failed".
twinmind-common-errors
Diagnose and fix TwinMind common errors and exceptions. Use when encountering transcription errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "twinmind error", "fix twinmind", "twinmind not working", "debug twinmind", "transcription failed".
together-common-errors
Together AI common errors for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together common errors".
techsmith-common-errors
TechSmith common errors for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith common errors".
supabase-common-errors
Diagnose and fix Supabase errors across PostgREST, PostgreSQL, Auth, Storage, and Realtime. Use when encountering error codes like PGRST301, 42501, 23505, or auth failures. Use when debugging failed queries, RLS policy violations, or HTTP 4xx/5xx responses. Trigger with "supabase error", "fix supabase", "PGRST", "supabase 403", "RLS not working", "supabase auth error", "unique constraint", "foreign key violation".
stackblitz-common-errors
Fix WebContainer and StackBlitz errors: COOP/COEP, SharedArrayBuffer, boot failures. Use when WebContainers fail to boot, embeds don't load, or processes crash inside WebContainers. Trigger: "stackblitz error", "webcontainer error", "SharedArrayBuffer not defined".