Which AI agents does this loop work with?

claude-loop — iterative sessions with cost tracking is written for claude-code.

Is this loop safe to run unattended?

This loop is graded C (55/100) by looprepo's automatic safety evaluator, which checks for exit conditions, iteration budgets, verification steps, and scoping before publishing.

Loop/ralph Automationmedium riskintermediatesafety C · 55 · open-ended

claude-loop — iterative sessions with cost tracking

An automation harness that runs repeated Claude Code sessions while tracking cost and tokens per iteration — the reference answer to the number-one objection to agent loops: runaway spend.

prompt

→ Claude

Automation toolkit running repeated `claude` sessions with per-iteration cost and token monitoring; inspired by Dex Horthy's context-engineering talk. Cap the run at 25 iterations; leave remaining work for the next session.

claude-code

Implementation note

When to use: you are sold on iterative agent sessions but not on surprise bills — this harness exists specifically to answer the number-one objection to agent loops, runaway spend. Inspired by Dex Horthy's context-engineering talk. How it works: an automation toolkit that runs repeated claude sessions in a loop while recording cost and token usage per iteration, so you can see exactly what each cycle consumed rather than discovering the total afterward. The per-iteration granularity is what makes the data actionable: an iteration whose token count spikes is visible immediately, and trends across a run tell you whether the loop is converging or thrashing. Safety: measurement is the rail here — per-iteration cost visibility is what lets you set informed caps and kill a run that is trending wrong. Pair it with hard limits (iteration caps, budget ceilings), since tracking alone observes spend rather than stopping it.

Source: li0nel/claude-loop ↗

More automation loops

Ship production-grade apps autonomously

Loop/ralphnew

Hand an idea to Claude Code; it authors specs, designs, builds, tests, secures, and ships until enterprise done or budget exhausted.

prompt

→ Claude

# dare-to-be-stupid — Design (v2, refined) > A Claude Code plugin. One command, /dare , hands an idea or PRD to an autonomous > loop that authors specs, designs, builds, tests, secures, ships, fixes, and iterates > until the app passes an enterprise-production definition of done — or the budget dies. > > Named for the Weird Al song. The joke is that it runs the Ralph Loop on purpose , > with --dangerously-skip-permissions , and narrates the whole thing in the voice of an > '80s Junkion. Pre-production only. Never points at anything with users. This is v2. It keeps the strong core of the original spec (external reviewer, ratchet, guard hook, Junkion style) and adds the three phases the original left thin relative to the actual goal: PRD authoring, a design phase, and a real enterprise DoD including security, CI, docs/observability, and design quality (with quality plugins auto-installed). --- ## 0. The premise, in one paragraph The User builds documentation-first: spec → system docs → API contracts → CLAUDE.md → code. dare-to-be-stupid is the deliberate inverse, packaged as comedy that also solves two real engineering problems. It is a real build , not a joke ar

automationhigh riskclaude-code

source ↗

claude-progress.txt harness pattern (Anthropic)

Loop/ralph★ Anthropic

Anthropic's first-party file-as-memory harness for long-running agents: every fresh-context session recovers state from a progress file and the git log, does one unit of work, updates the file, commits, and exits.

prompt

→ Claude

Long-running agent harness: each fresh-context session starts by reading `claude-progress.txt` + git log to recover state, does one unit of work, updates the progress file, commits, exits. Initializer session sets up the file; coder sessions loop. Guardrails: Stop when the goal is verifiably met, or stop after 15 iterations, whichever comes first. Verify each pass by running the relevant tests or checks — self-reported success does not count. Keep changes minimal and never touch files outside the task’s scope.

automationmedium riskclaude-code

Complete all tasks in tasks.md

Loop/ralphnew

Work through your tasks.md file, completing each task until none remain or max iterations is reached.

prompt

→ Claude

/ralph-loop "Complete all tasks in tasks.md" --max-iterations 50

automationmedium riskclaude-code