Which AI agents does this loop work with?

Draft weekly release notes is written for claude-code.

Is this loop safe to run unattended?

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

Loop/schedule Automationlow riskbeginnersafety A · 100 looprepo

Draft weekly release notes

Every Friday at 2pm, draft release notes from merged PRs into releases/DRAFT.md and verify all links resolve.

prompt

→ Claude

/schedule every Friday at 2pm, draft release notes from the PRs merged since the last draft: group changes into features, fixes, and docs, write one plain-English line per change with the PR link, and save to releases/DRAFT.md. Draft only — a human edits and publishes; never post or send anywhere. Verify every PR link resolves and every merged PR since the last run is covered before saving. Stop after 1 pass per run.

claude-code

Source: looprepograded A · 100/100 — how grades work →

More automation loops

claude-progress.txt harness pattern (Anthropic)

Loop/ralph★ Anthropic A

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

Anthropic Engineering ↗

Run an autonomous dev team across GitHub repos (looper)

Loop/ralphcommunity B

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.

automationmedium riskclaude-code

nexu-io/looper ↗

Auto-complete TODOs, keep tests green

Loop/loopcommunity Cnew

Work through unfinished TODOs in progress.md, implement each, run tests/lint/build, and continue until the backlog is done.

prompt

→ Claude

/loop 0s --name dev --ask-never --safe --no-overlap --batch 5 --compact-every 200m --checkpoint-only --progress-file progress.md Treat progress.md as the project state. Continue with the next unfinished TODO, implement it, mark completed items, add useful follow-up TODOs, run tests/lint/build when available, and keep going while work remains

automationmedium riskclaude-code

ByBrawe ↗