Which AI agents does this loop work with?

Run an autonomous dev team across GitHub repos (looper) is written for claude-code.

Is this loop safe to run unattended?

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

Loop/ralph Automationmedium riskintermediatesafety B · 75 · open-ended GitHub

Run an autonomous dev team across GitHub repos (looper)

Runs Claude Code/Codex as an autonomous multi-role dev team — planner → reviewer ↔ fixer → worker — across all of a user's GitHub repos, entirely driven by issue labels. Each loop runs in its own git worktree so multiple repos/issues proceed in parallel without collisions.

prompt

→ Claude Code

Register a repo with looper, then label an issue `looper:plan` and assign it to yourself. The planner reads the issue, explores the repo, drafts a spec, critiques and revises it, and opens a spec PR labeled `looper:spec-reviewing`. A reviewer re-reads the PR on every commit and posts inline review threads; a fixer pulls those threads, addresses them in its own worktree, and pushes, ping-ponging with the reviewer until every thread is resolved. Once labeled `looper:spec-ready`, a worker implements the spec, runs checks, and iterates on its own output until checks pass and the PR is ready for human review and merge. Every phase transition is gated on a GitHub label via `looperd`, so a human can pause or take over at any boundary.

claude-code

Implementation note

High risk: opens PRs, pushes commits, and runs across multiple repos with label-gated human checkpoints as the only stop mechanism — keep branch protection and required human PR approval on, and pilot on one non-production repo before enabling multi-repo mode. This is a distinct, actively maintained, specifically named tool with its own label-based orchestrator (looperd); it is NOT the same project as the already-published 'Looper — design-review your loop before running it' entry (source: ksimback/looper, a plan-first design-review skill with no GitHub/label integration) and is thematically adjacent to but more specific than the already-published 'Multi-repo autonomous dev team loop' — evaluator/human reviewer should confirm no duplicate before publishing.

Source: nexu-io/looper ↗graded B · 75/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 ↗