Everything Alex Krentsel said on any show that made the record, most notable first. Each card names its show and opens the statement there.
Krentsel: AI self-improvement requires collapsing outer optimization loops
“You have some outer system that's optimizing some inner system. What if you want to optimize the way you're doing? You're optimizing, then you need some outer, outer loop, and it's this infinite recursion out. And the only way I think out of that is to collaps…”
Krentsel: AI takeoff flywheel will emerge from agents iterating on harness code
“There's a moment like that happening now, and this is the moment that's going to be a flywheel, I feel like, because this takeoff moment will come from being iterating in the same layer that you are producing, I think.”
Krentsel: OpenClaw, Pi, and Claude Code hardcode static agent policies
“These are all policy decisions that are static, that are defined for OpenClaw, or for Pi, or for Clawed code, if you look at their Source code. And so that is the kind of, that is the policy of what an agent is, the tools it can use, the skills it has, how it …”
Krentsel: Improving AI models should architect their own agent harnesses over humans
“We believe All of that needs to be improvable by the agent, especially as the agents keep getting better, because as they keep getting better, it's this better lesson. You don't want to over-specialize because you don't want the human kind of deciding all thes…”
Krentsel: Exo autonomously modified its code to inspect Pokémon game RAM
“We've had XO running, playing, playing Pokemon. And while it's running, the system itself decided to try inspecting the like RAM of the game and then went and mapped the RAM to, and people have reversed in the past, people have reverse engineered this manually…”
Krentsel: Harness architecture must enforce agent rules instead of model alignment
“My bet is this though, that people keep trying to get models to do things that align with their goals and alignment is an unsolved problem. We keep trying to like RLHF, like try to align these models to do the right thing. In harness space, we actually have an…”
Krentsel: Decoupling executor from harness enables safe agent self-evolution
“What this gives you this nice split is it gives you an isolated execution environment down here. It gives you protected state, and then it has a very explicit stateless layer that's safe for self evolution. So the executor can propose changes to itself in a wa…”
Krentsel: Exo autonomously re-architected its Discord adapter, cutting costs by 96%
“We asked it, Hey, I noticed, I asked, Hey, but how much did the last message cost in the discord adapter?
And it was like, it was.
It's like, are you serious?
16 cents.
That's actually crazy.
Like.
Go work on driving that down.
And so it went and re-architecte…”
Krentsel: Exo enables AI agents to safely edit themselves at runtime
“In a nutshell, XO is an agent that's fully recursive. So it's able to safely edit all aspects of itself at runtime to kind of get better at the task that it's working on. And it's enabled by this very kind of minimal, but opinionated harness architecture that …”
Krentsel: AI agents are fundamentally LLM calls wrapped in context construction machinery
“I think about an agent as an LLM call that is wrapped in machinery that's used to construct context. It's really a big context construction machine. And also it provides a way of executing actions.”
Krentsel: Agent teleportation is only needed when scaling parallel tasks
“In a world where you're running a single agent, working on a single task, there is like very little need for teleporting your stuff away. Just, you either run it locally while you're working, or by the way, if you want it to just be always on, you have to run …”
Krentsel: Agent logic belongs in the executor while state belongs in harness
“The way you choose to record or inject memory lives in the executor, but the actual memories themselves go down in the exo harness as artifacts for that conversation or for that agent. And so it's kind of like the, how you do things is defined in the executor.…”
Krentsel: OpenClaw agent threads cannot be interrupted during active execution
“Once an agent kind of goes and starts working on a thing in a thread, that thread is not interruptible. As the thing is off working, if you try to ping it just won't respond. You don't even know what it's doing, which is really frustrating.”
Krentsel: Interruptible agent workflows will mirror OS-style background task management
“So the way that we're going to need to reinvent what that kind of interactive interruptible work looks like in the agent layer, which is separate from the work going on, I think in the, like in the model layer. And in this like interactive model space, but I t…”
Krentsel: Self-improving AI requires explicit objective evaluators to avoid misalignment
“In all these optimization problems, the final difficulty is
You always have to provide some evaluator and that evaluator has to kind of reflect your goals, because otherwise there's no signal for the thing to hill climb or to optimize, or that signal, it might…”
Krentsel: Exo Automatically Rolls Back Runtime Executor Rebuilds That Fail
“And we have in the exo harness, a special garden guardian kind of process that will allow the executive to be rebuilt at runtime mid step. And also provide some sort of kind of soaking process where After being rebuilt, we try to bring up the executor, let it …”
Krentsel: The Exo Harness Is Running in Production at Braintrust
“The EXO harness and agents built over top of it is running in production at Braintrust.”
Krentsel: A16z GP Martin Casado writes code daily for the Exo project
“Martine really codes. Martine's really in this. Scoting day to day. So it's been super fun, the three of us working together. If you look at the commits, we're all there.”