# Closing the Agentic Loop Slides for Kent C. Dodds's "Closing the Agentic Loop" (given at All Things Open 2026 and BIOS SPHERE 2026). One deck serves three formats, and `?event=` picks an event: - **Short talk** (the default URL): the talk plus the FAQ. - **Event** (`?event=aie-2026`): the one-hour AI Engineer Code Summit cut, with the event name and a Podium QR (corner of every slide, and on the title). Event config lives in `data/events.json`. `?format=hour` is an alias for this event. - **Full-day workshop** (`?format=full`): the same slides plus the setup and lab slides, where attendees run the [autopilot skill](https://github.com/kentcdodds/kcd-skills/tree/main/skills/autopilot) on their own repos. The attendee guide is [LAB-GUIDE.md](./LAB-GUIDE.md). The deck holds quick references and reminders; the FAQ at the end answers the questions that come up most, in Kent's own words. It's built on [Reveal.js](https://revealjs.com/) 5.2.1 (pinned from npm) and compiled into one self-contained web page. Reveal, its notes plugin, the fonts and the images are all inlined, and it makes no network requests, so it works from a USB stick with the venue Wi-Fi off, opened straight from disk. ## Present Open the hosted page, or `dist/index.html` straight from disk (no server needed). These are Reveal's own keys: | Action | Keys | | --- | --- | | Next / previous slide | Right / Left Arrow, Space, Page Down / Page Up, N / P | | First / last | Home / End | | Speaker view (notes, next slide, clock, timer) | S (opens a popup; allow it) | | Overview | O or Esc | | Fullscreen | F | | Jump to slide | G, then the slide number | | Pause (black screen) | B or . | | Toggle light / dark theme | T (this deck's own key) | | Key help | ? | Each slide has an id, and Reveal keeps it in the URL hash (for example `#/pr-3782`); `#pr-3782` works too. The break slide restarts an 8-minute countdown each time it's shown. The timer is editable: click it (or Tab to it), type `mm:ss`, `m:ss` or plain minutes, and Enter restarts it from that time. Escape or clicking away cancels; an invalid value is outlined in red and ignored. While you type, deck shortcuts (S, T, F, arrows) are off. ### Short talk, event, or full day The default is the short talk. Add `?format=full` for the full-day workshop: it adds the setup slide and Labs 1 to 4 plus show and tell (each with a lab countdown) and drops the short talk's "Your turn" slide. Combine with the other options, for example `?format=full&theme=light`. In-deck links keep the query string, so you stay in the mode you opened. `?event=aie-2026` is the one-hour AI Engineer Code Summit session (primary). It uses the hour slide set: hides the slides in `HOUR_HIDE` (`src/c/deck.js`), adds the two `data-format="hour"` slides (what autopilot does, after the ladder, and one combined Deploy slide), moves Your turn to right before the final slide, and applies `data/hour.json` notes for a session with no live autopilot run. The event entry in `data/events.json` sets the title, page title, and Podium URL; the build writes a QR for that URL (no external QR service). A small QR to the event page sits in the bottom-right corner of every slide except ones that already show that QR (the title). `?format=hour` is an alias for `?event=aie-2026`. The FAQ stays after the final slide, so it opens by link or `#/faq-...` without being in the main flow. Lab timers work like the break timer (click to edit), with one difference: they keep running while you visit other slides, and showing the lab slide again resumes the same countdown (a reload in the same tab resumes too). The break timer restarts each time. ### FAQ The FAQ sits after the Thank you slide: an index (`#/faq`) with a link to each of the 12 questions, and a link back to the index on every FAQ slide. The Questions slides and the Thank you slide link to the index. ### Light and dark The deck follows the system theme (`prefers-color-scheme`) and switches live when the system changes. Add `?theme=light` or `?theme=dark` to the URL to force one. T flips the theme for this browser and remembers it, so the speaker view matches; press T again to go back to following the system. `?static` turns slide transitions off, and `?linear` uses linear navigation. Both work like the kody.codes Reveal deck. ## Slides Slides are for the audience: a headline plus up to three short lines. Everything addressed to the speaker (demo beats, timing, citations, the full rung wording) is in the speaker notes. In file-name order: - `title`: Title - `factory`: Factory numbers - `lineage`: Lineage - `kody-what`: What Kody is (and you don't need it) - `thesis`: The loop - `pillars`: Three pillars - `lab-setup`: Setup and preflight (full-day only) - `section-1`: Section 1: Good PRs - `run-autopilot`: Run autopilot - `your-turn`: Your turn (short talk only) - `ladder`: The 13 rungs - `agents-md`: AGENTS.md is a router - `primitives`: Primitives: what exists, where it lives - `decisions`: Decision records - `friction-checks`: Friction becomes static checks - `pr-template`: The PR template is the rubric - `doors`: One-way vs two-way doors - `lab-1`: Lab 1: Kick off autopilot (full-day only) - `qa-1`: Questions? Next: Review + verification - `lab-2`: Lab 2: Review what your agent produced (full-day only) - `section-2`: Section 2: Review + verification - `ship-pr`: ship-pr: one tick at a time - `pr-3782`: ~9 taps. No error. They left. - `pr-3765`: It showed its work - `verify-see`: Agents need a way to see the app - `control-kody`: control-kody - `health-checks`: Feature tests prove features. Health checks prove the running version. - `qa-2`: Questions? Next: Break - `break`: Break - `section-3`: Section 3: Limit the blast radius - `flags`: Risky changes ship dark - `rollback`: Rollback: rehearse it - `backups`: A backup you've never restored is a hope - `credentials`: Credentials agents use but never see - `qa-3`: Questions? Next: Loops + the factory - `section-4`: Section 4: Keep improving - `loops`: Friction loop - `signal-loop`: Signal loop - `product-decision`: How a product decision happens - `codebase-cleanup`: Fork it: @kentcdodds/codebase-cleanup - `kody-mcp`: Where Kody MCP fits - `lab-3`: Lab 3: Engineer one gap (full-day only) - `lab-4`: Lab 4: Rerun and compare (full-day only) - `show-and-tell`: Show and tell, and close (full-day only) - `final`: Thank you - `faq`: FAQ - `faq-cost`: FAQ: What does this cost? - `faq-bloat`: FAQ: You don't read the code. What about bloat? - `faq-tests`: FAQ: Who writes the tests? - `faq-review`: FAQ: LLM review or static checks? - `faq-primitives`: FAQ: How do agents know which primitives to use? - `faq-adrs`: FAQ: ADRs: tickets, stale ones, monorepos - `faq-security`: FAQ: Is it secure? - `faq-kody`: FAQ: What is Kody, and do I need it? - `faq-prompting`: FAQ: How do you prompt and spec? - `faq-autonomy`: FAQ: How much do you review? What merges itself? - `faq-product`: FAQ: Product work: design, discovery, priorities - `faq-output`: FAQ: Don't you drown in agent output? ## Edit - Rung names, wording and scores: `data/rungs.json`. The slide shows the names; the wording and scores go in its notes. Set `showScores` to `false` to drop the scores. - Factory numbers: `data/factory.json`. Every number needs its query. - Events: `data/events.json`. Add a slug with `title`, `pageTitle`, `format` (the slide set), `podiumUrl`, `displayUrl`, optional `aliases` and `notes`. The build generates the QR. `?format=hour` is an alias for `aie-2026`. - Slides: `src/slides/*.html`, in file-name order. Add `data-format="full"` to a section for a full-day-only slide (or `data-format="short"` for short-talk only). - FAQ slides (`20-faq.html` to `32-faq-output.html`): keep the index links and the back links in step; verify checks both. Then run `npm install` (once), `npm run build`, and commit `app/assets.generated.ts` and `dist/index.html`. Run `npm run verify` to check every slide and the speaker view and save screenshots. ## Fonts Bricolage Grotesque and Wix Madefor Text are both licensed under the SIL Open Font License 1.1 and are embedded in the page unchanged. Reveal.js is MIT licensed (Copyright Hakim El Hattab); its licence header stays in the inlined code.