> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-overview-and-insights.md).

# Hivel AI Impact: Overview & Insights

#### Overview

Hivel's AI Impact view draws on data from your connected AI tools - Cursor, GitHub Copilot, and Claude - to show how much of your shipped code is AI-assisted versus human-written. It surfaces patterns and trends over time, helping teams understand adoption and measure its effect on developer productivity.

**What you'll see**

* AI vs. human contribution, based on signals from integrated tools
* Aggregated trends for a clearer team-level view

#### Why teams use this view

AI tool dashboards tell you how much AI is being used. The AI Impact screen helps you connect that usage to what actually matters - how it's **influencing cycle time, throughput, review time, and other engineering metrics**.

Instead of tracking adoption in isolation, teams can start to see whether increased AI usage is translating into meaningful improvements across the board.

<div data-with-frame="true"><figure><img src="/files/q602P1tFvOnROm3Y4pQm" alt=""><figcaption></figcaption></figure></div>

#### User adoption categories

To help you quickly understand adoption at the individual level, Hivel groups users into categories based on AI usage within the selected time range.

* Inactive: 0%
* Occasional: 1–30%
* Regular: 31–70%
* Power: 71–100%

#### Trends over time

<div data-with-frame="true"><figure><img src="/files/GfNyd67QNNB1wBoMH6ja" alt=""><figcaption></figcaption></figure></div>

The screen also highlights how adoption changes over time.

* **Team AI usage trends:** understand which teams are leading adoption and where additional enablement may help.
* **Developer distribution trends:** see how usage is distributed across developers and how it shifts over time.

<div data-with-frame="true"><figure><img src="/files/OAuwv1I2DeLVPaJbwH1j" alt=""><figcaption><p>Developer distribution across categories and split of Human vs AI generated code</p></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="/files/GNuETKLEb9Txfkv7rdaX" alt=""><figcaption><p>Developer distribution trend</p></figcaption></figure></div>

***

#### **A note on Code Telemetry**

For teams with Code Telemetry enabled, Hivel also processes commit-level data to independently verify and enrich AI classification signals. If commit details have not been processed for a given PR, telemetry collection for that PR may be incomplete, which can affect classification accuracy. This is separate from the integration-based signals described above and is typically relevant for teams running advanced pipeline configurations.

<div data-with-frame="true"><figure><img src="/files/wnLJduR5yBC5N71a8IYL" alt=""><figcaption></figcaption></figure></div>

**Common questions on Code Telemetry**

*Why might Hivel show lower AI usage than other dashboards?*

In most cases, discrepancies are caused by one of the following:

1. Unmerged pull requests (only merged code is included).
2. Processing delays for very large PRs.
3. Historic data has not been synced, which can limit comparisons.

*How the confidence score is summarized*

* Code blocks within a PR are evaluated individually.
* At the PR level, the confidence score generally scales with the amount of code in the PR. In practice, larger PRs tend to yield higher confidence, while smaller PRs tend to yield lower confidence.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>More about Code Telemetry</td><td><a href="/pages/8l1IV2qM1p1LERBAcLc0">/pages/8l1IV2qM1p1LERBAcLc0</a></td></tr></tbody></table>

***

**Conclusion**

Hivel's AI Impact screen provides a practical, production-focused way to understand AI usage and impact across teams and developers - so you can scale AI tooling with clarity and confidence.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hivel.ai/ai-adoption/hivel-ai-impact-overview-and-insights.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.