GitHub Copilot is one of the several coding AI assistants that GitClear can instrument. Enabling Copilot Metrics opens access to GitClear's AI Impact & Correlation Stats.
linkSetting up Copilot Measurement
If you log in via GitHub, no special setup is necessary. You only need to ensure the organization/enterprise enables "Copilot Metrics," as described in the following section.
If you log in via Bitbucket, Gitlab or Azure, you'll need to ensure Copilot Metrics are enabled, and either create a token, or log in to GitClear from your GitHub account.
linkEnsuring the enterprise account has Copilot Metrics "Enabled Everywhere"
As of September 2025, we have seen mixed results for whether Github enables access to Copilot Metrics by default. To ensure Copilot Metrics are enabled,
Visit your GitHub enterprise settings: they should be of the form https://github.com/enterprises/<enterprise-slug>/settings
If you don't know your enterprise-slug, the list of enterprises you have Settings access to is available at https://github.com/settings/enterprises click the "Settings" button next to the enterprise to configure.
Click the "Policies" tab from the top row, then click "Copilot" from the left tabs, to arrive at your Enterprise "Copilot usage metrics" setting:
Confirm that Copilot Metrics API and Copilot Usage Metrics are enabled
In some subscriptions, GitHub may not enable "Enterprise" access and may configure the Copilot Metrics API through Organization settings instead. In this case, you can view the Organizations you are able to configure at https://github.com/settings/organizations. Click "Settings" next to the organization that has Copilot seats, and choose "Copilot" => "Policies" in the left sidebar.
linkEnsuring that Organization(s) allow Copilot Usage Metrics
If you have newly enabled Copilot in your Enterprise, it's a good time to confirm that you have organizations also allow Copilot and Copilot Metrics to be retrieved:
Individual GitHub organizations need to have Copilot Usage Metrics enabled
Upon activating Copilot for the Enterprise, there is usually at least one Organization automatically enabled, but if you have multiple Organizations in your Enterprise, you likely need to visit those Organizations individually to enable Copilot is enabled.
After the Organization has Copilot enabled, you must then click on Copilot => Policies and confirm that "Copilot usage metrics" is enabled for this Organization. The process is identical to enabling Copilot Metrics for the Enterprise settings.
linkGetting Copilot Metrics with Bitbucket, Gitlab or Azure repos
You have two options to get Copilot usage metrics: you can either
Log in to GitClear from your GitHub account and email support@gitclear.com with the email address for both your accounts to be connected
Create a GitHub Personal Access Token using the instructions below
The benefit of the latter is that it can be enabled immediately, but the drawback is that you either have to create a non-expiring token (which GitHub recommends against) or you have to undertake a new chore to go regenerate a token every X days.
On balance, we recommend logging in to GitHub and emailing us your two accounts to connect, but if you prefer to generate a token, read on.
linkGenerating a GitHub Personal Token to Access Copilot Metrics
A Github Personal Token (GitHub help page on the topic) can be used to generate AI Impact & Correlation Stats on GitClear.
First, on GitClear, visit your Entity's "Settings" => "AI Usage" tab.
Then, on GitHub:
Click here to create a new "Classic" token (alternately, you can view your existing tokens)
Fill out the permissions for your token, ensuring it checks the box for "Copilot"
Shown using a non-expiring token that can be deleted later by visiting GitHub Token Settings
After creating "Generate token," you should get a key of the length and prefix
ghp_XXXFGyxOsZpbdGIa4WV9KwGFIW6WIF1RXXXX
linkGetting Granular Copilot Stats
One interesting aspect of GitHub's Copilot Usage API as of Q4 2025 is that it offers two levels of granularity for its AI stats: by organization, or by team. It does not offer per-developer stats, in the manner that other AI APIs (Cursor, Anthropic, OpenAI) do.
As a consequence of GitHub's stat processing API, there is outsized benefit to synchronizing your GitHub teams to GitClear.
A one-time sync is sufficient to ensure that you'll be able to see per-team AI usage stats. However, Elite subscribers can also set up a "perpetual sync" that will, on a daily basis, synchronize your GitClear team members and repos with each team defined on GitHub.
linkCursor API Stats
Cursor offers more granular stats than GitHub Copilot. To retrieve stats from Cursor, follow Cursor's help documentation to generate an Admin API key:
Navigate to cursor.com/dashboard → Settings tab → Advanced → Admin API Keys
Click Create New API Key
Give your key a descriptive name (e.g., "Usage Dashboard Integration")
Copy the generated key immediately - you won't see it again
Format: key_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Start with "Dashboard" => "Settings":
Then scroll down the Settings page to "Advanced," where you can click the button for "New Admin API Key"
The key you copy can be pasted into GitClear's "Settings" => "AI Usage" tab.
linkClaude Code Analytics
As of early 2026, Anthropic makes it somewhat challenging to get access to your Claude Code usage stats.
Currently, Claude.ai subscriptions are separate from Claude Console.
Claude.ai is where most users interact with Claude from, and it can allow users to upgrade to subscriptions that permit access to Claude Code. But as of Q1 2026, it does not offer any path by which to generate an API token.
Claude Console is where Admin API keys can be generated, which are essential to enable access to Claude Code usage data (on GitClear or any other platform). Claude Console does not offer subscription plans - all billing is metered as pre-purchased credits.
Opus 4.5 claims that Claude.ai accounts can be connected with Claude Console accounts, but this is not documented anywhere. This page will be updated if we find a successful path by which the accounts can be linked.
In order to instrument GitClear stats, it is necessary for the enterprise to use Claude Console until Anthropic finishes creating a means for Claude.ai users to generate an Admin API key.
linkHow to determine if you are correctly set up to use Claude Code via Claude Console
Visit the Claude Console Usage page. If your Claude licenses are connected to your Anthropic Admin API key, then you should see token usage on this page:
If you see recent activity on the Claude Console usage page, then you'll be able to see your Claude Code analytics via GitClear and other data analytics products
On the other hand, if your Claude Code usage is coming from Claude.ai, you will see token activity on this page. <-- If you see recent activity on this page, then you will not see any Claude Code Analytics. Your Claude Code users are connected to Anthropic via Claude.ai. As of Q1 2026, Anthropic does not yet provide any possible way to retrieve this data from Anthropic.
If you would like Anthropic to prioritize allowing you to access your Claude Code analytics from Claude.ai, consider contacting feedback@anthropic.com or support@anthropic.com, the only published email addresses for Anthropic.