Skip to main content
Weave tracks GitHub Copilot in two ways: through your existing GitHub integration for organization-level usage and spend, and through the Weave plugin installation guide for per-developer Copilot Chat telemetry. The GitHub integration requires no separate Copilot connection for usage data; the plugin is an optional machine-level setup for session, prompt, tool, and edit details.
This page is GitHub usage and billing. For per-developer Copilot Chat sessions (prompts, tools, edits, AI skills), see the Copilot plugin.

​
What’s tracked

  • Copilot usage — engineers using Copilot and their activity
  • Code generation — AI-assisted code attributed via commit metadata
  • Cost tracking — per-user Copilot spend and seat cost

​
Prerequisites

  • A connected GitHub integration
  • GitHub Copilot enabled for your organization or enterprise
  • For per-user spend: admin access to GitHub billing (so Weave can read the billing usage report)
  • For per-developer session telemetry: the Weave plugin installed for each developer

​
Setup

1

Connect GitHub

Follow the GitHub integration setup if you haven’t already. Copilot usage rides on the same connection.
2

Connect Copilot billing

On Data, open the Copilot card in the AI section and use the Billing row. An admin can click Check connection. If it shows Permission needed, a GitHub organization owner grants the GitHub App Administration: read permission from Update permissions, and then you check again. A successful check enables automatic per-user billing sync, with no support ticket required.
3

Verify

Check that Copilot usage and cost appear in Weave’s AI metrics.
If GitHub reports that enhanced billing is not available for your organization, keep uploading Copilot spend via CSV on the AI ROI page (Upload → Upload Copilot spend sheet (CSV)). That remains the fallback.

​
Metrics enabled

Once connected, you can track:

​
Cost tracking

Copilot cost combines actual billed usage with seat cost:
  • Usage spend (actual) — Weave reads the GitHub billing usage report, which itemizes per-user premium/usage charges (premium requests, and AI credits under GitHub’s usage-based billing). Where GitHub reports a user’s charges directly, these are real billed amounts attributed to the engineer who incurred them. Where it doesn’t (for example, the current day, which GitHub hasn’t finalized), Weave splits the organization’s billed total across engineers by their AI credit use and marks that cost as estimated.
  • Seat cost — base Copilot seat cost. When GitHub’s billing report includes seat line items, Weave uses those; otherwise enter your Copilot subscription in Settings → Financial → Tool subscription costs (seats × cost per user).
GitHub is moving Copilot to usage-based billing (AI credits, where 1 credit = $0.01). Weave reads whatever line items GitHub reports, so both the legacy premium-request model and the AI-credit model are reflected as actual cost. Code completions and next-edit suggestions remain unbilled by GitHub and so carry no usage cost.

​
Data privacy

Weave syncs usage and billing metadata from GitHub:
  • Per-user Copilot usage and billed amounts
  • Commit metadata with AI attribution
We never access:
  • Source code content or diffs
  • Copilot’s responses
  • File paths or project structure
For per-developer Copilot Chat sessions (prompts, tools, edits, and AI skills), install the Copilot plugin. That path uses Copilot Chat’s OpenTelemetry export and does not replace this GitHub usage/billing connection.
  • Copilot plugin — per-developer Copilot Chat OTEL telemetry
  • GitHub — the integration Copilot usage and spend ride on
  • Cursor — AI IDE alternative
  • Claude Code — CLI-based AI assistant
Last modified on October 17, 2026