---
schema: 1
type: video
title: >-
  It’s Tokens All The Way Down: How RLMs are Different — Kevin Madura,
  AlixPartners
description: >-
  Ask a model to sum twelve numbers scattered across thirty thousand tokens and
  it will often get it wrong. Give it a Python REPL and it writes a few lines of
  regex instead. That is the shift Kevin Madura, director of advanced technology
  at AlixPartners, describes in recursive language models. An RLM treats its
  context as an object living in a REPL rather than as tokens it must attend to,
  so it can slice, compute over, and iterate on the input as a variable. The
  second property matters as much: it can delegate to another model, including
  itself, with its own parameters, so a hard problem decomposes recursively and
  only the results that matter return to the main context. On a long chain of
  thought benchmark that moved accuracy from 2.6 percent to 45.4 percent, with
  the largest gains on tasks that reduce cleanly to code. Madura frames it
  against what most teams do now. RAG stuffs the window until quality rots.
  Agents and tool calls shuttle JSON strings back and forth, leaving logic,
  execution, and results loosely coupled. An RLM keeps all three in one
  environment. He walks a cohort retention analysis where three data frames go
  in, the model reasons in its own REPL as if typing in a notebook, and decides
  itself when to stop and submit a typed answer. Then case studies:
  consolidating long invoices with no chunking or embedding, surfacing patterns
  in raw logs, optimizing an agent harness from its own traces, and generating a
  security report across five hundred thousand lines of code. His closing bet is
  that models post trained to be RLM aware will make this much stranger. Speaker
  info: - https://x.com/kmad - https://www.linkedin.com/in/kevinmadura/ -
  https://kmad.ai Timestamps: 0:00 - What a recursive language model is 1:36 -
  Recursive decomposition and delegating to sub models 3:25 - Benchmarks and the
  cost curve 4:31 - A deterministic shell, with the model filling the middle
  5:24 - Context rot, and why an RLM avoids it 6:21 - How this differs from RAG,
  agents, and tool calls 8:00 - When to use one, and when to skip it 9:38 -
  Small examples, buried numbers and data frames 12:35 - A cohort analysis
  walkthrough and its traces 15:45 - Case studies, invoices, logs, and a whole
  codebase 20:04 - What happens when models become RLM aware --- Watch along
  with the corrected transcript, summary, timestamps and resources on this
  talk's official AIE page:
  https://ai.engineer/talks/xo68uCibfm8-youtube-5b2fd674275eca48ff07 Join our
  upcoming AI Engineer conferences (see https://ai.engineer landing page): -
  AIEi Shanghai, November 5–6 — the first for meeting top Chinese labs and
  engineers - AIE CODE in SF, November 10–12 — the top AI Coding conference
  returns - AIEi Sydney, December 7–8 — the first AIEi run alongside NeurIPS
  2026 in Sydney ---
canonical: >-
  https://liquidgold.cc/channel/aidotengineer/explore/video/it-s-tokens-all-the-way-down-how-rlms-are-different-e5415e971ba0
markdown: >-
  https://liquidgold.cc/channel/aidotengineer/video/it-s-tokens-all-the-way-down-how-rlms-are-different-e5415e971ba0.md
llms: null
parent: 'https://liquidgold.cc/channel/aidotengineer.md'
channel: aidotengineer
updated: '2026-10-24T03:59:50.994Z'
language: null
children: []
videoId: xo68uCibfm8
durationSeconds: 1248
publishedAt: '2026-09-09T13:30:27.000Z'
searchChunks:
  - ordinal: 0
    text: null
    startSeconds: 23
    endSeconds: 102
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=23'
    heldReason: rights
  - ordinal: 1
    text: null
    startSeconds: 23
    endSeconds: 102
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=23'
    heldReason: rights
  - ordinal: 2
    text: null
    startSeconds: 23
    endSeconds: 102
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=23'
    heldReason: rights
  - ordinal: 3
    text: null
    startSeconds: 112
    endSeconds: 212
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=112'
    heldReason: rights
  - ordinal: 4
    text: null
    startSeconds: 112
    endSeconds: 212
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=112'
    heldReason: rights
  - ordinal: 5
    text: null
    startSeconds: 222
    endSeconds: 278
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=222'
    heldReason: rights
  - ordinal: 6
    text: null
    startSeconds: 222
    endSeconds: 278
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=222'
    heldReason: rights
  - ordinal: 7
    text: null
    startSeconds: 324
    endSeconds: 335
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=324'
    heldReason: rights
  - ordinal: 8
    text: null
    startSeconds: 393
    endSeconds: 485
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=393'
    heldReason: rights
  - ordinal: 9
    text: null
    startSeconds: 393
    endSeconds: 485
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=393'
    heldReason: rights
  - ordinal: 10
    text: null
    startSeconds: 485
    endSeconds: 497
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=485'
    heldReason: rights
  - ordinal: 11
    text: null
    startSeconds: 497
    endSeconds: 582
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=497'
    heldReason: rights
  - ordinal: 12
    text: null
    startSeconds: 497
    endSeconds: 582
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=497'
    heldReason: rights
  - ordinal: 13
    text: null
    startSeconds: 593
    endSeconds: 758
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=593'
    heldReason: rights
  - ordinal: 14
    text: null
    startSeconds: 593
    endSeconds: 758
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=593'
    heldReason: rights
  - ordinal: 15
    text: null
    startSeconds: 758
    endSeconds: 769
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=758'
    heldReason: rights
  - ordinal: 16
    text: null
    startSeconds: 769
    endSeconds: 951
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=769'
    heldReason: rights
  - ordinal: 17
    text: null
    startSeconds: 961
    endSeconds: 1204
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=961'
    heldReason: rights
  - ordinal: 18
    text: null
    startSeconds: 961
    endSeconds: 1204
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=961'
    heldReason: rights
  - ordinal: 19
    text: null
    startSeconds: 961
    endSeconds: 1204
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=961'
    heldReason: rights
  - ordinal: 20
    text: null
    startSeconds: 1216
    endSeconds: 1248
    watch: 'https://liquidgold.cc/watch/xo68uCibfm8?t=1216'
    heldReason: rights
---


# It’s Tokens All The Way Down: How RLMs are Different — Kevin Madura, AlixPartners

Ask a model to sum twelve numbers scattered across thirty thousand tokens and it will often get it wrong. Give it a Python REPL and it writes a few lines of regex instead. That is the shift Kevin Madura, director of advanced technology at AlixPartners, describes in recursive language models. An RLM treats its context as an object living in a REPL rather than as tokens it must attend to, so it can slice, compute over, and iterate on the input as a variable. The second property matters as much: it can delegate to another model, including itself, with its own parameters, so a hard problem decomposes recursively and only the results that matter return to the main context. On a long chain of thought benchmark that moved accuracy from 2.6 percent to 45.4 percent, with the largest gains on tasks that reduce cleanly to code. Madura frames it against what most teams do now. RAG stuffs the window until quality rots. Agents and tool calls shuttle JSON strings back and forth, leaving logic, execution, and results loosely coupled. An RLM keeps all three in one environment. He walks a cohort retention analysis where three data frames go in, the model reasons in its own REPL as if typing in a notebook, and decides itself when to stop and submit a typed answer. Then case studies: consolidating long invoices with no chunking or embedding, surfacing patterns in raw logs, optimizing an agent harness from its own traces, and generating a security report across five hundred thousand lines of code. His closing bet is that models post trained to be RLM aware will make this much stranger. Speaker info: - https://x.com/kmad - https://www.linkedin.com/in/kevinmadura/ - https://kmad.ai Timestamps: 0:00 - What a recursive language model is 1:36 - Recursive decomposition and delegating to sub models 3:25 - Benchmarks and the cost curve 4:31 - A deterministic shell, with the model filling the middle 5:24 - Context rot, and why an RLM avoids it 6:21 - How this differs from RAG, agents, and tool calls 8:00 - When to use one, and when to skip it 9:38 - Small examples, buried numbers and data frames 12:35 - A cohort analysis walkthrough and its traces 15:45 - Case studies, invoices, logs, and a whole codebase 20:04 - What happens when models become RLM aware --- Watch along with the corrected transcript, summary, timestamps and resources on this talk's official AIE page: https://ai.engineer/talks/xo68uCibfm8-youtube-5b2fd674275eca48ff07 Join our upcoming AI Engineer conferences (see https://ai.engineer landing page): - AIEi Shanghai, November 5–6 — the first for meeting top Chinese labs and engineers - AIE CODE in SF, November 10–12 — the top AI Coding conference returns - AIEi Sydney, December 7–8 — the first AIEi run alongside NeurIPS 2026 in Sydney ---

Canonical: https://liquidgold.cc/channel/aidotengineer/explore/video/it-s-tokens-all-the-way-down-how-rlms-are-different-e5415e971ba0 · Channel: [AI Engineer](https://liquidgold.cc/channel/aidotengineer.md)

> Search chunk text is held until public-source provenance is verified.

## Document chunks

> Missing: no stored document chunks are available.
