Skip to main content

Manage AI tool integrations

Connect, manage, disconnect, and troubleshoot AI tool integrations, and learn what data each provider makes available in LinearB.

Steven Silverstone
Updated by Steven Silverstone
I updated the complete article, including Edit mode, historical-data behavior, filters, error states, duplicate rules, accessible callouts, and standardized actions.

Overview

LinearB’s AI tool integrations provide one place to connect and manage external AI coding tools.

Each integration collects usage data from its provider and makes the supported metrics available in LinearB. Available data depends on the provider and connection type.

Permissions: Anyone with access to AI Tools settings can add, edit, disconnect, or reconnect an integration. No additional LinearB permission is required specifically for the Edit action.

Open AI Tool Integrations

  1. Go to Settings.
  2. Open Company Settings.
  3. Select AI Tools.
  4. Select Integrations.

The Integrations sidebar displays your configured AI tool integrations. Select an integration to view its provider, connection type, status, configuration details, and available actions.

  • Select Connected to view active integrations, including integrations that currently have a validation or collection error.
  • Select Disconnected to view integrations that were previously disconnected.
Integration names: When a provider supports multiple connection types, the sidebar identifies the configured variant. For example, it may display GitHub Copilot — Classic token or Claude Code — OpenTelemetry.

Supported Providers and Connection Types

Provider Connection types Configuration guide
GitHub Copilot Classic token
Fine-grained token
Enterprise
Choose a GitHub Copilot connection
Cursor Access token Connect Cursor to LinearB
Claude Code Admin API
Analytics API
OpenTelemetry
Choose a Claude Code connection
AWS Amazon Q Developer
Kiro
Connect Amazon Q Developer to LinearB
Connect Kiro to LinearB
AWS integrations: In LinearB, AWS is the provider. Select Amazon Q Developer or Kiro as the connection type.

Data Available by Provider

Provider Adoption and accepted lines Models, tokens, and estimated consumption
GitHub Copilot Included Included
Cursor Included Included
Claude Code Included Included
Amazon Q Developer Included Not available
Kiro Included Not available

Adoption and accepted-lines data appears in AI Analytics.

Model, token, and estimated-consumption data is available through Metrics Builder. Predefined consumption queries can be grouped by supported dimensions such as model, team, repository, or day.

Estimated consumption is not a billing total. LinearB calculates consumption using reported tokens and model pricing. Vendor plans, discounts, credits, negotiated pricing, and pricing changes can cause the estimate to differ from the provider’s invoice.

Add an AI Tool Integration

  1. Go to Settings → Company Settings → AI Tools → Integrations.
  2. Click Add New.
  3. Under Select AI provider, select the provider and click Continue.
  4. Under Connection type, select the connection method and click Continue.
  5. Under Main Settings, enter the requested credentials and configuration.
  6. Follow any provider-specific instructions displayed in LinearB.
  7. Click Connect.

LinearB validates the submitted configuration. When validation succeeds, the integration appears in the Connected list.

Note: Credentials and setup requirements vary by provider. Review the applicable configuration guide before starting.

Edit an Integration

Edit mode lets you update the available configuration fields without disconnecting the integration.

  1. Go to Settings → Company Settings → AI Tools → Integrations.
  2. Select Connected.
  3. Select the integration you want to update.
  4. Under Main Settings, click Edit.
  5. Update the available configuration fields.
  6. Click Save changes to apply the update or Cancel to discard it.
Important: A provider or connection type cannot be changed through Edit mode. To use a different provider or variant, add a new integration.
OpenTelemetry: Claude Code OpenTelemetry does not provide an Edit action for its ingest token. Use the token-rotation action when a new token is required.

What happens to historical data?

Editing an integration does not delete previously collected metrics.

  • Saving an edit may trigger LinearB to recollect a recent window of provider data.
  • Recollected records are updated in place and are not counted twice.
  • Data older than the provider’s recollection window remains unchanged.
  • The recollection window and processing time vary by provider and connection type.
Important: Updating credentials or connection settings can temporarily interrupt collection if the corresponding provider-side configuration is not also updated. Follow the instructions displayed for the selected integration.

Understand Integration Status

Connected

The integration is active and LinearB can collect data from the provider.

Connected with an error

An active integration with a validation or collection error remains under Connected and displays an error indicator. Select it to review the error and edit its configuration.

Disconnected

LinearB is no longer collecting new data through the integration. Previously collected data is preserved, and the integration remains available under Disconnected.


Disconnect an Integration

  1. Open Settings → Company Settings → AI Tools → Integrations.
  2. Select the integration in the Connected list.
  3. Click Disconnect.
  4. Review the confirmation message.
  5. Click Disconnect to confirm.

LinearB stops collecting new data and moves the integration to the Disconnected list. Previously collected data is preserved.


Reconnect an Integration

  1. Open Settings → Company Settings → AI Tools → Integrations.
  2. Select Disconnected.
  3. Select the integration you want to restore.
  4. Click Reconnect.
  5. Review the saved configuration and enter replacement credentials if required.
  6. Complete validation to restore the integration.

LinearB resumes collecting new data when validation succeeds.

Note: If the saved credentials have expired or been revoked, create replacement credentials with the provider and enter them during the reconnect flow. You do not need to create another integration.

Duplicate Integration Rules

Only one active integration using the same provider and connection type can be connected at a time.

For example, two GitHub Copilot Classic token integrations cannot be active simultaneously.

  • A failing integration still counts as active for this rule.
  • To reconnect a previous integration with the same provider and connection type, first disconnect the currently active integration.
  • A different connection type is managed as a separate integration.
Historical data: Disconnecting or replacing an integration does not delete metrics that were collected previously.

Claude Code OpenTelemetry Data

Claude Code OpenTelemetry begins sending data after OpenTelemetry is enabled and the generated managed settings are deployed to your developers.

Historical data: Claude Code OpenTelemetry does not provide historical backfill. Data collection begins after OpenTelemetry is enabled and telemetry starts reaching LinearB.

Learn more:


Troubleshooting

The Integration Shows an Error

  • Select the integration under Connected.
  • Review the error displayed in its details.
  • Confirm that the credential or token is still valid.
  • Confirm that it has the permissions required by the provider.
  • Verify organization, account, repository, AWS, and region settings as applicable.
  • Under Main Settings, click Edit, correct the configuration, and click Save changes.

Saving an edit clears the current failure status. The next validation or collection attempt determines whether the integration is working successfully.

The Integration Is Connected but No Data Appears

  • Confirm that users are actively using the connected AI tool.
  • Verify that the configured organizations, accounts, or resources cover the expected users.
  • Allow time for the provider to make usage data available.
  • Review the provider-specific collection cadence and historical backfill window.
  • For OpenTelemetry, confirm that the managed settings were deployed and approved.

An Integration Cannot Be Reconnected

  • Confirm that its saved credentials are still valid.
  • Enter replacement credentials during the reconnect flow if required.
  • Check whether another active integration uses the same provider and connection type.
  • If a duplicate is active, disconnect it before reconnecting the previous integration.

Configuration Guides


How did we do?

Choose a Claude Code connection

Contact