Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-14 · high
It traces the pattern to Karpathy's autoresearch repo, sitting near 90,000 stars on GitHub.
Why now: The guide posted July 12, two days before this briefing picked it up.
A July 12 guide sorts agent loops into four types: heartbeat, cron, hook, and goal, per MarkTechPost.
That distinction matters if you've got any agent running on a schedule instead of firing off a one-time prompt. A heartbeat loop runs on a short interval no matter what's happening, whether there's work to do or not. Cron is the familiar version, fixed times, fixed cadence. Hook loops wait, then react, firing when a PR lands or CI fails. Goal loops are different in kind: they keep iterating until a success condition is met, then they stop on their own.
MarkTechPost traces the whole pattern back to Karpathy's autoresearch repo, which sits near 90,000 GitHub stars. That's the reference point the taxonomy gets built around.
This maps onto how I already think about my own scheduled jobs, and it's made me realize I've been sloppy about naming them. A job I call cron might actually be a goal loop wearing a schedule as a costume, one that should stop the moment it hits a condition instead of firing at a fixed hour whether there's anything to do or not.
The fix isn't complicated. Look at what actually ends the job: a clock, or a condition? If it's a condition, stop calling it cron.
The guide doesn't say what happens when a goal loop never converges, or a hook never fires. Naming four loop types is the easy part. Documenting how each one fails is what'll actually be useful.
Each link below shares sources, entities, or timing with this story.
LLM Wiki built by Karpathy / Shared entity: Karpathy / Earlier coverage
Linked by a graph relationship (LLM Wiki built by Karpathy); both cover Karpathy; earlier Karpathy coverage from 2026-04-30.
Loop uses Claude / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Loop uses Claude); both cover Karpathy, Loop; overlapping topics (agent, engineering, loop).
Loop uses Claude / Shared entity: MarkTechPost / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Loop uses Claude); both cover MarkTechPost; reported by the same outlet (marktechpost.com).
Loop uses Codex / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (Loop uses Codex); both cover July, Karpathy; earlier July coverage from 2026-04-28.
Loop uses Claude / Shared topic / Tension
Linked by a graph relationship (Loop uses Claude); overlapping topics (agent, engineering, prompt); pushes against this story (but).
Loop uses Codex / Shared entity: Karpathy / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Loop uses Codex); both cover Karpathy; overlapping topics (actually, agent).
Loop uses Claude / Shared entity: July / Earlier coverage
Linked by a graph relationship (Loop uses Claude); both cover July; earlier July coverage from 2026-07-13.
Linked by a graph relationship (Loop uses Claude); both cover July; earlier July coverage from 2026-05-13.