Looper CLI
A background daemon loops over GitHub or Forgejo issues, drafts specs, reviews and fixes PRs until they are ready for human merge.
- 143 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The daemon creates branches, PRs and comments under your forge credentials without a human present.
- Agent loops spend tokens and can change code in the repository.
Install
- Works in
Manual install
curl -fsSL https://raw.githubusercontent.com/nexu-io/looper/main/scripts/install.sh | shFast path for macOS on ARM and Linux; then `looper bootstrap` and `looper project add`. Read the script before running it.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The daemon creates branches, PRs and comments under your forge credentials without a human present.
- Agent loops spend tokens and can change code in the repository.
This is third-party code. Review the repository files before installing.
What it does
Looper is a Go CLI and daemon that runs AI agents as an autonomous dev team across your GitHub and Forgejo repositories. The `looperd` daemon polls the forge, picks up assigned labeled issues and runs specialized agents: planner, reviewer, fixer and worker. Each loops until its own exit condition is met. The planner reads the issue and repository and drives a spec to a PR. The reviewer rereads the PR on every new commit. The fixer closes review comments and the worker implements the issue in isolated worktrees. Merging stays with a human. The `looper takeover` mode adopts a single PR, and the `pr-takeover` skill hands it to any agent with a single request.
Who it is for. Teams and solo developers with an issue stream on GitHub or Forgejo who want to hand routine planning, review and fixes to agents and keep merging for themselves.
Good fit when
- Labeled issues must become a spec and PR without manual launches.
- A PR is reviewed again on every new commit until it meets the bar.
- One PR must be carried to merge without watching it yourself.
- An agent in any client gets a request to take a PR over.
Not a fit when
- Agents must not get write access to the repository.
- The project lives on another platform, since only GitHub and Forgejo are supported.
- You need one interactive session with no daemon and polling.
Example request
Take this PR over until it merges: read the pr-takeover skill from the Looper README link and follow it, asking me when unsure.Limitations
Install is a script through `curl`, with ready builds for macOS on ARM and Linux on amd64 and arm64. The daemon works under your forge credentials (`gh auth status` or a Forgejo token) and can create branches, PRs and comments, so grant minimal rights and begin with one test repository. Agents take their models from configuration and spend tokens in a loop. Do not rely on automatic merging: Looper brings a PR to a state ready for a human merge.
How to disable. Stop the daemon and remove it with the commands in `docs/installation.md`, then revoke forge tokens and drop the `looper:` labels from repositories.
FAQ
What roles do the agents have?
The planner drives a spec to a PR, the reviewer checks the PR on each commit, the fixer answers review comments and the worker implements the issue. Each loop runs until its own exit condition.
How do I run it manually?
With `looper plan --project <id> --issue <num>`, `looper review <owner>/<repo>#<pr> --loop` and `looper work --project <id> --issue <num>`.
What does bootstrap do?
It interactively writes configuration, installs the managed daemon and starts `looperd`. The `--yes` flag is for scripts only.
How do I take over one PR?
Ask an agent to read `skills/pr-takeover/SKILL.md` and follow it. In background mode `looper takeover` carries the work.
Which forges are supported?
GitHub and Forgejo. GitHub needs `gh` authentication, Forgejo a token in an environment variable or a `tea` login.
Discussion
No questions or reviews yet.
Related
CLI toolsA pattern library and skill set for recurring agent loops: issue triage, dependency cleanup, PR babysitting
A Rust CLI and TUI: agents in containers, parallel tabs, TOML workflows from issue to PR and a scheduled agent squad
A local gate in front of git push: the branch goes through review, tests, docs and lint in a separate worktree before it reaches the remote with a PR
Orloj declares agents, tools and policies in YAML and runs multi-agent systems with queues, approvals and tracing.
A background process manager for agents: the agent starts a dev server and reads its logs, status and ports later, plus a TUI
devvm gives each project its own virtual machine with the right toolchains, where Claude Code and Codex cannot see your secrets
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Looper (this card) | no | 143 | |
| Claude Squad | no | 8,790 | a terminal app for starting parallel agent sessions by hand; Looper runs as a daemon over forge issues and drives PRs through roles |
| Orchestrator | no | 119 | one agent launches others on your request; Looper picks up labeled issues itself and loops until a PR is ready |
README in short
Looper keeps the forge as the source of truth and runs spec, review and implementation in isolated worktrees. Details are in the user guide at `docs/users-guide.md`.