# AI Impact Feature

Use this feature to identify patterns in AI adoption across different user segments and understand how AI coding assistants affect your team's development metrics.

### Get more from your AI tooling – the research-backed way

This feature is based on our original research about the impact of AI on engineering teams, where we followed 500+ developers for months. We combined telemetry data from real development workflows, AI tooling telemetry data, comprehensive surveys, and in-depth interviews with engineering leaders and team members. This research helps us understand not just whether AI tools are being adopted, but how they affect productivity, code quality, collaboration patterns, and developer wellbeing.

Our findings show that the actions you take as a leader have the biggest impact on the success of your AI rollout – not your tooling. With the right initiatives, you can help your team get more benefit from AI, with fewer of the costs (to codebase quality, learning, and more). But to do that, we need to be able to: 

* See what AI interventions are working and which aren’t
* Support our team members to learn – whether they’re engaged or skeptical
* Measure the full impact of AI – we don’t want to focus so much on productivity that we lose sight of code quality or the impact on developer experience
* Get early warning signs of AI slop

This feature will help you do just that. Follow the links below to learn more.

If you're curious about our original research, check out [multitudes.com/research](https://www.multitudes.com/research).

### Getting started

To get started, set up integrations with your AI tooling. The installation docs are here:

* [Claude Code](/integrations/claude-code.md)
* [Cursor](/integrations/cursor.md)
* [Github Copilot](/integrations/github-copilot.md)

We also support [Open Telemetry](/integrations/open-telemetry.md) data - so let us know if there's another OTel data source you'd like to see here!

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>AI Adoption</strong></td><td><a href="https://docs.multitudes.com/metrics-and-definitions/ai-impact-feature/ai-adoption">https://docs.multitudes.com/metrics-and-definitions/ai-impact-feature/ai-adoption</a></td></tr><tr><td><strong>AI Impact</strong></td><td><a href="https://docs.multitudes.com/metrics-and-definitions/ai-impact-feature/ai-impact">https://docs.multitudes.com/metrics-and-definitions/ai-impact-feature/ai-impact</a></td></tr></tbody></table>


---

# 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://docs.multitudes.com/metrics-and-definitions/ai-impact-feature.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.