loope

Label a GitHub issue. Get a pull request.
An always-on loop that turns your issues into reviewed PRs with Claude Code — with no infrastructure to run.

Why loope

• You add one label. ai-agent on the issue you already wrote. That's the whole workflow.
• It asks before it guesses. A vague issue gets you questions, not a wrong PR.
• Design first — with your product owner in the room. An architect agent debates a product-owner agent that decides the way you would, from a few rules you write once.
• Ships like a teammate. A PR that closes the issue, a hand-verification checklist, and a review pass before anything is called done.
• Failures park. They never loop. Rate limit, budget cap, crash — the issue is parked with the full error and nothing retries until you say so. It never burns tokens unattended.
• One board. Many machines. Every account. Run workers on as many machines and Claude Code logins as you have; route issues by label. The issue board is the only thing they share — no queue, no database, no coordinator.
• See every step, and what it cost. Tokens, cost and session per step; one fleet view of every worker and how much usage each account has left.

Install

curl -fsSL https://raw.githubusercontent.com/ngthluu/loope/main/install.sh | sh
loope --config loope.json

One Go binary for macOS and Linux. Bring your own git, gh and claude — nothing else to run. Start from worker/loope.json.example; see Installation.

Learn more

Guide	What's inside
How it works	The lifecycle, the label state machine, the confidence gate
Installation	Prerequisites, --doctor, labels, building from source
Configuration	Models, retries, persona, per-worker labels, fleet telemetry
Dashboard · Fleet telemetry	What you see while it runs
Operations	Always-on behaviour, failure handling, running as a service
Development · Release notes	Contributing and what changed

License

MIT © ngthluu