Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Cursor error

Cursor: [provider] integration is not connected

Error message
[provider] integration is not connected

Status: By designLast verified 1 documented fix2 sources

What it means

IntegrationNotConnectedError 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.

Causes

  • Creating a cloud agent for a repo whose SCM provider isn't connected to your Cursor team.

How to fix it

  1. Fix 1.

    Open error.helpUrl (help_url in Python) to reconnect the provider, then retry.

    Snippet
    if (err instanceof IntegrationNotConnectedError) {
      console.error(err.provider, err.helpUrl);
    }

More Cursor errors

All 18 Cursor errors

FAQ

What does "[provider] integration is not connected" mean in Cursor?

IntegrationNotConnectedError 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.

How do I fix "[provider] integration is not connected"?

Open error.helpUrl (help_url in Python) to reconnect the provider, then retry.

Is this Cursor error fixed?

Status: By design. Expected behavior, not a bug. The documented fixes change the setup that triggers it.

Sources

Last verified against 2 sources: official docs, maintainer replies and release notes.

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.