Skip to main content

Research

The State of AI Coding Agents in 2026

Which coding agents engineers use and how fast that shifted in 2026. The 2026 Stack Overflow and JetBrains surveys cover adoption; METR measures the length of tasks frontier models finish on their own.

Reading time
6 min read
Sources
16 cited
In this piece
9 products

Key findings

  1. Claude Code and GitHub Copilot lead reported use. Of 12,255 Stack Overflow 2026 respondents, 65.5% used Claude Code and 58.7% used Copilot in the past year, ahead of OpenAI Codex at 29.5% and Cursor at 25.5%.
  2. Use shifted within months. JetBrains measured Claude Code at work rising from 18% of professional developers in January 2026 to 39% in May to July, and Codex from 3% to 16%. GitHub Copilot fell to 21%, from 29% a year earlier.
  3. On METR's task suite, the length of task a frontier model completes half the time has doubled about every 129 days since 2023. It grew from 4 minutes for GPT-4 to about 12 hours for Claude Opus 4.6 in February 2026.
  4. Trust stays conditional. Only 6.6% of Stack Overflow 2026 respondents trust AI output with important work decisions, and 76.5% run AI output locally before they use it.

Claude Code leads coding agent use at work in 2026, and engineers still check agent output by hand before they trust it. Agents are now the main way developers use AI at work. In Stack Overflow's 2026 survey, 65.9% of respondents use a coding assistant or agent at work, and JetBrains finds 90% of professional developers use agents at least weekly. Write your review and permission rules now, because they apply whichever agent your engineers pick next quarter.

Who uses which agent

Claude Code and GitHub Copilot sit far ahead of the rest, with Cursor and Codex in a second group. Stack Overflow asked respondents which coding agents or assistants they had used over the past year. Most named more than one, so the shares add up to well over 100%.

Stack Overflow draws its sample from its own community and does not reweight it, so its shares measure reach among engaged developers. JetBrains reweights its survey to the global developer population and finds the same leader. In May to July 2026, 39% of professional developers used Claude Code at work, and 47% in the United States.

Figure 1Coding agents and assistants used in the past year
ProductShare of respondents
Claude Code65.5%
GitHub Copilot58.7%
OpenAI Codex29.5%
Cursor25.5%
Google Antigravity16%
Gemini Code Assist14.6%
Windsurf (now Devin Desktop)6.5%
Cline4.5%
Devin2.9%

Stack Overflow Developer Survey 2026, n = 12,255 respondents to the coding agent question, fielded June 23 to August 5, 2026, published October 6, 2026. Multiple answers allowed.

How fast the market moved in 2026

Claude Code more than doubled its share of developers using it at work between January and mid-2026, and Codex grew fivefold. Cursor and GitHub Copilot lost share. JetBrains asked the same question twice, in its January AI Pulse survey and in its Developer Ecosystem Survey from May to July.

Two products changed shape during the year. On June 18, 2026, Gemini CLI stopped serving Google AI Pro and Ultra subscribers and free Gemini Code Assist users, who move to Antigravity CLI. Gemini Code Assist Standard and Enterprise customers keep their access. Windsurf became Devin Desktop on June 2, 2026, with plans and pricing unchanged, and Devin's Pro, Max, and Teams full seats now include it.

Figure 2Professional developers using each tool at work, JetBrains, January and May to July 2026
ProductJanuary 2026May to July 2026
Claude Code18%39%
GitHub Copilot29%21%
Codex3%16%
Cursor18%12%
JetBrains AI (AI Assistant and Junie)11%9%
OpenCode7%
Google Antigravity6%6%

JetBrains Research. January 2026: AI Pulse, 10,000+ professional developers. May to July 2026: Developer Ecosystem Survey 2026, 15,000+ professional developers, reweighted by region, employment, language, and familiarity with JetBrains products.

How much work an agent finishes on its own

A model's time horizon, in METR's measure, is the length of task it completes half the time, with each task timed by how long human experts take. On version 1.1 of METR's task suite the frontier horizon has doubled roughly every 129 days since 2023 (95% interval 104 to 158 days). Claude Opus 4.6 reached about 12 hours in February 2026, with a wide interval of 5.3 to 60.6 hours.

The newest models have outgrown the suite, and METR now reports them in its evaluation write-ups. METR states that measurements above 16 hours are unreliable on the current suite, and it stopped updating its horizon page on September 8, 2026. In its May 2026 Frontier Risk Report, the most capable model shared with METR had a point estimate past that limit and below 20 hours. For GPT-5.6 Sol in June 2026, METR's standard method gives about 11.3 hours (95% interval 5 to 40 hours). METR does not treat that figure as a reliable measurement, because the model cheated on tasks more often than any public model it had tested. For Claude Opus 5.5 in September 2026, METR used five AI research tasks in place of a time horizon.

A horizon counts tasks that pass automated checks, which is a lower bar than review. In METR's March 2026 review, repository maintainers would not have merged roughly half of the test-passing pull requests agents wrote.

Figure 350% time horizon of frontier models on METR's Time Horizon 1.1 suite
ModelReleaseTime horizon
GPT-4Mar 20234 min
Claude 3.7 SonnetFeb 202560.4 min
o3Apr 2025119.7 min
GPT-5Aug 2025203 min
Claude Opus 4.5Nov 2025293 min
GPT-5.2Dec 2025352.2 min
Claude Opus 4.6Feb 2026718.8 min
Claude Mythos Preview (early)Apr 20261,044.8 min

METR Time Horizon 1.1 benchmark results, frontier models only, as of METR's last page update. METR treats values above 960 minutes as unreliable.

What engineers still check by hand

Developers trust agents with work they can verify. In Stack Overflow's 2026 survey, 48.0% of 14,304 respondents trust AI output when they can easily verify it, 16.3% only for low-risk tasks, and 6.6% for important work decisions. Asked how well AI handles complex tasks, 16.0% said very well and 38.8% good but not great.

Agents already write a large share of code. JetBrains' 2026 survey estimates that developers have agents write about 47% of their code outright, and that about 22% of developers rely on agents for more than 80% of it. The larger that share, the more each of the checks below matters.

Figure 4What developers do before using an AI-generated answer
StepShare of respondents
Run it locally76.5%
Compare against codebase context63.9%
Inspect tests and security implications53%
Read official documentation38%
Search Stack Overflow12.2%
Use it as-is9.6%

Stack Overflow Developer Survey 2026, n = 13,162. Multiple answers allowed.

How organizations govern agent use

Most organizations have not set a policy. In Stack Overflow's 2026 survey, 29.7% of respondents say AI use is optional and left to individuals, 24.0% work with approved tools and written guidance. Also, 10.2% are measured on AI use in performance reviews. On tooling, 32.8% use a few approved tools and 18.6% mostly one.

An organization without approved tools still runs agents, under each engineer's personal plan and data terms. Decide which plans your engineers use, which permissions agents get by default, and who reviews agent output before usage grows further.

Figure 5How AI tools or agents are used at respondents' organizations
How the organization treats AIShare of respondents
Optional, left to individuals29.7%
Approved tools and guidance24%
Encouraged by some teams, practices vary15.9%
Expected for some types of work11.5%
Measured in performance reviews10.2%
Not used for work6.1%
Not sure2.6%

Stack Overflow Developer Survey 2026, n = 13,167.

Methodology

Survey figures come from the Stack Overflow Developer Survey 2026 (30,903 valid responses, fielded June 23 to August 5, 2026) and JetBrains Research's 2026 survey posts, each with its n and window. Stack Overflow's respondents select themselves from its community, and JetBrains reweights its sample. Time horizons come from METR's Time Horizon 1.1 data and its 2026 evaluation reports, and product changes from the vendors' own pages. Every figure is its publisher's own, linked under Sources.

Products in this piece

Sources

Public source
12
Official documentation
4
  1. Stack Overflow: The results of the 2026 Developer Survey are here (Oct 6, 2026)Public sourcestackoverflow.blog
  2. Stack Overflow Developer Survey 2026: Methodology (30,903 responses, fielded Jun 23 to Aug 5, 2026)Public sourcesurvey.stackoverflow.co
  3. Stack Overflow Developer Survey 2026: AI, full data (published Oct 6, 2026)Public sourcesurvey.stackoverflow.co
  4. JetBrains Research: AI Coding Agents, Adoption Trends (Developer Ecosystem Survey 2026, Aug 2026)Public sourceblog.jetbrains.com
  5. JetBrains Research: Which AI Coding Tools Do Developers Actually Use at Work? (AI Pulse, Apr 2026)Public sourceblog.jetbrains.com
  6. JetBrains Research: How Much Code Do Developers Really Let Agents Write? (Aug 2026)Public sourceblog.jetbrains.com
  7. METR: Task-Completion Time Horizons of Frontier AI Models (Time Horizon 1.1, last updated Sep 8, 2026)Public sourcemetr.org
  8. METR: Time Horizon 1.1 benchmark results (data file, last updated Sep 8, 2026)Public sourcemetr.org
  9. METR: Many SWE-bench-Passing PRs Would Not Be Merged into Main (Mar 10, 2026)Public sourcemetr.org
  10. METR: Frontier Risk Report, February to March 2026 (May 19, 2026)Public sourcemetr.org
  11. METR: Summary of METR's predeployment evaluation of GPT-5.6 Sol (Jun 26, 2026)Public sourcemetr.org
  12. METR: Summary of METR's predeployment evaluation of Claude Opus 5.5 (Sep 22, 2026)Public sourcemetr.org
  13. Google Developers Blog: Transitioning Gemini CLI to Antigravity CLI (May 19, 2026)Official documentationdevelopers.googleblog.com
  14. Gemini CLI docs: Quota and pricingOfficial documentationgeminicli.com
  15. Devin docs: Self-serve plansOfficial documentationdocs.devin.ai
  16. Devin Desktop docs: FAQ on the move from WindsurfOfficial documentationdocs.devin.ai