Quickstart.

From a new account to the first work Perfloop runs on your code, and where its result shows. One task per step, with the page and the button the app shows.

Steps

1 · sign up

Sign up for a pay-as-you-go account, and confirm your email if asked. No card is needed. Self-serve accounts are for businesses and professionals based in the United States, aged 18 or older. If a teammate invited you to their workspace, accept the invitation.

2 · open your workspace

If you signed up, Perfloop created your workspace and made you its Admin. If you accepted a teammate's invitation, you joined their workspace instead. Perfloop then opens Start, which lists the setup steps that remain. Only an Admin can take step 3; if you are not one, ask your workspace's Admin to take it.

3 · connect a code host and choose repos

Before you connect, read Perfloop security: it lists what Perfloop reads, what it keeps, and what it cannot do. For GitHub, in Setup select Install Perfloop GitHub App. On GitHub, choose Only select repositories and pick the repos Perfloop may read. Back in Setup, select the repos for Perfloop to work on, then Save selection. Perfloop can see only the repos you pick on GitHub. Of those, it works only on the repos you save in Setup. Connect GitHub lists the access the App asks for.

For GitLab.com or a self-managed GitLab server, an Admin uses the GitLab tab in Setup. Enter the token of a GitLab bot account you create for Perfloop, then select List projects. Tick the projects Perfloop may use, then select Connect. See Connect GitLab for the access to give, how to connect a private server and how to revoke access. Enter credentials only in the app, never in chat or in a coding agent's tool call.

For GitHub Enterprise Server, see Connect GitHub Enterprise Server.

Setup, after the App is installed: choose repos, then Save selection.

Paid work draws on Usage, your workspace's prepaid balance. In a workspace you created by signing up, connecting your first code host adds a $100.00 free budget. This applies only if that code-host account has not received one before. Start shows one of these messages:

Your free budget of $100.00 was added to your Usage: the $100.00 is in your Usage balance, ready for paid work.
Your free budget is pending: the budget is recorded but not yet added to your Usage. Check its status on the Usage page.
No free budget for this account: the code-host account you connected first got a free budget before, so it cannot get another.

If your Usage balance is zero, paid work starts only after an Admin buys Usage on the Usage page. Buying needs no saved card.

If your Usage balance is above zero, saving your first selection starts one system model build on one of the repos you selected. The Model page shows which repo it is. Either free or purchased Usage can pay for it. Your other selected repos stay connected. Saving your selection again does not start another build. If the build cannot start, Setup keeps your selection and shows the reason and what to do next.

If the build stops early, the Model page shows the part of the repo it covered. To start another system model build, for example on one of your other repos, select Build this repo on the Model page. After step 4, your coding agent can also start one with buildModel. A build is paid work.

The build adds Cases to the Cases page. Each Case starts from a hypothesis: a possible problem worth testing.

what to expect

Many changes Perfloop tries are not proven. That is expected, and the failed tries stay on record in the Case. In an invited workspace, start with one Case before you turn on automatic work.

4 · connect your coding agent

Add the Perfloop MCP server to your coding agent and sign in with your Perfloop account. The steps for each agent are on The MCP server, and in Setup under Coding agents.

Setup, Coding agents: connect to https://app.perfloop.ai/mcp and follow the steps for your agent.

5 · start the first work

In a workspace created at signup, each repo's Case work control starts at Keep working: as the first model build finds Cases, Perfloop works ready Cases, one at a time, while Usage lasts. In an invited workspace it starts at Wait, and Perfloop picks no Case on its own. Either way, you can start work yourself:

Hand Perfloop a branch. Ask your agent to submit it. The agent calls submitDiff, then reads the findings with diff. A finding is a hypothesis Perfloop has not yet proven. Ask the agent to prove the one you want; it calls workCase.
Start a Case. Open Cases, open a Case in state Proposed, and select Work this case. When Perfloop starts work on it, the Case changes to Open. Your coding agent can start a Proposed Case too: it calls workCase with the Case's caseID, or with a hypothesisID. A Case found only in a branch or pull request also needs that diff, as above.

The header of a Proposed Case: Work this case starts Perfloop's work on it.

Each is paid work and draws on Usage. For Perfloop to pick and work Cases itself, an Admin sets the repo's Case work to Keep working and selects Save. Autonomy and limits explains each control.

New work needs a positive Usage balance. Work already in progress can cost more than the balance left. Unpaid Usage carries into the next Usage period. New funds first cover that shortfall.

6 · read the results

A Case page shows its state and the evidence behind it. What was wrong starts with a short summary when one exists; The full reasoning shows the rest. Verified means a change passed its checks, every claim held, and the verifier found nothing. Case states explains every state and what to do next.

A verified change can become a pull request, or only an issue when an issue is the better contribution, such as a finding the maintainers should fix themselves. For a newly connected repo, the Pull requests control starts at Ask. With Ask, each proven proposal waits in Inbox: select Allow & open PR (or Allow & open issue) or Reject. To let Perfloop open future proven pull requests without asking, an Admin can change the repo's Pull requests control to Open in Setup. The next automatic Case can start after you merge or close the pull request. You review and merge a pull request as usual; an issue has nothing to merge. Perfloop cannot approve, merge, or deploy.

Inbox, with Pull requests set to Ask: a proven change waits for Allow & open PR, or Reject.

Your agent reads the same results with cases, and a submitted change's findings with diff.

Get help

In the app, select Feedback in the side rail (in the menu on a phone), or write to hello@perfloop.ai. Both reach the Perfloop team.

Also in this section: Performance, Bugs, Security, The loop, Case states, Pull requests, Steering and learning, Initiatives, Autonomy and limits, Members, The MCP server, and Events.