loope
A stateless daemon that turns a labeled GitHub issue into a pull request using headless Claude Code, asking clarifying questions on vague issues, running an architect-versus-product-owner debate before implementing, and parking failures instead of retrying unattended.
loope watches GitHub issues for a configurable label and drives each one through to a pull request using headless Claude Code, with no server-side infrastructure to run beyond the loope binary itself. A vague issue produces clarifying questions rather than a guessed implementation, and before code is written an architect agent and a product-owner agent debate the design from a small set of rules the team writes once, aiming to make the decision the way a human product owner would.
Rate limits, budget caps and crashes park the issue with its full error message rather than retrying automatically, so a failure never silently burns tokens; nothing resumes work until the operator says so. Any number of machines and Claude Code accounts can run as workers pulling issues by label, coordinated only through the shared issue board with no separate queue, database or coordinator process, and a live dashboard shows every step's tokens, cost and session alongside per-account usage remaining.
It installs as a single Go binary for macOS and Linux and relies on the operator's own git, gh and claude CLIs.