The Coding Singularity Is Real — and Steeper Than Clark Presented

📊 Full opportunity report: The Coding Singularity Is Real — and Steeper Than Clark Presented on ThorstenMeyerAI.com — validation score, market gap, and execution plan.

TL;DR

AI systems now code at near-human levels for routine tasks, with capabilities expanding faster than earlier forecasts. The recursive self-improvement loop suggests the coding singularity is imminent, but deployment across complex real-world projects remains uncertain.

Recent data confirms that AI systems’ coding capabilities have advanced more rapidly than previously estimated, pushing closer to the so-called ‘coding singularity’—a point where AI-driven code generation becomes self-improving and runaway.

Thorsten Meyer reports that the capabilities of AI coding models, particularly as measured by SWE-Bench and METR time horizons, have improved substantially since Clark’s May 2026 analysis. SWE-Bench scores show models like Mythos Preview reaching 93.9% on routine coding tasks, indicating near-human performance on specific benchmarks. Meanwhile, METR data reveals that the time horizon for AI to generate functional code has shrunk from 12 hours in early 2026 to an expected median of 24 hours by year’s end, with some forecasts suggesting it could be as low as 15 hours.

The core argument is that the rapid improvement in coding ability is not just about better code generation but about the emergence of a recursive self-improvement loop—where AI systems improve their own capabilities faster, leading to an inflection point in AI development. Clark’s initial framing suggested a gradual approach, but recent data indicates the process is steeper and happening sooner than he projected.

The Coding Singularity Is Real — and Steeper Than Clark Presented
DISPATCH / MAY 2026 CLARK EXTENDED · CODING SINGULARITY · THE OUTSIDE READ
▲ The Outside Read Coding Singularity · May 2026
The Coding Singularity · Read From Outside the Frontier Lab

The coding singularity is real —
and steeper than Clark presented.

Clark’s data is accurate. The trajectory is plausibly steeper. The deployment is bifurcated. The labor consequence is empirical. The substance is recursive self-improvement.

Jack Clark’s Import AI #455 has a section called “The coding singularity – capabilities over time” that does the heavy lifting for his automated AI R&D thesis. This is the read on Clark’s section from outside the frontier lab. The headline finding: the capability data is real and possibly understated, the deployment reality is more bifurcated than “everyone codes through AI” suggests, and the substantive event is not the coding part — it’s the opening of the recursive self-improvement loop the coding capability makes operational.

codeAI R&Drecursion The wedge · The mechanism · The singularity
The structural read
“Coding singularity” is the right name. Coding is the wedge. The thing on the other side of the wedge is automated AI R&D. The substantive event is recursive self-improvement, which the coding capability makes operational.
93.9%
SWE-Bench Verified · Claude Mythos Preview
From ~2% Claude 2 in late 2023 · ~47× in 30 months
16+ hr
METR 50% time horizon · Mythos Preview · May 8 2026
“Measurements above 16 hrs unreliable with current task suite”
4.3mo
Post-2023 doubling time · METR 1.1 methodology
Faster than Clark’s 7-month figure · 20% steeper curve
−20%
Software dev employment · ages 22-25 · Stanford
From late-2022 peak · age-inverted hiring · empirical
SWE-BENCH 2% → 93.9% IN 30 MONTHS · MYTHOS PREVIEW SATURATING THE BENCHMARK METR 30s → 12hr → 16+hr IN 4 YEARS · TASK SUITE BEING OUT-GROWN BY THE MODELS CURVE STEEPENING POST-2023 DOUBLING TIME RECALCULATED TO 4.3 MONTHS · COTRA REVISED UP DEPLOYMENT 74% GLOBAL DEV ADOPTION · CLAUDE CODE $2.5B RUN-RATE · CURSOR $1.2B ARR LABOR MARKET JUNIOR POSTINGS DOWN 40-50% · STANFORD 22-25 EMPLOYMENT −20% THE STRUCTURAL READ CODING IS THE WEDGE · RECURSION IS THE SINGULARITY SWE-BENCH 2% → 93.9% IN 30 MONTHS · MYTHOS PREVIEW SATURATING THE BENCHMARK METR 30s → 12hr → 16+hr IN 4 YEARS · TASK SUITE BEING OUT-GROWN
The capability data · confirmed and updated

Clark’s numbers check out. Post-publication data is sharper.

Both benchmark trajectories Clark cites are publicly verifiable. Both have moved meaningfully in the week since Import AI #455 was published. The trajectory is plausibly steeper than the essay presents.

The two capability charts · post-publication state
SWE-Bench at saturation noise floor; METR running out of measurement headroom.
▲ FIG. 01A · SWE-BENCH VERIFIED
Real GitHub issues · saturating
Late 2023 · Claude 2~2%
Dec 2025 · Opus 4.580.9%
Apr 2026 · GPT-5.3 Codex85.0%
Apr 2026 · Opus 4.787.6%
May 2026 · Mythos Preview93.9%
Update Clark doesn’t include: on SWE-Bench Pro (harder problems), Mythos 77.8%, Opus 4.6 53.4%, GPT-5.4 57.7%. The gap widens substantially as task difficulty rises. Private-codebase subset drops scores another 5-10 points.
▲ FIG. 01B · METR TIME HORIZONS
50% reliability task duration · out-growing the suite
2022 · GPT-3.5~30 sec
2023 · GPT-4~4 min
2024 · o1~40 min
2025 · GPT-5.2 (High)~6 hr
Feb 2026 · Opus 4.6 (corrected)~12 hr
May 8 2026 · Mythos Preview≥16 hr
End 2026 · Cotra revised median~24 hr
METR 1.1 update: post-2023 doubling time recalculated to 130.8 days (4.3 months) — 20% faster than Clark’s 7-month figure. “Measurements above 16 hours are unreliable with current task suite.” The measurement instrument is the rate-limiter.
The curve is steeper than Clark presented. And the measurement is the rate-limiter.
The deployment reality · outside the frontier lab
Amazon

AI coding assistant software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Five-tool consolidated stack. Bifurcated by segment.

Clark: “frontier-lab researchers code entirely through AI systems.” Correct for frontier labs. Partially correct across the broader market — with substantial segment-level variance. The Cambrian explosion of 2024 has consolidated to five production-grade tools.

The five-tool consolidated stack · May 2026
Concentrated oligopoly with strong brand moats, high switching costs, and platform-grade revenue.
Claude CodeAnthropic · terminal-native
MCP-deep terminal agent. Strongest on hard tasks. The senior-engineer surface. CSAT 91%, NPS 54.
$2.5Brun-rate
18% global
24% US/CA
CursorAnysphere · IDE-native
VS Code fork with Composer 2. The default IDE agent. Credit-based billing the persistent complaint.
$1.2BARR
18% global
50%+ F500
GitHub CopilotMicrosoft · multi-model since Feb
Widest reach, slowest growth. Enterprise default. Now backs Claude + Codex in addition to GPT.
$$$est large
29% global
40% large ent
OpenAI CodexGPT-5.5 · post-Windsurf rebrand
Cloud-task-runner pattern. Async delegation surface. Acquired Windsurf for ~$3B in late 2025.
growing2026
~60% of
Cursor usage
DevinCognition · async autonomous
Most autonomous. Submit task → return PR. Highest demand on review discipline. $20 + $2.25/ACU.
nichegrowing
~5-10%
professional
Adoption by segment · the bifurcation
Frontier labs (Anthropic, OpenAI, DeepMind)
~100%
AI-native startups + Bay Area tech
~90%
Big tech (FAANG-adjacent)
60-75%
Mid-market enterprise
40-55%
Regulated industries (health/finance/gov)
15-35%
Long-tail enterprise + small IT shops
10-25%
The labor market consequence · observable, not theoretical
Amazon

machine learning development tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Stanford data confirms what Clark’s data implies.

Junior software engineering postings down 40-50% since 2024. Age-inverted hiring relative to historical software engineering patterns. The data is unambiguous on the entry-level segment. The longer-term consequences are unresolved.

The labor market data · current as of May 2026
Total dev employment up moderately; composition shifted toward mid-career and senior workers.
−40 to −50%
Junior dev postings since 2024
Junior dev job postings on major platforms. Some companies eliminated the role entirely. Bootcamp placement rates have cratered. CS graduates taking significantly longer to find first roles.
Source · multiple platforms · aggregated
−50%
Big Tech fresh-grad hiring 3-year decline
Big Tech hired 50% fewer fresh graduates over 2022-2024 than prior three years. Companies adopting AI cut junior dev hiring 9-10% within six quarters. Pattern is statistically robust.
Source · Harvard research · SignalFire
6.1 / 7.5%
CS / CompEng graduate unemployment
Computer science 6.1% · computer engineering 7.5%. Higher than fine arts (3%), nursing (1.4%), elementary education (1.8%), civil engineering (1%). CS unemployment was below 3% for most of the prior decade.
Source · Federal Reserve · 2025
−6 / +9%
Age-inverted hiring 22-25 vs 35-49
AI-exposure occupations: 22-25 cohort employment −6%, 35-49 cohort +9%. Software engineering historically favored younger workers. Now older workers gaining hiring share. Stanford 22-25 dev employment −20% from late-2022 peak.
Source · Stanford Digital Economy Lab
The structural read · coding is the wedge
Amazon

AI programming IDE

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

“Coding singularity” is the right name.

Clark calls it “the coding singularity.” The phrase is correct. The framing implies the significance is about coding. The actual significance is what the coding capability enables. Coding is the wedge. The thing on the other side is the singularity.

The recursive loop · what the coding singularity opens
Same capability that produces SWE-Bench saturation is the capability that produces automated AI R&D.
automates produces trains LOOP code SWE-BENCH 93.9% AI R&D METR 16+ HR HORIZON recursion SUCCESSOR TRAINS SUCCESSOR code’ NEXT GEN · BETTER the singularity RECURSIVE SELF-IMPROVEMENT

SWE-Bench saturating means the broader AI engineering capability has reached saturation. AI R&D is engineering with model training as the target output. The coding singularity is what you see. The recursive self-improvement loop is what you are looking at.

What this means · five audiences
Amazon

automated code generation tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Five audiences. Five different obligations.

The coding singularity has specific implications by stakeholder. The institutional response cycle in most democracies is longer than the cadence the data implies.

Stakeholder implications by audience
Calibrated to the empirical data, not to either techno-optimist or doomer framings.
▲ FOR SOFTWARE
ENGINEERS
Bilingual engineer beats monolingual engineer.
“Code quality” is depreciating; “code review quality” is appreciating. Skills that retain value: engineering judgment, architecture, regulatory understanding, agent supervision. AI tool fluency is table stakes, not differentiation. Develop agent orchestration skills now. The bilingual (direct coding + agent orchestration) engineer outperforms either monolingual extreme.
▲ FOR SOFTWARE
BUSINESSES
Engineering capacity stops being the moat.
30-50% productivity gains in serious AI-tool deployments. Competitive advantages that depended on engineering capacity are eroding. What replaces them: distribution, data network effects, domain specialization, regulatory expertise, customer relationships, brand. SaaS moat strategy needs explicit re-examination. The middleware layer (Cursor, Claude Code) is the new moat-rich position.
▲ FOR POLICY
PROFESSIONALS
The empirical question is resolved.
Labor market data resolves whether AI is affecting cognitive-work employment. It is. The policy response — reskilling, transition support, social safety net, education updates — needs to operate on the cadence the data implies. “Missing generation” problem is the near-term concrete consequence. Public sector tech employment may need to maintain pipelines private sector employers are cutting.
▲ FOR
INVESTORS
Productivity story misses the structural story.
(a) Frontier-lab equity captures upside if alignment is solved. (b) AI coding platforms are the immediate value-extraction layer — Cursor $1.2B ARR, Claude Code $2.5B run-rate. Moat real, defensibility against new model entrants the open question. (c) Human-labor-heavy software businesses face structural margin pressure. The thesis reading this as a productivity story underperforms the thesis reading it as structural reorganization.
▲ FOR
EVERYONE ELSE
If you wanted unambiguous evidence, this is it.
Public benchmark data + labor market data + deployment data + tool revenue data is the strongest available evidence that the AI transition is operational rather than speculative. The window for understanding and positioning is the same 32-month window the Clark series synthesis describes. Institutional response cycles in most democracies are longer than 32 months. What gets built during the window determines the equilibrium.

The coding singularity is the canary. The mine is what matters. Software engineers and developer-tool investors are paying attention. Alignment researchers and policymakers are paying less attention than the math suggests they should.

— The structural read · May 2026

Implications of Accelerated AI Coding Capabilities

This acceleration signifies that AI could soon handle a majority of routine software engineering tasks autonomously, drastically reducing the need for human intervention in many coding contexts. For software companies, this could mean faster development cycles and reduced costs, but also raises questions about job displacement and the control of AI self-improvement. Policymakers and investors need to prepare for a rapid shift in the software industry landscape, as the recursive loop of capability enhancement could lead to an AI-driven ‘coding singularity’ within the next 12 to 24 months.

Recent Data and Prior Forecasts on AI Coding Progress

Clark’s original analysis in May 2026 highlighted two key data points: SWE-Bench scores and METR time horizons, both showing significant improvements. SWE-Bench scores for models like Mythos Preview and Claude Opus 4.7 have risen sharply, indicating near-human performance on routine coding tasks. Meanwhile, METR’s time horizon for AI to generate functional code has decreased from 6 hours in 2025 to an expected median of 24 hours by the end of 2026, based on updated measurements from Cotra.

Earlier forecasts, including Clark’s, underestimated the speed of these improvements, with some predictions suggesting a slower pace. However, recent updates from Cotra and others show the trajectory has actually accelerated, with the doubling time for capabilities now closer to 4.3 months, rather than the 7 months initially assumed.

“The recent data confirms that AI coding capabilities are advancing faster than previously projected, indicating an imminent approach to the coding singularity.”

— Thorsten Meyer

Uncertainties in Deployment and Broader Industry Impact

While capability metrics have improved dramatically, it remains unclear how widely these advances are being adopted outside frontier labs. The performance gap between routine tasks and complex, unfamiliar codebases persists, and the speed at which AI can be integrated into large-scale, real-world software projects is still uncertain. Additionally, the long-term stability and safety of self-improving AI systems are unresolved issues that could influence deployment timelines.

Next Steps in Monitoring AI Coding Capability and Deployment

Researchers and industry leaders will focus on tracking the progression of AI coding performance across more challenging benchmarks and real-world applications. Further updates from Cotra and other measurement initiatives are expected to refine the timeline for the coding singularity. Policymakers and investors should prepare for rapid shifts in software development practices, with particular attention to safety, control, and economic impacts of autonomous AI coding systems.

Key Questions

How close are we to the AI coding singularity?

Based on recent data, the core capabilities are approaching a point where AI can autonomously handle most routine coding tasks within the next 12 to 24 months, but full self-improving systems and broad deployment are still uncertain.

What does the acceleration mean for software engineers?

It could lead to a reduction in demand for routine coding work, shifting roles toward oversight, architecture, and complex problem-solving, while some tasks become fully automated.

Are there risks associated with self-improving AI systems?

Yes, the potential for runaway self-improvement raises concerns about control, safety, and unintended consequences, which are active areas of research and policy debate.

Will all software development be automated soon?

No, current capabilities are strongest in familiar, routine tasks; complex, unfamiliar, or high-stakes projects still require human expertise, and the timeline for full automation remains uncertain.

What industries will be most affected?

Software development, tech startups, and AI-driven automation sectors will experience the most immediate impact, with broader implications for manufacturing, finance, and other data-intensive fields.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

Jack Clark Says It Out Loud — Reading the Co-Founder’s 60%/2028 Estimate on Automated AI R&D

Anthropic’s co-founder Jack Clark publicly estimates a 60% chance of autonomous AI R&D by 2028, signaling a major policy stance on AI timelines.

Fair-value appraisals for used GPUs and AI hardware

New fair-value appraisal method aims to standardize pricing for used AI hardware, helping brokers resolve price disputes and improve market transparency.

OpenEuroLLM. The third path.

OpenEuroLLM, a pan-European project funded by €20.6M EU budget, aims to develop multilingual LLMs but faces significant compute challenges, revealing structural limits.

Every Benchmark Launched 2023-2024 Has Fallen — The METR / SWE-Bench / CORE-Bench / MLE-Bench / PostTrainBench Sequence

Every major AI research benchmark launched in 2023-2024 has been saturated or is nearing saturation, indicating rapid progress in AI capabilities.