Makes a multiplayer coding agent IDE and cloud, which brings agent sessions, plan artifacts and code diffs together for teams.
HumanLayer sells AI or agent tools or services, so it has a reason to publish flattering numbers about AI. Its passages stay in the archive and carry this flag.
“ And of course, once you're feeling confident in the loop, we're going to want to speed it up, right? I have 150 RPC procedures to migrate. If I do one at a time, it's going to take six months, which is way longer than I want to wait.” Kyle Mistele Co-founder, HumanLayer · Executive
Context. Mistele is explaining why HumanLayer would raise the number of procedures its loop handles per run.
Talk: Loop Engineering from first principles , AI Engineer (YouTube) , July 25, 2026, at 16:23 .
[ Grade B ] Said in the last year Sells AI tools Passage page
“ if you're just getting started with AI, try to keep it around 100,000 tokens. For larger million context window, we … this up to … 200,000 tokens, but I've regularly tried to keep it under 60 for the hardest problems. I've regularly gone over 300K for things where I'm just kind of riffing with the agent, and I'm just … too lazy to compact it and move on and do a new one.” Dex Horthy CEO, HumanLayer · Executive
Context. Horthy is answering the moderator's question on whether context rot and context engineering are solved now that context windows are larger.
Talk: The Great Loops Debate , AI Engineer (YouTube) , July 17, 2026, at 28:36 .
[ Grade B ] Said in the last year Sells AI tools Passage page
“ And so my advice is … instead of trying to automate everything end-to-end, build these small incremental loops throughout your system, and you will wake up one day and you will be moving two to three times faster while still being able to read the code, while still owning the architecture.” Dex Horthy CEO, HumanLayer · Executive
Context. Horthy is answering the moderator's question on how to reach fully autonomous software factories if two to three times is what coding agents give most engineers.
Talk: The Great Loops Debate , AI Engineer (YouTube) , July 17, 2026, at 48:33 .
[ Grade B ] Said in the last year Sells AI tools Passage page
“ And every morning, we walk into the office to a small incremental PR that's low risk. And when we first did this, it was actually really frustrating, and we turned the loop off … because we had to constantly update the skill, we had to constantly check out the branch, change the skill, change the code, commit and push, and our loop was actually really high friction, right?” Kyle Mistele Co-founder, HumanLayer · Executive
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.
Talk: Loop Engineering from first principles , AI Engineer (YouTube) , July 25, 2026, at 13:48 .
[ Grade B ] Said in the last year Sells AI tools Passage page
“ At HumanLayer, we like to build out what we call golden patterns by hand before setting the agent loose. These are just like idiomatic hand-written examples for the agent to follow because they're just pattern replicators and otherwise you're getting what's in the docs or what the agent knows from the internet.” Kyle Mistele Co-founder, HumanLayer · Executive
Context. Mistele describes how HumanLayer prepares the skill given to the agent that makes each change in its migration loop.
Talk: Loop Engineering from first principles , AI Engineer (YouTube) , July 25, 2026, at 12:47 .
[ Grade B ] Said in the last year Sells AI tools Passage page
“ 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 · Executive
Context. Mistele explains why HumanLayer added a rule that a loop skips its run while its previous pull request is still open.
Talk: Loop Engineering from first principles , AI Engineer (YouTube) , July 25, 2026, at 15:12 .
[ Grade B ] Said in the last year Sells AI tools Passage page
“ So today I want to talk about what I think works in the real world and what we've started doing at HumanLayer, which, to be clear, is still building loops, right? I think loops are super powerful, but we can design loops and still read the code. In fact, we can design loops that make it easier to read the code because the loops are making the code better.” Kyle Mistele Co-founder, HumanLayer · Executive
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.
Talk: Loop Engineering from first principles , AI Engineer (YouTube) , July 25, 2026, at 4:03 .
[ Grade B ] Said in the last year Sells AI tools Passage page
“ To illustrate that, I'm going to walk through a control loop that we use internally at HumanLayer. For our loop, we are incrementally migrating our RPC API to Effect. We adopted it for some of our race prone code. We like it, so we're adopting it across the rest of our code base.” Kyle Mistele Co-founder, HumanLayer · Executive
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.
Talk: Loop Engineering from first principles , AI Engineer (YouTube) , July 25, 2026, at 9:09 .
[ Grade B ] Said in the last year Sells AI tools Passage page
HumanLayer