📊 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 coding capabilities have significantly improved, with models now handling routine tasks at near-human levels. The pace of progress suggests the coding singularity is approaching faster than earlier forecasts indicated, impacting software development and industry dynamics.

Recent data confirms that AI systems are now capable of handling the majority of routine software engineering tasks at near-human or super-human levels, accelerating the onset of the coding singularity beyond previous projections.

Two key data points from Thorsten Meyer’s analysis—SWE-Bench scores and METR time horizons—have been updated since early May 2026. SWE-Bench results show that models like Mythos Preview now achieve 93.9% on routine coding tasks, a significant increase from late 2023 levels. Meanwhile, METR time horizons, which measure how quickly AI can solve complex tasks, have shortened from an estimated 100 hours at the end of 2026 to a median of approximately 24 hours, reflecting faster progress than earlier forecasts.

These improvements indicate that AI’s ability to automate large portions of software engineering is advancing rapidly, and the deployment of these capabilities in industry is more widespread than initially believed. However, the data also shows that more difficult, less routine tasks—such as architectural judgment and unfamiliar codebases—remain challenging for current models, suggesting the singularity is primarily unfolding within a specific scope of 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
"Looks Good To Me": Constructive code reviews

"Looks Good To Me": Constructive code reviews

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
Avid Pro Tools Artist - Music Production Software - Perpetual License

Avid Pro Tools Artist – Music Production Software – Perpetual License

This item is sold and shipped as a download card with printed instructions on how to download the…

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 for Software Industry and AI Development

The acceleration of AI coding capabilities and faster task completion times suggest a near-term shift in software engineering practices, with AI systems increasingly automating routine tasks. This could lead to significant productivity gains, labor market shifts, and changes in how software products are developed and maintained. The findings also reinforce the likelihood that the coding singularity—an inflection point where AI begins self-improving rapidly—may arrive sooner and more steeply than previously thought, impacting policy, investment, and industry strategies.

Recent Data and the Evolution of AI Coding Capabilities

In May 2026, Thorsten Meyer’s review of recent updates confirmed that AI models like Claude Mythos Preview now perform at 93.9% on SWE-Bench tasks, up from 2% in late 2023. Similarly, METR time horizons, which measure how quickly AI can solve complex problems, have been revised downward from 100 hours to around 24 hours by the end of 2026, based on newer measurements and recalibrated forecasts. These updates reflect a faster-than-expected trajectory of AI progress, driven by improvements in model architecture and deployment practices across frontier labs and industry.

While earlier models struggled with unfamiliar codebases and complex architectural decisions, current data indicates that routine coding tasks are approaching or surpassing human-level performance for the tasks measured. The broader industry deployment is still uneven, with many organizations adopting AI for simpler, repetitive work, while more complex engineering remains a challenge. The debate over whether this constitutes the true ‘coding singularity’ continues, but the trend lines are clear: AI’s role in software development is expanding rapidly.

“The data shows AI models are now handling the majority of routine coding tasks at near-human levels, and the progress is accelerating faster than earlier forecasts suggested.”

— Thorsten Meyer

Remaining Challenges and Unanswered Questions in AI Coding

It remains unclear how well current AI models will perform on highly complex, unfamiliar, or architectural tasks outside the scope of existing benchmarks. The extent to which deployment in broader, real-world software engineering will match laboratory results is still uncertain. Additionally, the timeline for the full realization of the coding singularity—where AI self-improves autonomously at scale—continues to be debated among experts, with some arguing it could arrive sooner than expected and others cautioning about unforeseen obstacles.

Next Steps for Monitoring AI Progress and Industry Adoption

Researchers and industry leaders will focus on tracking the performance of AI models on more complex, real-world tasks beyond benchmark scores. Investment in AI deployment across diverse software environments is expected to increase, alongside regulatory and policy discussions about managing this rapid technological shift. The coming 12-24 months will be critical for observing whether the current acceleration continues and how industry adapts to these capabilities.

Key Questions

What exactly 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 inflection point where AI begins self-improving at an accelerating pace, significantly transforming software development.

Are current AI models capable of replacing human programmers?

Current models handle routine and well-defined coding tasks at near-human or super-human levels, but more complex, unfamiliar, or architectural tasks remain challenging. Full replacement of human programmers is not yet feasible across all aspects of software engineering.

How soon could the coding singularity happen?

Based on recent data, some experts suggest the core capabilities could reach a critical inflection point within the next 1-2 years, but the exact timing depends on further technological breakthroughs and deployment scale.

What are the risks associated with this rapid progress?

Potential risks include job displacement for certain roles, security vulnerabilities from autonomous code generation, and regulatory challenges related to oversight and safety of self-improving AI systems.

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

The New Personal Agent Layer

OpenClaw and Hermes introduce a new layer of persistent, action-oriented AI agents that operate across digital environments, transforming personal and enterprise workflows.

Anchor. The Schwarz Group model.

Schwarz Group’s €11B investment in a data center campus exemplifies Europe’s largest retail-led AI infrastructure effort, with potential for replication.

The queue. Why the grid, not the chip, is the binding constraint on AI.

The US AI buildout faces a new bottleneck: the power grid queue. Capital is bypassing the grid, shifting costs and reshaping geographic and economic dynamics.

The Forecast Is the Plan.

Major AI labs publicly commit to automating AI research by 2026, signaling a shift from aspiration to strategic execution. What this means for the industry.