# AI Usage

The Usage tab focuses on how your team uses AI tools. It gives you a clear picture of adoption and utility.

<div align="left"><figure><img src="/files/i6rFUcNlZHRxIO4Wdr3R" alt="" width="563"><figcaption></figcaption></figure></div>

#### Adoption Rate

**Adoption Rate** represents the percentage of developers actively using the AI tool within your organization. This helps you understand how widely AI is being adopted across your teams and codebase.

You can view this metric in two ways:

* **By User** – Displays the number of active users out of the total enabled users (active in Typo) within the selected time range.
* **By Code** – Shows the proportion of code changes made using AI compared to the total code changes during the selected time period.

#### Acceptance Rate

**Acceptance Rate** measures the percentage of AI-generated suggestions that are accepted by developers. A higher acceptance rate indicates that the AI is generating relevant and useful suggestions.

You can analyze this metric in the following ways:

* **Overall** – Displays the total accepted suggestions as a percentage of all suggestions generated.
* **By Language** – Breaks down generated and accepted suggestions at the programming language level.
* **By Terminal (Claude)** – For Claude, shows the breakdown of generated and accepted suggestions at the terminal level.
* **By IDE (Copilot)** – For Copilot, displays the breakdown of generated and accepted suggestions at the IDE level.

The table at the bottom of the page provides a detailed breakdown for each team and developer, including:

* **Enabled Users:** The total number of developers who have access to the AI tool.
* **Active Users:** The number of developers who have actively used the tool in the selected time range.
* **AI Ratio:** The proportion of code generated by AI compared to code written by the developer.
* **Suggestions:** The total number of suggestions the AI has provided.
* **Acceptance Rate:** The percentage of suggestions that were accepted.


---

# Agent Instructions: 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://typo.gitbook.io/typo-help-docs/platform/ai-coding/ai-usage.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.