Skip to main content

Connect integrations

Use this guide to connect the two external systems CodeTogether AI works with: source control and, on on-premises deployments, an AI analysis provider. You'll find both at Settings > Integrations. Neither is required for basic capture, but each improves what the product can tell you.

  • Deployment: SaaS, On-premises
  • Role: Owner, Admin

Only system Owners and Admins can manage integrations. GitHub is available on both deployments, but the two connect differently. An AI analysis provider is a self-service connection on on-premises only; on SaaS it is enabled by contacting sales.

Before you begin​

To connect an integration, you need all of the following:

  • Owner or Admin on the organization: Managing integrations requires one of these roles. See Roles reference.
  • For GitHub: permission to install a GitHub App in your organization. On on-premises, also permission to provision a GitHub App from a manifest.
  • For an AI provider, on-premises only: an account, a base URL, a model name, and an API key for one of the supported providers.

Connect GitHub​

CodeTogether AI captures commits, files and lines changed, branches, commit-to-push lag, and work-item flow natively, without connecting anything. Connecting GitHub is enrichment on top: it adds pull-request and merge-outcome data, so the product knows what actually merged rather than only what was pushed.

On SaaS​

CodeTogether AI provides its own GitHub App: you provision nothing and manage no credentials.

  1. Go to Settings > Integrations > Source Control.
  2. Select Connect.
  3. Choose the GitHub organization and the repositories to install the App into, then complete setup on GitHub. You're returned to the Source Control tab when it finishes.

Repository access is chosen during the GitHub App installation, not on this page. To change it, select Manage repositories on GitHub rather than disconnecting.

Screenshot

The GitHub connection card on SaaS, showing account, host, repository access, and webhook health for the connected App.

On-premises​

Each on-premises deployment provisions and owns its GitHub App, so credentials stay in your environment rather than CodeTogether's.

  1. Go to Settings > Integrations > Source Control.
  2. Select Create from Manifest to provision a GitHub App.
  3. Select Connect on the new registration to install the App.

Once provisioned, the registrations table shows each App's status, host, sync mode, and credential validity, with per-row Disconnect, Rotate credentials, and Enable or Disable actions.

On-premises Source Control tab with no customer-owned GitHub App registered yet

Settings > Integrations > Source Control on an on-premises deployment before a GitHub App is provisioned.

Both deployments​

Only GitHub is supported: no Bitbucket, GitLab, or Azure DevOps connector exists, and no issue-tracker connection is needed.

Connect an AI analysis provider​

This connection provides the model that powers CodeTogether AI's own analysis: the value point scores, the summaries, and the narrative descriptions in developer traces. Without a provider, scoring falls back to the deterministic heuristic and reads as heuristic fidelity.

On SaaS, this connection is not self-service. Contact sales to enable it as part of detailed value analysis on a Company plan.

On-premises, connect a provider yourself:

  1. Go to Settings > Integrations > AI Analysis Providers.
  2. Select a supported provider kind: Anthropic, OpenAI, Ollama, or a custom OpenAI-compatible endpoint.
  3. Set a display name, base URL, model, and API key. The key is write-only and never shown again.
  4. Select Test connection, then Activate.
Screenshot

The AI Analysis Providers tab at Settings > Integrations on an on-premises deployment, listing configured providers with their status.

You can keep several providers configured and activate or deactivate them. The provider you connect is your own account, your keys, and your spend. CodeTogether AI does not supply the model and does not train on your code or data. Usage is deliberately lightweight, so the impact on your token budget is small.

Connecting a provider is what makes full fidelity scoring possible. See Tune value points to check whether content analysis is on and adjust it.

What connecting an AI provider does not change​

Connecting a provider does not change your AI spend numbers. Token usage and AI dollar cost are captured natively from your developers' own tools and priced by a built-in catalog. The provider you connect powers CodeTogether AI's analysis, not your developers' work.

Troubleshooting​

Value points read as unavailable or heuristic​

No AI analysis provider is active, so full-fidelity scoring cannot run. On-premises: connect and activate a provider, then recalculate. SaaS: contact sales, since self-service provider connection is not available. See Tune value points.

A repository is missing from a work area picker​

Connecting GitHub narrows the repository picker to the repositories that the App grants access to. Without a connection the picker lists every known repository. Confirm the App's installation covers the repository you expect.

If this doesn't fix it​

Contact support with all of the following. Tickets missing these take longer to resolve:

  • The integration type and, for GitHub, the App's status and host from the Source Control tab.
  • For an AI provider, the provider kind and whether Test connection succeeded.
  • Your deployment kind and server version.