perflooplog 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 30 September 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.
  • 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.

Each publication records the repo's contribution-policy excerpt and its source. An Admin can require that this guidance allows agent contributions before a pull request opens automatically. With that setting on, restricted, unknown, or missing guidance waits for a member's approval. It also stops automatic replies, withdrawals, and reactions on pull requests whose recorded guidance restricts agent contributions. The setting is off by default.

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. Neither publication setting requires the other.

Turning a control off stops later automatic starts. It does not cancel a Session or build already admitted, and if Perfloop's own infrastructure interrupts one, the fresh Session that replaces it still starts. Removing a repository from scope resets its controls.

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.

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

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

Questions: hello@perfloop.ai