Perfloop is always-on performance engineering for your code. It hunts the repos you select for performance wins and bugs, proves each change with paired benchmarks and your tests, and opens a pull request with the evidence attached, written the way your team writes code.

What it does on GitHub

• Reads code in the repositories you select, and nothing else.
• Pushes a branch and opens a pull request only for a change that has been proved and approved. This is why it needs write access to contents and pull requests.
• Comments on pull requests and replies to review feedback, so you can steer the next change.
• Reads CI results and commit status to confirm a change passes your checks.

What it never does

Perfloop never merges, approves, requests changes on, or closes a pull request, and it pushes only to the branch of its own pull request. Its proxy enforces this on every request, scoping each token to the action at hand. Installation tokens expire within an hour.

It has no access to repository settings, Actions, secrets, members, deployments, or your organization. Your code is never used to train models.

Keep a branch protection rule on your default branch that requires a reviewed pull request, and you review and merge every change.

How the connection works · Security