Boris Runs Thousands of Agents While He Sleeps. The Whole Trick Is One Command: /loop
The engineer who built Claude Code casually mentioned he has a few hundred AI agents running during the day and a few thousand doing deeper work every night. The mechanism behind it isn't exotic. It's one command — /loop — and it changes how operators should think about recurring work.
Field Notes #004 — I watched a short clip of Boris Cherny — the engineer who built Claude Code, the tool I use to run most of my businesses — get asked how he actually uses it day to day. His answer reframed how I think about the word “automation.” — Dakota
Someone asked Boris a simple question: how many sessions do you run?
Here’s roughly what he said, and the numbers are the point:
“Usually I have like five to ten sessions. And the sessions usually have a bunch of agents — so currently we probably have a few hundred agents going. Every night I have like a few thousand that are doing kind of deeper work.”
A few hundred during the day. A few thousand overnight. This is the person who wrote the tool, so he’s at the far end of what’s possible — but the mechanism he reached for to get there is not exotic, and it’s available to everyone reading this.
The trick isn’t an army of agents. It’s one command.
Boris named two ways he manages all of it. The first is the one everybody already knows: you ask Claude to spin up a bunch of sub-agents to divide a task and work in parallel. Useful, but it’s still you, sitting there, kicking it off.
The second is the one he said he keeps reaching for more and more:
“The thing I’ve been finding myself using more and more is loop. Slash loop. It’s the coolest thing — it’s the simplest thing that works. All it is is you have Claude use cron to schedule a job for some point in the future, and it’s a repeat job. It can run every minute, every five minutes, every day — however often you want.”
That’s it. /loop isn’t a model. It isn’t a new product. It’s Claude scheduling itself to wake up on an interval and do a job, over and over, without you in the chair.
He said he has dozens of these running right now. Two examples he gave:
- One babysitting his pull requests — fixing CI when it breaks, auto-rebasing branches that fell behind.
- Another keeping CI healthy — catching flaky tests before they cost anyone an afternoon.
Read those again, but cross out the engineering words. “Babysitting the thing that’s supposed to be moving forward.” “Catching the small problem before it becomes a wasted afternoon.” That’s not a developer task. That’s every job an operator does.
What this looks like when you don’t write code for a living
The instinct, watching a clip like this, is to file it under “cool, for programmers.” That’s the wrong file.
A loop is just a standing instruction: every interval, go check on this thing and handle it. The codebase is incidental. Swap in a business and the same pattern shows up everywhere:
- Every morning at 6:30, pull every overnight notification across Close CRM, Gmail, the calendar, the phones, and QuickBooks, rank them by what’s actually on fire, and have it waiting before the first coffee. (I already run exactly this — it’s the morning brief I’ve written about.)
- Every hour, check whether any inbound lead has gone unanswered past your promise window — and flag it, or answer it.
- Every night, scan the pipeline for deals that have gone quiet and draft the nudge.
- Every Monday, reconcile what got booked against what got invoiced and surface the gap.
None of those are hard. They’re just things that have to happen on a schedule and currently happen because a human remembers to do them. That’s the exact shape of work a loop eats.
The real lesson underneath the big numbers
It’s tempting to fixate on “a few thousand agents overnight” and decide this is a different universe than yours. It isn’t. Boris didn’t get there by being superhuman. He got there because he stopped doing recurring work himself and started writing down the work so something else could do it on a timer.
That’s the same gap I keep hitting in every business I look at. Not “do they have AI.” It’s: has anyone ever written down the work that happens over and over, in a form something else can run? Almost nobody has. So they keep paying a human — usually themselves — to be the cron job.
The frontier version is a few thousand agents grinding through a codebase at 3 a.m. The operator version is one loop that makes sure no lead sits unanswered overnight and no missed call goes uncalled-back. Same idea. Wildly different price tag for being the first one in your market to actually do it.
The future isn’t a smarter chatbot you ask for help. It’s standing instructions that run while you sleep — and quietly hand you a business that kept moving overnight.
This is the difference between AI that gives you advice and AI that does the work. We wire the second kind directly into the software you already run — your CRM, your phones, your calendar — so the recurring stuff happens on a timer instead of in your head. That’s AI Orchestration, and there’s a live one answering Dump Dynasty’s phone right now at +1 (605) 937-5430.
Clip: Boris Cherny on his Claude Code setup. Translated for operators.