Loopflow

LoopFlow

Stop prompting your coding agent. Design the loop that prompts it.

LoopFlow turns Claude Code into a system that runs itself: you declare a goal, a pipeline of agents, and a verification gate in one YAML file — LoopFlow iterates until the gate passes, the budget runs out, or the attempt limit is hit. One agent writes, a *different* agent checks, and a memory file makes every run smarter than the last.

📺 Demo video

  LoopFlow demo — release-check loop, 2 iterations

Why loops?

For two years the workflow was: write a prompt, read the output, write the next prompt. You held the tool the whole time.

That's changing. As Boris Cherny (creator of Claude Code) put it: *"I don't prompt Claude anymore. I have loops running that prompt Claude."*

A loop is a recursive goal: you define what "done" looks like, and the agent iterates until it gets there. But doing this raw has three sharp edges:

1. Agents grade their own homework. The model that wrote the fix will happily declare it works.
2. Unattended loops burn money. A loop running itself is also a loop making mistakes — and spending tokens — unattended.
3. The agent forgets everything between runs. Every run re-derives what the last run already learned.

LoopFlow is a small, sharp tool built around exactly those three problems:

No API keys, no daemon, no cloud. If claude works in your terminal, loopflow works.

Quickstart

Requirements: Node 18+, Claude Code installed and authenticated.

Anatomy of a loop

What happens when you run it

- Each step is one headless Claude Code run (claude -p). Steps see the loop's memory, the outputs of earlier steps in the iteration, and — on retries — the gate's feedback.
- A gate must end with VERDICT: PASS or VERDICT: FAIL. No verdict counts as FAIL: *an unverified pass is…