Ralph v2 board-driven autonomous dev
Claude Code sequences research/plan/build/verify cycles against a GitHub Projects V2 board until backlog is empty.
# CLAUDE.md This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. ## What This Is ralph v2 (GH-1662) — a Claude Code plugin for board-driven autonomous development over a GitHub Projects V2 board. Two skills, one read-only agent, one typed board CLI, two courtesy hooks, and a scheduler-owned loop. The driving model sequences its own research/plan/build/verify; enforcement is code, not prose. Design record (normative): thoughts/shared/ideas/2026-07-31-ralph-v2-minimal-harness.md . The repo also ships two independent plugins: plugin/ralph-knowledge/ (semantic search over thoughts/, own MCP server + npm release) and plugin/ralph-playwright/ (UI-testing skills), plus plugin/ralph-demo/ (Remotion demo videos). ## Build & Test From the repo root: bash npm install # workspace dev deps (tsx, vitest) npx vitest run ralph/scripts/board.test.ts # the board CLI's contract suite npx tsc --noEmit # typecheck shellcheck -S error ralph/hooks/ .sh ralph/scripts/ .sh ralph-knowledge builds/tests from plugin/ralph-knowledge/ ( npm ci && npm run build && npm t
claude-code
More automation loops
Codex App Automations (Scheduled Agent Runs)
Codex's native answer to scheduled agent loops: define a prompt plus a schedule in the Codex app and it runs in the cloud on cadence — nightly dependency audits, morning issue triage — with no terminal open. The Codex-side equivalent of Claude Code Routines.
Define an Automation in the Codex app: a prompt + schedule that runs in the cloud on cadence (e.g., nightly dependency audit, morning triage of new issues), no terminal open.
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 risk
Ship PRD stories via dual-agent loop
Ralph runs a generator and evaluator in tandem until all user stories pass acceptance criteria and browser tests.
# 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
Keep task probes passing
Run a task until its probe passes, exhausting reasonable attempts before reporting blocked or complete.
/goal semantics. The cap exists so the orchestrator can redirect on genuinely stuck tasks (one redispatch via the orchestrator-side rule, then needs-attention ), not so the subagent can give up early. The subagent must not return STATUS: COMPLETE until the probe passes; it must not return STATUS: BLOCKED before exhausting reasonable attempts
automationmedium risk