Which AI agents does this loop work with?

/goal + Routines overnight combo is written for claude-code.

Is this loop safe to run unattended?

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

Loop/schedule Automationmedium riskintermediatesafety A · 95 Sabrina Ramonov

/goal + Routines overnight combo

The two-layer answer to how do I run this overnight: /goal drives in-session work to done, while a scheduled Routine keeps recurring unattended work running on Anthropic's cloud with your laptop closed.

prompt

→ Claude Code

/schedule a Routine (runs on Anthropic cloud, laptop closed) for recurring unattended work, and use `/goal` for in-session iterate-to-done — the two-layer overnight pattern. 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.

claude-code

Implementation note

When to use: the how-do-I-run-this-overnight question — you want in-session work driven to completion while you watch, and recurring unattended work running with the laptop closed. This is the two-layer answer. How it works: /goal handles the in-session layer, iterating a task to its done condition while you are at the keyboard. /schedule creates a Routine for the recurring layer, which runs on Anthropic's cloud on cadence — no local machine required, laptop closed. The split is deliberate: goals are for converging on a defined outcome now, Routines are for standing work that should happen without you. Safety: the two layers carry different risk profiles. Goals run under your observation with your local permissions; Routines run unattended in the cloud, so scope what a Routine can touch conservatively and give it report-heavy, mutation-light work until you trust its judgment. Put turn caps in your goal text as usual. Hardened 2026-07-27: explicit stop/cap/verification guardrails appended; regraded D→A.

Source: Sabrina Ramonov ↗graded A · 95/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 ↗