Canonical: https://weaveos.com/integrations

[Home](https://weaveos.com/)/[Token Intelligence](https://weaveos.com/products/token-intelligence)/AI coding tool integrations: data and coverage

Data sources · Sources checked November 14, 2026

# AI coding tool integrations: data and coverage

Check whether each connected account covers the providers, costs, client activity, and repositories you need.

[Book a demo](https://weaveos.com/demo)[Read the guide ↓](https://weaveos.com/integrations#article-can-weave-track-ai-usage-without-manual-logs)

On this page

- [Can Weave track AI usage without manual logs?](https://weaveos.com/integrations#article-can-weave-track-ai-usage-without-manual-logs)
- [What each source reports](https://weaveos.com/integrations#article-what-each-source-reports)
- [Why reported cost may differ from the invoice](https://weaveos.com/integrations#article-why-reported-cost-may-differ-from-the-invoice)
- [Matching tool activity to merged code](https://weaveos.com/integrations#article-matching-tool-activity-to-merged-code)
- [Test the connection with a known user](https://weaveos.com/integrations#article-test-the-connection-with-a-known-user)
- [Router setup is separate from analytics](https://weaveos.com/integrations#article-router-setup-is-separate-from-analytics)
- [Check access before connecting accounts](https://weaveos.com/integrations#article-check-access-before-connecting-accounts)
- [Sources](https://weaveos.com/integrations#sources)

## Can Weave track AI usage without manual logs?

Weave automatically collects supported AI coding activity after you connect provider accounts or configure the coding clients your team uses. Developers do not need to log covered interactions by hand. The [AI report](https://docs.weaveos.com/reports/ai) brings those records together with connected repositories to compare tool usage, cost, and engineering output by tool, team, and engineer.

The collection paths below cover different records. Provider APIs can supply account activity or billing; client telemetry adds session detail. Account access, client installation, identity mapping, and some cost inputs still need setup.

Scroll horizontally if needed →

| Tool                                                         | Automatic collection after setup                                                                                                                                                                           | Setup and coverage to confirm                                                                                                                                                                                                                                         |
| ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Cursor](https://docs.weaveos.com/ai-tools/cursor)           | The Admin API supplies per-user activity and Cursor-billed spend. The [client plugin](https://docs.weaveos.com/ai-tools/cursor-plugin) adds session and editor activity.                                   | Admin API access requires an active Team or Enterprise plan and team admin access. The plugin works on any Cursor plan after installation. Gateway and BYOK tokens and costs need a separate gateway-log connection.                                                  |
| [Claude Code](https://docs.weaveos.com/ai-tools/claude-code) | Configured telemetry captures activity. Enterprise Analytics can provide actual per-user billed cost; Console reports provide organization cost and per-user usage estimates.                              | Match the key to the billing source. Install the [plugin](https://docs.weaveos.com/ai-tools/claude-code-plugin) in each environment for richer session detail; centrally managed telemetry settings do not install its hooks. Bedrock and Vertex billing is separate. |
| [Codex](https://docs.weaveos.com/ai-tools/codex)             | The [customer install command](https://docs.weaveos.com/ai-tools/codex-plugin) configures telemetry and hooks. Codex Analytics API credits can fill engineer-days without token telemetry where available. | Configure the plan and contract rates in Weave, restart Codex, and approve its hooks. Reported subscription cost uses configured rates or seat allocation; it is not an imported subscription invoice.                                                                |
| [GitHub Copilot](https://docs.weaveos.com/ai-tools/copilot)  | The connected GitHub App supplies supported organization usage. Compatible [Copilot Chat and CLI clients](https://docs.weaveos.com/ai-tools/copilot-plugin) can send session telemetry.                    | Organization usage APIs require Business or Enterprise. Billing needs separate access; use the spend CSV fallback when enhanced billing is unavailable. Client telemetry requires its own configuration.                                                              |

Start with a known developer: check that a recent session appears under the right person, inspect the cost-source label, and find their work in a connected repository. Then use the [AI report](https://docs.weaveos.com/reports/ai) to compare supported tool, team, and engineer views. Missing telemetry remains a coverage gap; it does not establish that a tool was unused.

## What each source reports

Connecting a provider's usage API does not necessarily give you billing data. GitHub Copilot is one example: usage reporting and enterprise billing require different permissions. Neither record tells you which code reached a merged pull request. That requires source control and a way to match the tool user to the contributor.

Weave collects data through provider APIs, configured coding clients, and source-control connections. Coverage depends on the provider plan, account, and permissions. Client telemetry also depends on which engineers and machines are configured to send it.

Scroll horizontally if needed →

| Source                                                            | Usage or activity                                                                   | Cost data                                                                                                   | Access and coverage to check                                                                                                    |
| ----------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| [Cursor](https://weaveos.com/integrations/cursor)                 | Workspace API activity; separate plugin session and edit telemetry                  | Admin API spend; account for subscription and included usage                                                | Workspace admin access for Team or Enterprise. Plugin activity is per configured engineer.                                      |
| [GitHub Copilot](https://weaveos.com/integrations/github-copilot) | GitHub organization activity; separate compatible client telemetry for Copilot Chat | Provider billing, seats, and premium requests where accessible                                              | Connect the organization or enterprise that pays. Usage access alone does not provide billing data.                             |
| Claude Code                                                       | Provider reports and configured telemetry or plugin sources                         | Enterprise analytics may provide billed per-user costs; Console reports and telemetry can provide estimates | Check the plan, key type, paying account, identity mapping, and machines sending telemetry. Cloud-provider billing is separate. |
| Codex                                                             | Configured client telemetry or plugin activity                                      | Credits at a configured rate, or token-based estimates                                                      | Check which client and account are connected. Reference-priced activity is not a ChatGPT subscription invoice.                  |
| OpenAI direct API                                                 | Provider usage at the available user or project scope                               | Token-based estimates                                                                                       | Verify the connected account and project. Negotiated adjustments may not be included.                                           |
| Devin and Windsurf                                                | Provider usage available for the connected plan                                     | Usage units at a configured rate; Windsurf can also use seat allocation                                     | Check the plan, units, and configured rate. Units do not verify an invoice.                                                     |
| Gemini CLI                                                        | Configured token and activity telemetry                                             | No native CLI dollar cost; a configured subscription can be allocated                                       | Check telemetry senders and subscription assignment. Token activity is not billed cost.                                         |
| Modal                                                             | Organization-level compute billing                                                  | Metered cost at organization scope                                                                          | Check workspace and billing account. The amount is not automatically assigned to engineers.                                     |

## Why reported cost may differ from the invoice

A token-based estimate uses observed activity and a reference price. It can help explain usage without including a subscription allowance, negotiated discount, credit, or tax. A configured seat allocation spreads a subscription cost across assigned users. Neither calculation should be presented as an invoice amount.

Weave distinguishes billed, estimated, modeled, client-reported, and allocated costs. The label matters when comparing tools. A billed per-user amount from Claude Code enterprise analytics and a Console usage estimate can have different account scopes and cost bases, even when both are expressed in dollars.

An apparently low total can also come from an unconnected second workspace, an enterprise account that pays for several organizations, or a reimbursed personal subscription. Compare the connected accounts with the invoices. The [AI coding budget guide](https://weaveos.com/use-cases/ai-coding-tool-budget) works through seats, allowances, and overages.

## Matching tool activity to merged code

A suggestion can be accepted and then deleted before commit. A commit can contain AI-assisted code even when the author has no connected tool telemetry. An open PR may never merge. These are different stages, so an activity count cannot stand in for an authorship percentage or a merged-output total.

Scroll horizontally if needed →

| Question                       | Evidence to check                                                        | What it leaves open                                    |
| ------------------------------ | ------------------------------------------------------------------------ | ------------------------------------------------------ |
| Was the tool used?             | Provider activity or configured client telemetry                         | Other clients and unconfigured machines may be missing |
| What did it cost?              | Invoice, estimate, configured rate, or seat allocation                   | Billing and activity may cover different accounts      |
| Which changes had AI evidence? | Native attribution, Git metadata, or activity-based estimates            | Keep direct, inferred, and estimated signals distinct  |
| Which work merged?             | Connected repositories, contributor identities, and merged pull requests | Repositories outside the connection are not included   |
| What happened after merge?     | Review, quality, rework, and later delivery signals                      | Activity and output alone do not show business value   |

The [AI code authorship guide](https://weaveos.com/features/ai-code-authorship) distinguishes direct tool evidence, Git co-authorship, and activity-based estimates. Preserve those distinctions when reporting attribution. A change without detected AI evidence may still have been AI-assisted.

## Test the connection with a known user

Pick a user whose tool activity and merged work you can inspect for a known period:

1. Check the latest sync for the connected provider account.
2. Find the user's activity and confirm that their tool identity maps to the correct person.
3. Compare the reported cost with the invoice for the same account and billing period. Record whether it is billed, estimated, modeled, client-reported, or allocated.
4. Find a merged PR in a connected repository. Check its author mapping and the source of any AI attribution.

If the activity appears but the PR does not, check repository scope and contributor mapping. If usage appears without cost, check billing access and the cost source. A successful connection confirms that an account is reachable; it does not confirm that every expected record is present.

## Router setup is separate from analytics

[Weave Router setup](https://weaveos.com/router/quickstart) configures where a coding client sends model requests. Analytics connections supply the activity, cost, and source-control records used in reports. Routing a client through Weave does not confirm that billing or repository data is connected. Connecting analytics does not change the client's routing configuration.

## Check access before connecting accounts

The connection flow lists the permissions requested for each source. Check them against the provider account, billing owner, and repositories you intend to include. An organization usage connection and an enterprise billing connection may need different owners to approve access.

For account-access and retention requirements, see [Weave security](https://weaveos.com/security) and involve your security owner in the setup. If you need help debugging a connection, remove API keys, prompts, source code, and account exports from screenshots or public examples.

## Sources

- [Weave Token Intelligence: supported cost and usage sources](https://weaveos.com/products/token-intelligence)
- [Weave AI ROI methodology: cost fidelity and attribution](https://weaveos.com/methodology/ai-roi)
- [Weave Cursor integration: account and plugin requirements](https://weaveos.com/integrations/cursor)
- [Weave GitHub Copilot integration: usage and billing permissions](https://weaveos.com/integrations/github-copilot)
- [Weave AI code authorship: direct, inferred, and estimated evidence](https://weaveos.com/features/ai-code-authorship)
- [Cursor documentation: Admin API, client telemetry, and gateway coverage](https://docs.weaveos.com/ai-tools/cursor)
- [Claude Code documentation: telemetry and billing sources](https://docs.weaveos.com/ai-tools/claude-code)
- [Codex documentation: client setup and configured costs](https://docs.weaveos.com/ai-tools/codex)
- [GitHub Copilot documentation: usage, billing, and CSV fallback](https://docs.weaveos.com/ai-tools/copilot)
- [Weave cost definitions: provider coverage and pricing methods](https://docs.weaveos.com/metrics/ai-tool-costs)
- [Modal documentation: metered compute and monthly billing](https://docs.weaveos.com/data-sources/modal)

## Connecting your team's tools

Review your provider accounts, billing access, and repositories with the Weave team.

[Book a demo](https://weaveos.com/demo)

## Related pages

- [Cursor data and access ↗](https://weaveos.com/integrations/cursor)
- [GitHub Copilot data and access ↗](https://weaveos.com/integrations/github-copilot)
- [AI coding tool budgets ↗](https://weaveos.com/use-cases/ai-coding-tool-budget)

On this page

- [Can Weave track AI usage without manual logs?](https://weaveos.com/integrations#article-can-weave-track-ai-usage-without-manual-logs)
- [What each source reports](https://weaveos.com/integrations#article-what-each-source-reports)
- [Why reported cost may differ from the invoice](https://weaveos.com/integrations#article-why-reported-cost-may-differ-from-the-invoice)
- [Matching tool activity to merged code](https://weaveos.com/integrations#article-matching-tool-activity-to-merged-code)
- [Test the connection with a known user](https://weaveos.com/integrations#article-test-the-connection-with-a-known-user)
- [Router setup is separate from analytics](https://weaveos.com/integrations#article-router-setup-is-separate-from-analytics)
- [Check access before connecting accounts](https://weaveos.com/integrations#article-check-access-before-connecting-accounts)
- [Sources](https://weaveos.com/integrations#sources)
