Deterministic backlog loop for Codex CLI
A Codex-first autonomous runner that pulls exactly one task per iteration from a JSON backlog with fresh context each run and a JSONL audit log for full traceability.
Implementation note
When to use: you want Ralph-style backlog grinding with Codex CLI as the engine, in contexts where traceability matters — you need to answer what the loop did on iteration 14 after the fact. How it works: an autonomous runner that pulls exactly one task per iteration from a JSON backlog, runs it with fresh context, and appends a JSONL audit log entry per iteration, giving the whole run a machine-readable paper trail. The one-task-per-iteration discipline keeps each run bounded and attributable, and the JSON backlog is the shared state between iterations. It can optionally interleave Claude Code runs alongside Codex. Safety: the JSONL audit log is the distinguishing rail — full traceability of what ran, when, and against which task, which most homemade Ralph loops lack entirely. Keep backlog items small and independently shippable, and bound total iterations yourself, since the runner's determinism governs task selection, not spend.
More automation loops
Ship production-grade apps autonomously
Hand an idea to Claude Code; it authors specs, designs, builds, tests, secures, and ships until enterprise done or budget exhausted.
claude-progress.txt harness pattern (Anthropic)
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.
Complete all tasks in tasks.md
Work through your tasks.md file, completing each task until none remain or max iterations is reached.