log inget access →

Autonomy and limits.

What Perfloop may start on its own, per repository, and the limits that stop work. Every control is in Setup under Automatic work. None of them lowers the proof bar, and none lets Perfloop merge.

Updated 7 October 2026.

Four controls per repository

  • Model upkeep. Keep model current rebuilds the model on Perfloop's schedule. Off, you or a coding agent start builds. On by default.
  • Case work. Keep working lets Perfloop pick the next case from the Frontier and work it, one automatic case at a time per workspace. Off, you or a coding agent start each case. Off by default. Before choosing a case, Perfloop can read its recorded candidates, verification findings, and Session outcomes.
  • PR feedback. Handle automatically lets feedback on a pull request Perfloop opened start a Session. A failed check starts one by itself. A comment or a review starts one when the code host says its author can push to the repository, with the rest waiting in Inbox; on Cursor Origin, with no push check. Off, every feedback Session waits for you. On by default.
  • Pull requests. Open automatically opens the pull request for a validated case without a member decision. Off, each proposal waits in Inbox. Off by default. Leave it off for a repo whose maintainers want a person to approve each pull request.

After a PR feedback Session stalls, Perfloop stops automatic retries for the same feedback, even if the branch moves. Changed feedback can start fresh work. To continue unchanged work, turn Handle automatically off and approve the Session in Inbox. The case stays open and keeps its evidence.

Stop work on a case also stops later automatic Sessions for that case. New feedback and branch changes leave it paused. If a PR feedback decision is waiting, use Approve & run on the case or in Inbox to continue it, even with Handle automatically on. Otherwise, use Work this case. Stopping does not close the case or remove its evidence.

Member sign-off is a separate workspace choice, also off by default. Every new commit keeps the Perfloop Agent Signed-off-by line. With member sign-off on, the approving member's display name and account email appear in an additional line and become public in the repo's commit history. Automatic publication uses the configured Admin's identity. An Admin enables this by selecting themselves with a complete profile; any Admin can turn it off. If that account loses access, automatic publication waits until an Admin repairs or clears the selection.

Turning a control off stops later automatic starts. It does not cancel a Session or build already admitted, and work interrupted by Perfloop's infrastructure can continue in a replacement Session. Removing a repository from scope resets its controls.

Turning Keep working back on discards an unused choice for that repo made before the pause. Triage compares cases again before choosing the next automatic case for that repo. Sessions already started can continue.

An automatic case interrupted by Perfloop's infrastructure can continue in replacement Sessions. Time in the original Session and its replacements counts toward the first Session's time limit until a new candidate or proof result is recorded. If that time is spent at an interruption, the case stays open for triage to choose again. This recovery limit does not apply to cases you or a coding agent start, or to PR feedback Sessions.

Research

One cadence per workspace: off, every hour, every day, every week, or a number of seconds. A new workspace that can run research starts at every day. Each turn runs one research Session on one active Initiative and is billable. An Initiative takes cadence turns only after its first research Session, which a coding agent starts with startResearch whatever the cadence is. setResearchCadence changes the cadence; zero turns it off.

Usage and the Case limit

Once a workspace has had a Usage period, Usage is the prepaid balance every Session draws on. When it is out, no new Session starts, whatever the controls say; a proven candidate can still open its pull request. Before that first period, work runs on an internal allowance with no balance to watch. Each case has a Case limit, the default maximum per case for the period, shown on the case page as Used / Case limit. A case at its limit with Usage remaining waits in Inbox for an Admin to set a new total or continue it without a limit. The Usage page shows the balance and every Session's use.

Near a Case limit, Perfloop gives a ready pull request proposal priority over optional work. Your repository's approval settings still apply. The hard limit can stop work before a proposal is ready.

Perfloop also bounds each Session and each model build on its own side. Those are cost controls, not settings.

In a self-serve workspace, a new Case Session uses the workspace's usual Session cap when Usage covers it. Otherwise, if Usage covers a smaller proof, the Session starts with a smaller cap and a 15-minute time limit. Free budget and purchased Usage follow the same rule. A replacement after an infrastructure interruption keeps the accepted cap and time limit, charged to the same Usage period.

Setup names the automatic work that Usage cannot fund. Other funded work can still run.

Also in this section: The loop, Case states, Steering and learning, Initiatives, Members, and The MCP server.

Questions: hello@perfloop.ai