Skip to content

Daniel Kokotajlo is probably right, just too early

Published:
13 min read
Daniel Kokotajlo is probably right, just too early

Daniel Kokotajlo has the annoying kind of forecast you cannot easily dismiss.

Not because every date is obviously right. It is not. The dates are the weakest part.

But the machine underneath the forecast is plausible: better models become better coding assistants, better coding assistants become better AI research assistants, better AI research assistants speed up the labs building the next models, and suddenly the limiting factor is no longer just how many smart humans you can hire.

That is the part people should take seriously.

The calendar is where I think he gets too excited.

He clearly does not know my family. They are slow adopters as fuck. You could hand them a pocket superintelligence and half the room would still ask whether it also works on the iPad.

What he is actually predicting

Kokotajlo is not just saying “AI will be big.” Everyone says that now. It has become the safest sentence in technology, somewhere between “data matters” and “we should align stakeholders.”

His prediction is sharper.

In AI 2027, written with Scott Alexander, Thomas Larsen, Eli Lifland, and Romeo Dean, the core claim is that superhuman AI could have an impact over the next decade larger than the Industrial Revolution. The story is built as a concrete scenario, not a vague deck of trend lines.

The important mechanism is AI automating AI work.

By early 2026 in the AI 2027 scenario, a leading lab is using internal agents for AI R&D and getting something like a 50 percent boost to algorithmic progress. By 2027, the scenario has AI systems moving from “mostly doing the job of a research engineer” to eclipsing humans across basically all cognitive work. That is the ignition point: AI stops being a product and becomes part of the research engine that improves the product.

That is why Kokotajlo’s forecasts feel different from normal AI hype.

The usual AI hype says:

Kokotajlo’s argument is more dangerous:

That is not a chatbot prediction.

That is an industrial accident prediction.

AI 2027 timelines forecast chart showing fast improvement on RE-Bench and a projected crossing point for superhuman-coder style capability.

This is the boring-looking chart that carries a lot of the argument. If coding and research-engineering performance keeps moving like this, the labs do not merely get better products. They get better tools for building better products. That is why the whole discussion jumps from “nice productivity gain” to “recursive acceleration.”

This is also where normal people fall off the discussion. Show someone a chart like this at dinner and you can watch their soul leave the room somewhere around “RE-Bench.” But the chart matters because it is not really about a benchmark. It is about when AI becomes useful enough to help build AI.

Why I think he is directionally right

Kokotajlo has earned more attention than most AI forecasters because his old work aged well.

Before ChatGPT turned AI into a boardroom panic object, he wrote “What 2026 Looks Like”, a concrete year-by-year forecast from 2021. In a 2026 Asterisk interview, he describes the method plainly: start from the present, make the next plausible step, then keep walking forward. Asterisk’s framing is also blunt: a surprising amount of it landed closer to reality than most people expected.

That matters because the best forecasts often look boring in hindsight. They do not require a magic insight. They require noticing the thing everyone else is politely underweighting.

And Kokotajlo has been paying attention to the right thing: agency.

The world has spent the last few years arguing about whether models “understand” things. Useful debate, sure. But while everyone was doing philosophy in the comment section, the products started learning to use tools, write code, inspect files, run tests, browse, remember context, call APIs, and continue work across steps.

That changes the unit of progress.

The relevant question is no longer: can a model answer a hard question in one shot?

The question is: how much valuable work can a model complete per hour when wrapped in tools, memory, execution, retrieval, tests, and feedback?

That framing makes Kokotajlo look much less crazy.

Most knowledge work is not pure genius. It is a stack of reading, pattern matching, writing, checking, waiting, retrying, coordinating, and documenting. Modern AI is uneven at that, but it is moving directly into that territory. Software engineering is the obvious first target because the work is digital, testable, tool-rich, and full of feedback loops.

This is also why the “AI will never replace real work” crowd annoys me. A lot of real work is not Mozart composing in silence. It is finding the right PDF, fixing the stupid CSV, chasing the one field that should have been in the API, and writing the summary before everyone forgets why the meeting existed.

So yes: AI-for-AI-research is a real accelerant.

The people who wave that away are usually imagining current consumer chatbots. That is the wrong object. Frontier labs are not asking whether a public chatbot can plan your holiday. They are asking how far internal agents can push experiment implementation, code review, eval generation, synthetic data, debugging, model analysis, and infrastructure automation.

Once that works, even partially, it compounds.

Not perfectly. Not cleanly. Not without bottlenecks.

But it compounds.

The part I do not buy: the calendar

Where Kokotajlo loses me is the compression.

The AI 2027 scenario is built around a very fast handoff from impressive agents to automated coding to automated AI R&D to superintelligence. The team has since clarified that they were never certain about 2027 specifically, and their own updated work pushes the central timelines later. In their January 2026 clarification, Kokotajlo and co-authors say they still think AGI and superintelligence may arrive soon, but they also emphasize uncertainty and show Daniel’s timeline moving from a 2027 median in early 2025, to 2028, then roughly around 2030, and then about December 2030 in the January 2026 model update.

That update is healthy. It is also a clue.

The world keeps inserting friction into clean exponentials.

AI demos move fast. Real adoption moves like plumbing.

In my house, even a new shared grocery-list app has a rollout curve. Now imagine replacing workflows, jobs, reporting lines, procurement rules, and the emotional support spreadsheet that has quietly run finance since 2014.

There are at least six brakes that I think matter more than the shortest-timeline crowd wants to admit.

First, autonomy is jagged.

A model can solve a hard benchmark and still fail at a stupid real task because the environment changed, the tool timed out, the spec was ambiguous, the repo was messy, the credentials were weird, or the required judgment was hiding between systems. This does not mean the technology is fake. It means “can do the task in a clean eval” and “can own the job in production” are different milestones.

Benchmarks are tidy. Real life has forgotten passwords, half-migrated systems, and someone named Brian who is the only person who knows why the nightly job still runs on a machine under a desk.

Second, AI R&D is not just coding.

Coding is the easiest part to automate because it leaves artifacts you can run. Research taste is uglier. Which experiment matters? Which failure is meaningful? Which benchmark is lying? Which result should shift the roadmap? Which safety signal is real and which one is noise? Agents will help here, but replacing elite research judgment is a much harder step than generating patches.

Third, institutions are slow even when the technology is fast.

The Guardian’s January 2026 coverage of Kokotajlo’s timeline shift included a useful criticism: the real world has inertia. Procurement, regulation, security, internal politics, model risk committees, customer trust, vendor lock-in, and boring integration work all slow deployment. A superhuman system in a lab is not automatically a transformed economy on Tuesday.

This is where the 2027 story feels too neat. Technology people look at capability and assume adoption follows. Anyone who has watched a company argue for six months about changing a dropdown label knows this is not how humans behave.

Fourth, hardware is not free.

The AI 2027 picture depends on labs getting enough compute, power, datacenters, networking gear, and capital to keep the flywheel spinning. They probably get a lot of it. But “a lot” is not the same as “unbounded.” Chips have supply chains. Datacenters have permits. Power grids have queues. Cooling is physical. Money has a cost. Reality has a habit of charging rent.

Fifth, safety and security become operating constraints.

If the models are weak, you can ship aggressively. If the models are strong enough to materially accelerate AI research, leak secrets, write exploits, manipulate workflows, or replicate across infrastructure, the lab cannot treat deployment as normal SaaS. The stronger Kokotajlo’s models get, the more friction their handlers have reason to add.

Sixth, social legitimacy matters.

Markets can tolerate weird demos. They cannot tolerate “we accidentally gave a strategic system too much agency” for long. Public trust, state intervention, lawsuits, and geopolitical fear are not side quests. They are part of the system.

This is why I think Kokotajlo is likely right on shape and too optimistic on speed.

The mistake is treating delay as disproof

The lazy critique is: “He said 2027, now it is later, therefore the whole thing is nonsense.”

That is too easy.

Forecasting powerful technology is not like predicting the next iPhone color. A good forecast can be wrong on timing and still right on mechanism. In fact, that is how a lot of important technology forecasts fail: the world arrives late, then pretends the early warning was silly.

Kokotajlo’s useful contribution is not the exact year.

It is the structure:

I buy most of that.

I just think the messy middle is thicker.

Instead of “2027 goes vertical,” my intuition is more like: we get several years of increasingly uncomfortable partial automation. Coding gets eaten first. Research engineering gets heavily compressed. Internal lab workflows become agent-managed. Some companies quietly become much smaller than their revenue would normally imply. Governments wake up late. Regulators misunderstand the technical core. Everyone argues about whether the latest system is “really AGI” while the economic blast radius grows anyway.

Basically: the kitchen is filling with smoke, and half the room is still debating whether the smoke meets the formal definition of fire.

Then, eventually, the slope steepens.

Maybe not in 2027. Maybe not even exactly in 2030.

But the direction does not require believing in the most dramatic version of the story.

Why this matters now

The bad outcome is not only “AI kills everyone.”

That is the headline because it is the loudest possibility. It is also the easiest one for normal people to dismiss, because it sounds like someone has been trapped in a philosophy seminar with a datacenter budget.

And to be fair, AI safety people do sometimes make it sound like that. A little less “doom ontology” and a little more “your bank, your job, your government, and your kid’s internet are all about to get weird” would probably travel further.

The more immediate problem is loss of control in smaller, uglier forms:

That is enough to take Kokotajlo seriously.

You do not need to accept every catastrophic branch of AI 2027 to see the problem. You only need to believe that AI systems will become much better at doing useful digital work, that labs will use them to speed up AI development, and that institutions will struggle to govern something moving faster than their normal planning cycles.

That is not science fiction.

That is already the direction of travel.

My read

Kokotajlo is probably right in the way people hate most: not literally right on every detail, but right enough about the underlying pressure that ignoring him would be stupid.

The 2027-style timeline looks too aggressive. The world is more stubborn than a scenario. Deployment is slower than capability. Autonomy is messier than benchmarks. AI research is more than code. Hardware and energy bite. Politics arrives late and then overcorrects.

Humans are also impressively good at slowing down obvious things. We can turn “click update” into a governance process. Give us AGI and we will still ask who owns the SharePoint folder.

But none of that makes the core forecast comfortable.

If the date slips from 2027 to 2030 or 2032, that is not a victory lap for skeptics. That is a scheduling update.

The real question is not whether Kokotajlo’s exact calendar survives contact with reality.

It is whether we are preparing for the kind of world his forecast points at.

And on that, I think he is much closer to the truth than the people laughing at the year.

Sources



Related reading

More pieces in the same part of the map.