GitHub Copilot usage and cost reporting in Weave

What does Weave support for GitHub Copilot?

Token Intelligence names Copilot as a native integration and includes GitHub Copilot in per-user cost reporting. The AI ROI methodology explains how these sources can be examined alongside code output, quality, and delivery.

The Connect Copilot flow distinguishes a GitHub connection from plugin telemetry. For Business and Enterprise plans, GitHub supplies organization usage context. The plugin supplies additional telemetry from configured developer machines; it does not replace billing access.

What can each type of evidence answer?

This separation matters for seat decisions. Assigned seats, active use, accepted suggestions, and reviewed changes are different measures. Choose the measure that answers the decision instead of treating any increase as a success.

How do you connect usage and session telemetry?

Open Connect Copilot, select the applicable plan or plugin option, and follow the GitHub connection or Install Weave Plugin path. The plugin option supports Copilot plans independently of the Business or Enterprise reporting connection, but requires a compatible client. Check which engineers are sending telemetry before calling that coverage organization-wide.

How do organization and enterprise billing differ?

Use Connect GitHub Copilot Spend to inspect the billing connection separately from usage:

• Organization billed on its own: connect GitHub first. The Weave GitHub App needs Administration: read, accepted by a GitHub organization owner.
• Organization billed through a GitHub Enterprise: install the Weave app on the enterprise through a GitHub enterprise owner and grant Enterprise billing: read. The organization’s spending is read from that enterprise installation rather than requiring a separate organization billing permission.
• Billing API unsupported: retain the monthly CSV import path. An unsupported billing source is not evidence of zero spending.

Only a Weave organization admin can run the connection check. A successful check starts spend syncing; it does not make data appear before the next sync. Read the displayed status and missing-permission action for the account that actually pays the bill.

Which vendor definitions should you check?

GitHub provides Copilot usage and adoption documentation and REST metric definitions. Vendor plan requirements, endpoint availability, permissions, reporting thresholds, and retention can change. Use the current documentation for the endpoint your connection actually uses.

During a Weave evaluation, confirm the connected organization or enterprise, the available date range, and the identity mapping to source control. Ask which values are per person and which remain aggregated. Access to GitHub source repositories is a separate question from access to Copilot reporting.

GitHub usage-metric permissions are distinct from billing permissions. A successful source-control or adoption connection does not establish that the billing API is accessible. Confirm each source independently and preserve the period and field definitions in your report.

How should costs and missing values be reported?

Weave labels cost sources so a vendor-billed amount can be distinguished from an estimate, modeled usage, or allocated seat cost. Reconcile the selected period with billing records and document the allocation rule used for subscriptions.

Missing usage is not necessarily zero use. It can reflect a permission gap, reporting threshold, period mismatch, or disconnected identity. Missing cost is not a free tool. Keep unavailable values distinct from observed zeros and investigate coverage before comparing teams.

Do not distribute an organization-level total across engineers or PRs without a stated rule. If the data supports only a broader comparison, retain that level of reporting.

How does Copilot usage connect to AI code authorship?

Weave distinguishes native tool evidence, commit metadata, and activity-based estimates. A direct usage metric does not prove that all code in the associated PR came from Copilot. An engineer can use several tools on the same change, so tool-level contribution counts can overlap.

Inspect a sample of commits and merged PRs. Preserve unknowns and evidence labels. Then use code output measurement and quality outcomes to understand the completed work.

What should a Copilot evaluation establish?

Choose a reporting period and one connected team. Validate the source for each metric, reconcile costs, and inspect mapped identities. Compare adoption with representative merged work, review effort, and rework.

The outcome should be a defensible renewal or rollout decision with recorded gaps. Use the AI ROI methodology for baseline design and cost-per-output interpretation before describing the result as a financial return.