A developer shared "loop," a tool that upgrades the Ralph loop — the while-loop that repeatedly pipes PROMPT.md into Claude — into a verified version. The original loop lacks memory between runs, trusts the agent's claim of "done," never stops itself, and allows the agent to edit its own tests. The tool adds a critic step before completion, framed by the author as "loop engineering": controlling what happens after the agent answers rather than the prompt itself.
A Substack essay, shared on Reddit, advocates 'loop engineering': building automated systems that prompt coding agents recursively until a verified goal is met, rather than hand-writing prompts. It catalogs five building blocks now shipping in Claude Code and Codex, plus on-disk memory as a sixth. For practitioners, it reframes agent work as system design around parallelism, skills, and verification loops.
A Substack essay, shared on Reddit, advocates 'loop engineering': building automated systems that prompt coding agents recursively until a verified goal is met, rather than hand-writing prompts. It catalogs five building blocks now shipping in Claude Code and Codex, plus on-disk memory as a sixth. For practitioners, it reframes agent work as system design around parallelism, skills, and verification loops.
Looperators is an open-source canvas that automates multi-agent loops. When Claude Code finishes a task, its diff is automatically sent to a reviewer agent; blocking issues wake the same Claude session to fix them, and the loop stops after a configurable number of laps. It solves the problem of manually orchestrating iterative code review and revision workflows for developers using Claude Code.
Looperators is an open-source canvas that automates multi-agent loops. When Claude Code finishes a task, its diff is automatically sent to a reviewer agent; blocking issues wake the same Claude session to fix them, and the loop stops after a configurable number of laps. It solves the problem of manually orchestrating iterative code review and revision workflows for developers using Claude Code.
This project extends Matt Shumer's Gauntlet Loop (Claude of Duty) to handle production-ready applications, integrating with CI, migrations, and a protected production branch. It uses LLM agents as builders and critics within each task to ensure quality against a reference, aiming to make the loop more practical for real-world development.
This project extends Matt Shumer's Gauntlet Loop (Claude of Duty) to handle production-ready applications, integrating with CI, migrations, and a protected production branch. It uses LLM agents as builders and critics within each task to ensure quality against a reference, aiming to make the loop more practical for real-world development.
Agent Vigil is a deterministic tool that verifies whether Claude Code agents actually did what they claimed in their session logs. It reruns tests, diffs file changes, checks paths, and cross-references tool calls, without using LLM judges. It helps developers trust agent outputs by catching discrepancies.
Agent Vigil is a deterministic tool that verifies whether Claude Code agents actually did what they claimed in their session logs. It reruns tests, diffs file changes, checks paths, and cross-references tool calls, without using LLM judges. It helps developers trust agent outputs by catching discrepancies.
A developer asks how others use agentic loops, citing Geoffrey Huntley's foundational ralph loop pattern. The discussion surfaces evolved practices and tools, including the /loop slash command, while noting context bloat concerns.
A developer asks how others use agentic loops, citing Geoffrey Huntley's foundational ralph loop pattern. The discussion surfaces evolved practices and tools, including the /loop slash command, while noting context bloat concerns.