Cursor
Cursor errors and fixes
18 Cursor error messages, quoted verbatim, each with what it means, why it happens and the fix documented in official docs, maintainer replies or release notes. Verified .
All Cursor errors
- Status: Fixed in release4 fixed in release
- Status: Workaround9 workaround
- Status: By design5 by design
Agent Execution Timed OutCursor's extension host did not finish starting within 60 seconds, so Agent features could not initialize. The same root cause shows up as "Timeout waiting for EverythingProvider" in network diagnostics.Status: WorkaroundTimeout waiting for EverythingProviderShown in Cursor's network diagnostics when the extension host did not finish starting in time. Official docs state it has the same root cause as "Agent Execution Timed Out": the extension host did not start within 60 seconds.Status: Workaround<filename> is too large (4MB limit)A file attached to a Cloud Agent at cursor.com/agents exceeds the web attachment limit. Documents and images have a 4 MB per-file limit; videos have a separate 15 MB per-file limit. The browser rejects the file before upload.Status: By designCursor is damagedA macOS warning when launching Cursor. Official docs say it is a macOS issue, not a corrupted download.Status: Workaroundsuspicious activityOfficial docs: this message appears when your request is blocked as a security measure. VPNs can sometimes trigger it. (The docs quote only the phrase "suspicious activity"; the full in-app wording is not reproduced on an official page.)Status: Workaroundxcrun: error: unable to find utility "mcpbridge"The Xcode MCP integration cannot start because the system is pointed at Command Line Tools instead of the full Xcode installation.Status: Workaroundmissing tabIdentifierXcode MCP tools called from Cursor report errors about a missing tabIdentifier because some tools need a workspace context.Status: WorkaroundPrivate worker limit exceededA Cloud Agent run on Self-Hosted Machines does not start because the team hit the connected worker cap.Status: By design{"error": "Too Many Requests", "message": "Rate limit exceeded. Please try again later."}HTTP 429 from Cursor's APIs: the per-user, per-team or per-organization rate limit was exceeded. Admin and Organization API responses include Retry-After: 60 and the body {"code": "error", "message": "Rate limit exceeded"}.Status: By design{"error": "Forbidden", "message": "Enterprise access required"}HTTP 403 from Cursor's APIs: the API key is valid but lacks permission, for example calling Enterprise features on a non-Enterprise plan.Status: By design[provider] integration is not connectedIntegrationNotConnectedError from the Cursor TypeScript or Python SDK when creating a cloud agent for a repository whose source control provider is not connected to your Cursor team. The error carries provider (for example "github", "gitlab", "azure-devops") and a helpUrl.Status: By designService unavailableNetworkError from the Cursor TypeScript SDK (typical messages "Service unavailable" or "Timeout"): a transient backend issue, network partition, or exceeded deadline.Status: WorkaroundThe shell command returned no exit statusCursor CLI shell commands failed before running on a Mac self-hosted worker started with --computer-use.Status: Fixed in releaseListening for the OAuth callbackMCP OAuth login in the Cursor CLI hung on this status when the local OAuth callback port was already taken.Status: Fixed in releaseOkta FastPass requires network permissionSigning in with Okta FastPass in Cursor's built-in browser stopped at this message.Status: Fixed in releaseAuthenticating…In the Cursor CLI, queued sudo password prompts stuck on "Authenticating…".Status: Fixed in releaseValidation fails with access deniedConnecting a team's AWS Bedrock account through an IAM role fails validation with access denied (documented troubleshooting symptom).Status: WorkaroundAgent can't access repositoryCloud Agents or Bugbot cannot reach a GitHub repository through the Cursor GitHub app (documented troubleshooting symptom).Status: Workaround
New to Cursor? Start with Cursor in the tools directory.
Newsletter
Fixes for the tools you use, weekly
One email per week. New coding agent releases, what broke, and how developers are working around it.