“So the next thing we're going to do is add flow control. Because the other problem that we had when we did this was that if we were at a customer site for a week or if we were traveling or spent six days working on slides instead of writing code, the PRs from all of our loops would just stack up. They'd duplicate work. They'd conflict. And we wouldn't get around to doing it. And the loop's work is important, but it's not that important. And so now we just had all this junk we had to deal with…”
Kyle Mistele, Co-founder, HumanLayer. A founder of a company that builds with coding agents every day and runs the migration loop he describes; HumanLayer sells AI coding tooling, so the talk also promotes its approach.
HumanLayer sells AI or agent tools or services, so it has a reason to publish flattering numbers about AI. The passage stays in the archive; read it with that in mind.
How this was checked
Checked against the source by a first reader, then confirmed independently by a second reader who fetched the source without seeing the first reader's notes (Independent review agent (Claude Sonnet), blind second pass from passage text and citation only, no repository access, 2026-11-03).
Whisper reads 'So the next thing we're going to do is add flow control… And so now we just had all this junk we had to deal with. It wasn't important.' The passage ends at 'deal with…' (the ellipsis marks the omitted next sentence). Exact otherwise.
How to cite this passage
Kyle Mistele (HumanLayer), “Loop Engineering from first principles”, AI Engineer (YouTube), 2026-07-25, at 15:12. https://www.youtube.com/watch?v=xIt_mTQp6mY Archived at https://the-ai-record.com/passages/humanlayer-loop-prs-stack-up-customer-site-2026
Context. Mistele has just described scheduling the migration loop to run once a day as a CI workflow, and goes on to the problem HumanLayer hit with the first version.
Context. Mistele is opening the part of his talk about how his company builds agent loops, after arguing that loops which produce unreadable pull requests are the wrong design.
Context. Mistele introduces the worked example he uses for the rest of the talk: a daily agent loop at HumanLayer that migrates RPC procedures to the Effect library.
HumanLayer