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.

/ralph automationmedium riskintermediatesafety B · 75 · open-ended

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

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 ↗

More automation loops

Run workflows with dynamic sub-agents

/goalnew

Split a task into packets, run sub-agents in parallel, synthesize results, and verify completion.

prompt

→ Claude

/goal loop and verify until complete

automationlow risk

Run agent turns until goal met

/goalnew

Agent executes repeated turns toward a condition, with a lightweight evaluator checking progress after each turn until the goal is reached.

prompt

→ Claude

/goal <condition turns a prompt into a durable objective. Thanos immediately starts a turn toward the condition, and after each turn a fresh, tool-less side-channel evaluator (a one-shot completeSimple call, not a subagent — so no extra agent turn and no re-entrancy) reads the last turn's evidence and returns MET / NOT MET . NOT MET auto-continues another turn with the reason as guidance; MET clears the goal and records the achievement. Unparseable evaluator output is treated as NOT MET (fail-safe: it never declares a false "done

automationmedium risk

Run agent until goal met

/goalnew

Queue agent turns with goal context until your objective is achieved, treating the goal as untrusted data.

prompt

→ Claude

/goal <objective , after /goal resume , and after every agent turn that leaves the goal active , the extension queues Codex's goal continuation prompt as hidden model-visible context. The objective is XML-escaped and wrapped as untrusted user data so it does not become higher-priority instructions

automationlow risk

source ↗