loope — event-driven loop

loope is an event-driven loop that watches one GitHub repository for issues labeled ai-agent, picks the best one, and drives it all the way to a pull request using headless Claude Code sessions running inside git worktrees. Issue state lives entirely in GitHub labels, so the daemon itself is stateless and safe to restart.

Label an issue ai-agent and each poll cycle loope triages the best candidate, runs a bug- or feature-specific pipeline of Claude sessions in an isolated worktree, and — if the work produced commits — pushes the branch and opens a PR. A live web dashboard shows every issue it has touched. See How it works for the full lifecycle.

_{The live dashboard — every tracked issue, its pipeline steps, and per-step cost, tokens, and Claude session id.}

_{Label an issue ai-agent and loope drives it to a PR — closing it ai-done, or parking it ai-needs-info when it needs clarification.}

Install

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

This downloads the prebuilt binary for your OS/arch from the latest release, verifies its checksum, and installs it to /usr/local/bin. Binaries are published for macOS and Linux on amd64 and arm64.

loope is a wrapper around your local toolchain: it needs git, gh (authenticated), and claude on your PATH at run time. See Installation for prerequisites, the --doctor preflight, and building from source.

Then point it at a repo and run:

# grab loope.json.example from this repo (or the release archive), then:
cp loope.json.example loope.json   # edit repoPath / repoSlug / workDir
loope --config loope.json          # polls for labeled issues, serves the dashboard on http://localhost:8080

Documentation

Contributing

Issues and pull requests are welcome. CI (go build, go vet, go test ./...) must pass; please keep new behavior covered by tests that run without the network or external CLIs. See Development.

License

MIT © ngthluu