Which AI agents does this loop work with?

Deterministic backlog loop for Codex CLI 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 GitHub

Deterministic backlog loop for Codex CLI

A Codex-first autonomous runner that pulls exactly one task per iteration from a JSON backlog with fresh context each run and a JSONL audit log for full traceability.

prompt

→ Claude Code

Autonomous runner: exactly one task per iteration pulled from a JSON backlog, fresh context each run, JSONL audit log for traceability; optional Claude Code interleaving. Cap the run at 25 iterations; leave remaining work for the next session.

claude-code

Implementation note

When to use: you want Ralph-style backlog grinding with Codex CLI as the engine, in contexts where traceability matters — you need to answer what the loop did on iteration 14 after the fact. How it works: an autonomous runner that pulls exactly one task per iteration from a JSON backlog, runs it with fresh context, and appends a JSONL audit log entry per iteration, giving the whole run a machine-readable paper trail. The one-task-per-iteration discipline keeps each run bounded and attributable, and the JSON backlog is the shared state between iterations. It can optionally interleave Claude Code runs alongside Codex. Safety: the JSONL audit log is the distinguishing rail — full traceability of what ran, when, and against which task, which most homemade Ralph loops lack entirely. Keep backlog items small and independently shippable, and bound total iterations yourself, since the runner's determinism governs task selection, not spend.

Source: nibzard/looper ↗graded C · 55/100 — how grades work →

More automation loops

Ship PRD stories via dual-agent loop

Loop/ralphGitHub A

Ralph runs a generator and evaluator in tandem until all user stories pass acceptance criteria and browser tests.

prompt

→ Claude Code

# Ralph Harness — Agent Instructions ## Overview Ralph Harness is an autonomous AI agent loop that runs AI coding tools (Amp or Claude Code) repeatedly until all PRD items are complete. Each iteration is a fresh instance with clean context. Ralph supports two modes: | Mode | Architecture | When to use | |------|-------------|-------------| | simple | Single agent (self-implement, self-check) | Quick tasks, backend-only stories, well-defined small changes | | harness | Generator + Evaluator (dual-agent with contract) | UI-heavy features, complex stories, when quality is critical | ## Architecture: Harness Mode ralph.sh orchestrator │ ├── Planner (prd.json) │ Defines user stories, acceptance criteria, dependencies │ ├── Generator (generator-prompt.md) │ Drafts sprint contracts → Implements stories → Fixes based on feedback │ └── Evaluator (evaluator-prompt.md) Reviews contracts → Signs/locks → Tests in browser → Scores → Writes feedback ### Per-Story Flow 1. Contract Negotiation : Generator drafts contract.json → Evaluator reviews → Back-and-forth until Evaluator signs → Contract locked (immutable) 2. Build : Generator reads Hard cap: stop after 30 iterations even if PRD items remain.

automationhigh risk

claude-code

m18897829375 ↗

Ship production-grade apps autonomously

Loop/ralphGitHub B

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

prompt

→ Claude Code

# 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 risk

claude-code

trevor-ryan-burkholder ↗

Set and ship autonomous goals

Loop/goalGitHub B

Run a persistent goal autonomously until completion, routing each task to the optimal model for cost and capability.

prompt

→ Claude Code

/goal <objective · /loop <task | Set a persistent goal · run autonomously until complete (≤25 turns) |

automationlow risk

claude-code

adulari ↗