📊 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

New evidence shows AI models now code at near-human levels for routine tasks, with capabilities advancing faster than earlier forecasts. This accelerates the recursive improvement loop, potentially leading to a coding singularity.

Recent data confirms that AI models are now capable of performing a majority of routine software engineering tasks at near-human or super-human levels, and the pace of their capability improvement is faster than previously projected, indicating the onset of the coding singularity.

Thorsten Meyer reports that the capabilities of AI coding models, particularly those evaluated on the SWE-Bench benchmark, have increased substantially since earlier estimates. The Mythos Preview model now scores 93.9%, up from approximately 2% at the end of 2023, indicating near-complete automation of routine coding tasks in certain contexts. The data suggests that AI can handle roughly 80% of typical software engineering work on familiar codebases, primarily at the easier end of the task spectrum.

Simultaneously, the deployment landscape shows that many frontier labs and Silicon Valley companies are coding predominantly through AI systems, reinforcing the idea that AI-driven automation is becoming the norm in software development. The recursive self-improvement loop—where improved AI coding capabilities lead to faster development of even more capable AI systems—appears to be accelerating, with capability growth now outpacing earlier forecasts. The METR time horizon data indicates that AI systems are closing in on a 24-hour completion window for complex tasks by the end of 2026, a significant acceleration from prior predictions of around 100 hours.

While these developments confirm the presence of a rapid capability ramp, it remains unclear how much of this progress translates into broader, more complex engineering tasks involving unfamiliar codebases, architectural judgment, or domain-specific challenges. The current benchmarks primarily measure routine, well-understood coding tasks, which may not fully represent the entire scope of software engineering work.

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
FOXWELL NT301 OBD2 Scanner Live Data Professional Mechanic OBDII Diagnostic Code Reader Tool for Check Engine Light

FOXWELL NT301 OBD2 Scanner Live Data Professional Mechanic OBDII Diagnostic Code Reader Tool for Check Engine Light

【Vehicle CEL Doctor】The NT301 obd2 scanner enables you to read DTCs, access to e-missions readiness status, turn off…

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
Master Cursor 2.0 for AI Coding: Transform Your Workflow with Agent-First Coding, Multi-Agent Workflows & Modern IDE Power

Master Cursor 2.0 for AI Coding: Transform Your Workflow with Agent-First Coding, Multi-Agent Workflows & Modern IDE Power

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
BUILD YOUR FIRST AI PRODUCTS : A Step-by-Step Guide for Solopreneurs and Creators — Validate, Launch, and Monetize Intelligent Tools, and Automations Without a Team or Technical Background.

BUILD YOUR FIRST AI PRODUCTS : A Step-by-Step Guide for Solopreneurs and Creators — Validate, Launch, and Monetize Intelligent Tools, and Automations Without a Team or Technical Background.

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 rapid advancement of AI coding abilities suggests that a self-improving loop is now operational, which could lead to a technological singularity in software development. This shift has profound implications for software engineers, companies, and policymakers, as automation could drastically reduce the need for human coding in routine tasks and reshape the labor market. Additionally, the acceleration raises questions about AI governance, safety, and the future of AI-human collaboration in engineering fields.

Recent Data and Forecasts on AI Coding Progress

Since late 2023, AI models like Claude Mythos and GPT-5 have shown dramatic improvements in coding benchmarks. The SWE-Bench scores have increased from near-zero to over 90%, with the latest data from May 2026 confirming the trend. The METR project, which measures the time horizon for AI to complete complex tasks, has revised its forecasts downward, suggesting that AI will reach near real-time code completion within the next year. These updates indicate that the pace of AI capabilities is faster than earlier projections, including those by Cotra, who now estimates a median of 24 hours for complex tasks by the end of 2026.

Prior to these updates, many experts believed that AI would take several years to reach such levels of automation. The new data suggests that the self-improving cycle—where improved coding capabilities lead to the development of even more advanced AI systems—is now in motion and accelerating, potentially leading to the coding singularity described by Jack Clark.

“The capability data confirms that AI models are now handling a majority of routine coding tasks at near-human levels, and the pace of improvement is faster than previously thought.”

— Thorsten Meyer

Uncertainties Around Broader Engineering Tasks

It remains unclear how well current AI capabilities translate to complex, unfamiliar, or domain-specific engineering tasks that require architectural judgment, creativity, or domain expertise. The benchmarks primarily measure routine coding, which may not fully represent the entire scope of software engineering work. Additionally, the timeline for widespread deployment across diverse industries and the potential risks associated with rapid AI self-improvement are still uncertain.

Next Milestones in AI Coding Development

In the coming months, further updates from METR and other research initiatives are expected to refine the timeline for AI reaching near-real-time code completion. Observers will closely monitor deployment patterns across different sectors to assess how quickly AI-driven automation replaces human coding in complex scenarios. Policy discussions around AI safety and regulation are likely to intensify as capabilities accelerate, and researchers will seek to understand and mitigate potential risks associated with the self-improving loop.

Key Questions

What is the coding singularity?

The coding singularity refers to the point at which AI systems can autonomously improve their coding capabilities rapidly, leading to an exponential growth in their ability to develop increasingly advanced AI systems and potentially transforming software engineering.

How reliable are the benchmark scores in predicting real-world AI performance?

Benchmark scores like SWE-Bench measure specific coding tasks and are indicative of AI’s ability to handle routine software engineering work. However, they may not fully capture performance on complex, unfamiliar, or creative tasks involved in broader engineering work.

When might AI fully automate most software engineering tasks?

While current trends suggest rapid progress, precise timelines remain uncertain. Experts now estimate that near-real-time automation could be achievable within the next 12-24 months, but widespread adoption and handling of complex tasks may take longer.

What are the risks of this rapid AI development?

Accelerating AI capabilities raise concerns about safety, control, and job displacement. Policymakers and researchers are actively discussing regulation and safeguards to manage potential risks associated with self-improving AI systems.

Source: ThorstenMeyerAI.com

You May Also Like

The Hidden Power of AI for Internal Link Suggestions

Lurking within your website are hidden opportunities—discover how AI-powered internal link suggestions can unlock its full potential and transform your user experience.

Pentagon AI Goes Explicit: The Frontier Labs Move Inside the Classified Stack

The Pentagon has announced agreements with major AI firms to embed advanced AI capabilities into classified networks, signaling a shift toward AI-first military operations.

Recovery-percentile tracker for orthopedic surgery patients

A new recovery-percentile tracker for post-op orthopedic patients is being tested to help office staff manage patient calls more effectively, reducing anxiety and improving care.

The Continual Learning Research Map: Where the Memento Constraint Stands in May 2026

An analysis of ongoing research into the Memento Constraint highlights the progress and persistent challenges in achieving genuine continual learning in AI models, with timelines extending into 2028-2030.