Which AI agents does this loop work with?

Triage a repo in five minutes is written for claude-code, codex.

Is this loop safe to run unattended?

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

Loop/loop Maintenancemedium riskintermediatesafety C · 65 Forward Futurepre-dates current gate · under review

Triage a repo in five minutes

Triage the repo, route bounded maintenance to dedicated threads, and require proof and permission before anything lands.

prompt

→ Claude Code

While repository maintenance is active, wake every five minutes. Triage [repositories] and read each repository thread's latest state. Reuse one thread per repository; assign its highest-value bounded task only within granted permissions, and do not interrupt coherent active work. Require tests, live proof, autoreview, and green CI before work can land. Escalate product, access, security, or irreversible decisions. Record meaningful changes and stop when every item is landed, decision-ready, blocked, or has no work.

claude-code · codex

Use this when

Use this when Codex may coordinate maintenance across several active repositories and you want parallel work to stay steerable without duplicating or micromanaging threads.

How it runs

Define the repository scope, exclusions, and separate permissions for triage, delegation, implementation, push, CI repair, merge, and release.
Every five minutes, refresh each repository queue and read the latest state of its existing thread before choosing the highest-value eligible item.
Reuse one thread per repository, assign one bounded task, and let coherent active work continue unless it is blocked, stalled, unsafe, or off course.
Require tests, live proof, autoreview, and green CI; record the evidence, then route the next item or present the owner with one exact decision.

Done when

✓ Every repository item reaches a proven handoff or terminal state. Authorized autonomous work lands with evidence; other items are decision-ready, blocked with one exact ask, or recorded as a clean no-op.

Why it works

A five-minute heartbeat keeps the control plane current without turning polling into micromanagement. One thread per repository preserves context, while proof and authorization gates make autonomous landing auditable.

Implementation note

The source pairs Maintainer Orchestrator with github-project-triage, autoreview, and computer use for live proof. A heartbeat automates observation, not authority: triage, delegation, implementation, push, merge, and release remain separate permissions. Read current thread state before steering, and never duplicate or interrupt active work.

Source: Forward Future ↗graded C · 65/100 — how grades work →

More maintenance loops

Upgrade to current Node LTS

Loop/goallooprepo B

Move the project to the current Node LTS across .nvmrc, CI config, Dockerfiles, and engines, fixing deprecations until everything is green on the new runtime.

prompt

→ Claude Code

/goal the project runs on the current Node LTS — update .nvmrc, the engines field, CI workflow files, and any Dockerfile base images to the LTS version, then run install, build, lint, and the full test suite on it, fixing deprecation warnings and breakages one at a time; stop when all are green or after 15 turns

maintenancemedium risk

claude-code codex cursor

looprepo ↗

Upgrade dependencies one at a time

Loop/goallooprepo B

Walk through outdated dependencies one package per turn, upgrading, running the full check suite, and pinning back anything that breaks.

prompt

→ Claude Code

/goal `npm outdated` lists no minor or patch updates — upgrade exactly one package per turn, run tests, lint, and build after each, commit if green, and pin the previous version with a note in UPGRADE-BLOCKERS.md if it fails; stop after 20 turns

maintenancemedium risk

claude-code codex cursor

looprepo ↗

Triage untriaged issues to zero

Loop/looplooprepo A

Pick the oldest untriaged issue, validate it against the current build, then label it, close if obsolete, or document repro steps—one per turn until the queue empties or 12 iterations pass.

prompt

→ Claude Code

/loop pick the single oldest untriaged issue in the tracker; reproduce or validate it against the current build, then either label it (area, priority, effort), close it with a polite explanation if it is obsolete, or write the missing repro steps. One issue per iteration, never close anything that still reproduces, and propose bulk closes for maintainer review instead of executing them. Continue until the untriaged queue hits zero — stop after 12 turns and report the triaged/closed/escalated counts.

maintenancelow risk

claude-code