Home/By Use Case/AI for Coding: Adoption Overview
By Use Case

AI for Coding: Adoption Overview

AI coding tools have gone from novelty to default faster than almost any technology in software’s history. By 2026, 84% of developers report using or planning to use AI tools — and on stricter measures, around 90% regularly use at least one AI coding assistant at work, with roughly half reaching for AI every single day. The tool market has settled into a close three-way race: GitHub Copilot leads on raw adoption, but Cursor and Claude Code have surged to challenge it, and most developers now stack multiple tools rather than committing to one. Yet adoption and trust are moving in opposite directions. Even as usage climbs, the share of developers who trust AI output has fallen, controlled trials have questioned the real productivity gains, and platform data shows AI-assisted code shipping faster but with more incidents. This page maps the adoption curve, daily reliance, the tool landscape, and the widening gap between how much developers use AI and how much they trust it.

4 visualizations 5 sources Last updated June 2026 Free to embed
Loading chart...
Loading chart...
CHART 1 · ADOPTION CURVE

Developers using AI coding tools

AI coding tool adoption: 70% → 84% in two years

Loading chart...
Source: Stack Overflow Developer Survey 2025 (n=49,000+, 177 countries): 84% of developers use or plan to use AI tools, up from 76% in 2024 and ~70% in 2023. JetBrains’ Jan 2026 survey puts “regularly use ≥1 AI tool at work” at 90%. Adoption is now near-universal.
CHART 2 · DAILY RELIANCE

How often developers reach for AI

Daily reliance — highest among early-career devs

Loading chart...
Source: Stack Overflow 2025: 47% of all respondents — and 50.6% of professional developers — use AI tools daily; 17.7% weekly. Early-career developers lead (55.5% daily vs 47.3% experienced). Daily use, not “ever used,” is where real workflow integration shows.
CHART 3 · THE THREE-HORSE RACE

AI coding tool adoption at work

A three-horse race for AI coding tools

Loading chart...
Source: JetBrains AI Pulse (Jan 2026, 10,000+ devs): GitHub Copilot 29% work adoption, Cursor 18%, Claude Code 18% — three tools clustered close together. Copilot’s professional-developer share fell from 67% to 51% in a year (Stack Overflow) as Claude Code rose ~6x (3%→18%). Work-adoption share; tools also stack.
CHART 4 · USE VS. TRUST

Adoption is up; trust is down

Adoption is up — but trust is falling

Loading chart...
Source: Stack Overflow / DORA / METR 2025–26: only 29% of developers trust AI output accuracy — down from 40% in 2024 — and 46% actively distrust it. A METR randomized trial found experienced devs were 19% slower with AI despite feeling 20% faster, and DORA found PRs rose ~20% but incidents-per-PR rose ~23.5%. Productivity and quality are in tension.

About this data

This page compiles developer-adoption data for AI coding tools, drawing on the Stack Overflow 2025 Developer Survey (n=49,000+), JetBrains’ January 2026 AI Pulse survey (10,000+ developers), GitHub Octoverse 2025, Google’s DORA reports, the DX engineering-impact report, and METR’s randomized controlled trial.

The AI Behavior Index is the research arm of OneChat AI, an integrated multi-model AI platform. We compile and analyze data from primary research sources to make AI adoption and market trends more accessible to journalists, researchers, and decision-makers.

Why adoption figures range from 84% to 91%: they measure different populations and questions. Stack Overflow’s 84% is “use or plan to use” (so active use is lower); JetBrains’ 90% is “regularly use ≥1 tool at work”; DX’s 91% comes from organizations already on its engineering-intelligence platform (a more AI-forward sample). Tool-share figures also differ between Stack Overflow and JetBrains because of timing (Claude Code launched into the window) and sampling — the spread is the story, not any single number.

Methodology notes: survey figures come from large multi-country developer surveys; tool-share is work-adoption (a developer can use several, so shares don’t sum to 100%). The METR result is a randomized controlled trial on experienced open-source developers and may not generalize to all developers or tasks. Vendor studies (GitHub, Cursor) report larger productivity gains (50–100%) than independent ones — we lead with independent figures and flag vendor-sourced ones. The use-vs-trust gap is consistent across Stack Overflow and DORA.

Sources used on this page:

Corrections or suggestions: research@aibehaviorindex.org

For Journalists & Researchers

Use this data in your work.

Every statistic, chart, and graphic in this index is free to use and cite, with full source attribution. Can’t easily find what you need? Use our search bar to search by keyword, topic, or category.

✉️
Talk to our research team
Need a specific cut of data, an interview, or a quote? Email us — we typically respond within one business day.
research@aibehaviorindex.org →

How the data works

Every statistic shown is sourced from a publicly available study, survey, or report. We aggregate, organize, and contextualize this data — but the underlying research is conducted by the cited sources. Click any source link to access the original methodology. If you run into any issues or have a study to suggest, contact us at research@aibehaviorindex.org.