Provider connections

Provider connections authorize the agent to use services through your account. Start from Project setup → Connections or workspace Integrations.

Connect an accountCopy Anchor Link

1. Choose the personal or team workspace that should own the connection.
2. Select the provider and complete its authorization flow.
3. Review the connected account label and any requested permissions.
4. In the project, choose that account or inherit the workspace default.

Multiple accounts for one provider can coexist. For example, a workspace can hold two GitHub or Slack accounts, and each project can select the one it needs. A project pin takes precedence over the workspace default.

Available providersCopy Anchor Link

The connection catalog includes code hosts, project management, communication, documents, design, CRM, scheduling, deployment, and monitoring. Examples include GitHub, GitLab, Bitbucket, Linear, Jira, Slack, Notion, Google Workspace, Microsoft 365, Figma, HubSpot, Vercel, Supabase, and Sentry.

The catalog and granted provider permissions determine available operations. Connecting a service does not start a sync or authorize every possible action automatically; request the work you want the agent to perform.

Maintain a connectionCopy Anchor Link

Use the connection menu to manage the default, label, or account connection. A needs re-auth indicator means you should reauthorize it in the web app. If the agent cannot find a repository or workspace, check both the selected account and its provider-side access.

Before disconnecting an account, check which projects pin it or inherit it as their default. Choose a replacement when those projects still need the provider.

In the CLI, /integrations shows your personal connected accounts and their status; press o to manage them in the browser.