📊 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

Recent updates confirm AI’s coding capabilities have advanced significantly, creating a recursive loop of self-improvement. The coding singularity is happening faster than previously thought, but its full impact remains uncertain.

Recent data from May 2026 confirms that AI systems have achieved a level of coding capability that is fundamentally transforming software engineering, surpassing earlier estimates by Jack Clark and others. The evidence indicates that the so-called ‘coding singularity’—the point where AI self-improves through recursive automation—is actively unfolding, with significant implications for the industry and labor market.

Clark’s original data points—93.9% SWE-Bench score for Mythos Preview and rapid improvements in METR time horizons—have been confirmed and updated. Mythos Preview now scores 93.9%, up from about 2% in late 2023, indicating near-human performance on routine coding tasks within familiar codebases. The gap widens in more complex, private, and less familiar tasks, which remain challenging for current models.

Deployment patterns show the majority of frontier labs and Silicon Valley firms coding predominantly through AI, especially for routine tasks. However, broader industry adoption varies, with enterprise-level private codebases still presenting significant hurdles. The recursive self-improvement loop that Clark describes appears to be accelerating, with capabilities expanding faster than earlier projections suggested, especially in the last six months.

Meanwhile, the METR time horizon has shortened from an extrapolated 100 hours to a median of approximately 24 hours for end-2026, based on recent recalibrations. This indicates AI systems are approaching near real-time code generation, further fueling the perception of an imminent singularity.

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
AI VoiceWriter – Smart Dictation & AI Writing Assistant for Windows & Mac | USB Dongle & Mobile App for Voice Input, Proofreading, Rewriting & Multilingual Support

AI VoiceWriter – Smart Dictation & AI Writing Assistant for Windows & Mac | USB Dongle & Mobile App for Voice Input, Proofreading, Rewriting & Multilingual Support

🎙️ Hands-Free Voice Typing for Windows & Mac – Powered by iOS & Android dictation technology, AI VoiceWriter…

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
CODE GENERATION AND TEMPLATE SYSTEMS: Automated Scaffolding Reusable Patterns and Development Acceleration

CODE GENERATION AND TEMPLATE SYSTEMS: Automated Scaffolding Reusable Patterns and Development Acceleration

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
VIBECODING WITH GOOGLE ANTIGRAVITY IDE: Build AI-Powered Software at the Speed of Thought Using Agentic Workflows, Natural Language, and Flow-State Development

VIBECODING WITH GOOGLE ANTIGRAVITY IDE: Build AI-Powered Software at the Speed of Thought Using Agentic Workflows, Natural Language, and Flow-State Development

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
Lakeshore Self-Teaching Math Machines - Set of 4

Lakeshore Self-Teaching Math Machines – Set of 4

Our set of math machines puts fun math practice right at kids’ fingertips

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

The confirmation and acceleration of AI’s coding abilities suggest a fundamental shift in software development. Routine coding tasks are increasingly automated, potentially reducing demand for human programmers in certain areas while raising questions about the future of software engineering, labor markets, and AI governance. The unfolding recursive self-improvement loop could lead to rapid, unpredictable advancements, making it critical for policymakers, industry leaders, and developers to monitor and adapt.

Recent Data and the Evolution of AI Coding Progress

Since Clark’s initial assessment in early May 2026, new data has confirmed the rapid improvements in AI coding performance. SWE-Bench scores, especially for models like Mythos Preview, have remained high, with the gap between benchmark performance and real-world complexity narrowing. The METR time horizon, once projected at 100 hours, has now been recalibrated to a median of 24 hours, reflecting faster-than-expected progress. These developments build on a trajectory that has seen AI capabilities double approximately every 4.3 months since 2023, indicating a steepening curve.

While the data confirms the core thesis of Clark’s ‘coding singularity,’ it also highlights that the current capabilities are most effective on familiar, routine tasks. More complex, unfamiliar, or architectural work remains a challenge, and the extent of industry-wide adoption depends on how quickly these hurdles can be addressed.

“The recent data confirms that AI systems now handle the majority of routine software engineering tasks at near-human levels, and the progress is accelerating faster than previously estimated.”

— Thorsten Meyer

Unresolved Questions About Industry-Wide Impact

While the data confirms rapid progress in AI coding capabilities, it remains unclear how quickly these advancements will be adopted across diverse industries, especially in private, complex codebases. The extent to which AI will replace or augment human programmers in more sophisticated tasks is still uncertain. Additionally, the long-term effects of the recursive self-improvement loop on AI development speed and safety are not yet fully understood.

Monitoring AI Progress and Industry Adoption

The next steps include tracking further updates in AI coding benchmarks, observing deployment patterns across different sectors, and analyzing how the recursive self-improvement cycle evolves. Researchers and policymakers will need to assess risks and opportunities as AI systems approach real-time code generation, with particular attention to safety, ethical considerations, and labor market impacts.

Key Questions

How close are we to fully automating all software development tasks?

Current data suggests AI handles routine and familiar coding tasks at near-human levels, but complex, unfamiliar, and architectural work still pose challenges. Full automation of all software development is not yet achieved and may take years, depending on progress in these harder areas.

What does the ‘coding singularity’ mean for software engineers?

It indicates a shift where AI systems increasingly automate routine coding, potentially reducing demand for human programmers in certain roles, while also enabling new kinds of engineering work focused on oversight, architecture, and safety.

Are there risks associated with rapid AI self-improvement in coding?

Yes, rapid self-improvement could lead to unpredictable AI behavior or capabilities. Ensuring safety, alignment, and governance will be critical as these systems become more autonomous and capable.

How reliable are the current benchmarks in measuring AI coding ability?

Benchmarks like SWE-Bench provide a strong indication of AI performance on routine tasks, but they do not fully capture real-world complexity, especially in private or unfamiliar codebases. Their results should be interpreted as indicative rather than definitive.

What are the implications for AI regulation and policy?

The rapid progress underscores the need for proactive regulation and international cooperation to manage risks associated with autonomous AI systems, especially as they approach real-time self-improvement capabilities.

Source: ThorstenMeyerAI.com

You May Also Like

Osaurus brings both local and cloud AI models to your Mac

Osaurus introduces an open-source Mac application enabling users to run and switch between local and cloud AI models securely on their hardware.

Engineering Is Automated. Research Is the Residual.

Recent benchmarks show AI can automate core engineering tasks, leaving research as the remaining challenge, with implications for AI development timelines.

Disk Is the Contract: Inside Threlmark’s Local-First Architecture

Discover how Threlmark’s local-first design makes disk the ultimate source of truth, enabling offline work, fast responses, and seamless collaboration.

DDR5 Now, DDR6 Soon: A Buyer’s Field Guide

A comprehensive guide on current DDR5 options and what to expect from DDR6, helping buyers make informed decisions amid ongoing memory market shifts.