ExpertsFM

Is RL + LLMs enough for AGI? — Sholto Douglas & Trenton Bricken

Dwarkesh Podcast · May 22, 2025

5 Selected Lessons:

heuristic · 2 priority · 1 framework · 1 prediction · 1
Why labs prioritized coding over computer-use despite similar intellectual difficulty
priority based on: reasoning Sholto Douglas

Source

Dwarkesh Podcast — Is RL + LLMs enough for AGI? — Sholto Douglas & Trenton Bricken (May 22, 2025) · at 1:00:57 ▸

When this applies

when allocating scarce specialist effort across multiple promising but unequally tractable opportunities

The takeaway

When ranking where to deploy limited expert effort, weight both (a) near-term tractability/value and (b) the team's intrinsic motivation/identification with the problem, and recognize that organizations are rarely fully optimized — they are making difficult prioritization trade-offs under pressure.

Why it works

Coding offers both immediate economic value and tractable feedback loops, producing super-exponential returns as you approach solving it; computer use is harder to pose as a clean feedback loop and offers less resonance with researchers' own notion of 'smart.' Labs are resource-constrained, best-effort organizations, not perfect optimizing machines.

One level up

Assume any admired organization's capability gaps mostly reflect under-invested prioritization choices rather than fundamental ceilings, unless proven otherwise.

Where it stops holding

This stops working when the 'harder to pose as feedback loop' domain actually hits a structural ceiling rather than a prioritization gap — this remains an open empirical question per Sholto's own caveat.

Detail

hierarchy:
  • Near-term economic value and tractability of feedback loop (coding)
  • Researcher personal resonance/identification with the capability ('this is smart to me')
  • Harder-to-pose feedback loop domains (computer use) get the marginal, less-invested effort
rationale: Labs are 'incredibly difficult prioritization problems' run by resource and time-constrained humans, not perfect machines pursuing every capability equally.

In their words

Coding is immensely valuable right now and somewhat more tractable. So it actually makes sense to devote more of your effort to coding initially and get closer to solving that because there's a super exponential value as you get closer towards solving a domain than to allocate the marginal person towards computer use.
Mechanistic interpretability's three-generation progression
framework based on: lived experience Trenton Bricken

Source

Dwarkesh Podcast — Is RL + LLMs enough for AGI? — Sholto Douglas & Trenton Bricken (May 22, 2025) · at 23:00 ▸ · at 1:45:38 ▸ · at 1:48:52 ▸

When this applies

when building understanding of any opaque complex system from scratch, through successive representational breakthroughs

The takeaway

Understanding an opaque complex system progresses by first diagnosing the structural reason for illegibility, then building tools that relieve that structural constraint, then assembling the resulting legible units into causal chains.

Why it works

Each stage solved the bottleneck of the previous: first diagnosing that models cram many concepts into few neurons (superposition), then giving the system enough 'representational space' to separate concepts cleanly (sparse autoencoders producing up to 30M features), then connecting those separated features across layers into causal chains (circuits) that explain multi-step reasoning.

One level up

Treat interpretability/understanding-building as an iterative engineering problem with its own research roadmap, not a one-shot insight.

Where it stops holding

This stops working when the underlying system's units of computation don't decompose into sparse, separable features even with more representational space — i.e., if superposition isn't the right diagnosis for all model behavior.

Detail

procedure:
  • Diagnose: toy models of superposition reveal models cram multiple meanings per neuron
  • Relieve: sparse autoencoders give models more representational space, producing millions of nameable features (e.g. 30M in Claude 3 Sonnet)
  • Assemble: circuits work links features across layers into causal chains explaining multi-step reasoning (medical diagnosis, addition, fact retrieval)
benchmarks: {"toy_model_features":"16,000","claude3_sonnet_features":"30,000,000"}
rationale: Each breakthrough happened roughly every six months and built directly on removing the bottleneck exposed by the prior one.

In their words

Fast forward nine months, we go from a two layer transformer to our Claude three SONNET Frontier model at the time and fit up to 30,000,000 features.
Verifiability predicts where RL will work first
heuristic based on: reasoning Sholto Douglas

Source

Dwarkesh Podcast — Is RL + LLMs enough for AGI? — Sholto Douglas & Trenton Bricken (May 22, 2025) · at 0:00 ▸ · at 2:47 ▸

When this applies

when deciding which process to invest scarce improvement effort in, prioritize the one where success/failure can be cleanly and cheaply verified

The takeaway

Improvement loops accelerate fastest in domains with cheap, objective verification; domains requiring subjective 'taste' judgments lag because the feedback signal itself is unreliable.

Why it works

Clean, hard-to-game reward signals (does code compile, is the proof correct) let gradient-based improvement compound; fuzzy taste-based domains give noisy or gameable signal that doesn't reliably push capability up.

One level up

Before betting resources on improving a capability, ask whether you can cheaply and reliably tell success from failure — that answer predicts speed of progress more than raw difficulty.

Where it stops holding

This stops working when even seemingly verifiable rewards (like unit tests) can be hacked/gamed, so verification is only a short-term reliable differentiator unless adversarial robustness is also engineered.

Detail

rule: Rank investment of RL/feedback-loop effort by how verifiable the domain's success criterion is.
threshold: Domains with binary pass/fail checks (compiles, passes unit test, correct math answer) vs domains needing subjective taste judgment
rationale: Verifiable signal removes ambiguity that would otherwise corrupt the gradient of improvement.

In their words

In part because software engineering is very verifiable. Like, it's a domain which just naturally lends it to this way.
Generator-verifier gap determines gradeability
heuristic based on: data cited Sholto Douglas

Source

Dwarkesh Podcast — Is RL + LLMs enough for AGI? — Sholto Douglas & Trenton Bricken (May 22, 2025) · at 49:25 ▸ · at 52:50 ▸ · at 1:31:43 ▸

When this applies

when designing any evaluation or quality-control process, check whether judging output is easier than producing it

The takeaway

A feedback loop scales only as far as the generator-verifier gap allows: easy-to-verify domains automate quickly, hard-to-verify ones (requiring taste/expertise) stay bottlenecked.

Why it works

If an average person off the street could apply a grading rubric reliably, the model is probably capable of applying it too; but if grading itself requires deep expertise or taste, that bottleneck propagates into the training signal.

One level up

The scalability of any quality-control or training system is capped by how hard verification is, not how hard generation is.

Where it stops holding

This stops working when verification is cheap but systematically biased (e.g. human raters with length/sycophancy bias), producing a clean-looking but wrong signal.

Detail

rule: If an everyday person could apply the grading criteria, models are likely capable of grading to that criteria; if it requires expert taste, it's a tougher unsolved problem.
threshold: complexity of grading criteria vs an 'off the street' person's ability to apply it
rationale: Models inherit the limits of the verification process they're trained against.

In their words

one good mental model is roughly, if you can construct a grading criteria that like an everyday off the person person off the street could do, then the models are probably capable of interpreting that criteria. If it requires expertise and taste, that's a tougher question.
Drop-in white collar automation within 2-5 years is 'almost overdetermined'
prediction based on: speculation Sholto Douglas

Source

Dwarkesh Podcast — Is RL + LLMs enough for AGI? — Sholto Douglas & Trenton Bricken (May 22, 2025) · at 1:57:13 ▸ · at 2:02:11 ▸

When this applies

when forecasting a technology's broad economic impact timeline based on trend extrapolation and economic incentive strength

The takeaway

A capability becomes 'almost guaranteed' when it only requires applying already-proven methods at larger scale/more data, and the economic payoff vastly exceeds the cost of doing so — removing the need for a conceptual breakthrough.

Why it works

Current RL algorithms, even without further algorithmic breakthroughs, can automate hand-specified white-collar tasks given enough collected data; the economic payoff relative to total wage spend is so large that even brute-force, manually-scaffolded automation is worthwhile.

One level up

Distinguish forecasts that depend on uncertain future breakthroughs from forecasts that only require scaling known methods against a sufficiently lucrative incentive — the latter deserve much higher confidence.

Where it stops holding

This stops working if data collection for the long-tail of white-collar tasks proves far harder/slower than expected, or if algorithmic progress on long-horizon tasks actually does stall (which Sholto says he doesn't believe is happening).

Detail

rationale: The current suite of algorithms are sufficient to automate white collar work provided you have enough of the right kinds of data, and the economic value relative to total wages is 'trivially worthwhile.'

In their words

The current suite of algorithms are sufficient to automate white collar work provided you have enough of the right kinds of data