# Perfloop docs.

Guides for Perfloop, and the explanation they assume. The connect guides are written for the engineer doing the setup and for the security reviewer who checks the access it asks for. The work pages are for the engineer who runs Perfloop on a repository and reads its results.

Updated 22 September 2026.

## [How it works](https://perfloop.ai/docs/how-it-works)

Start here. It explains the model Perfloop builds of your software, the patterns it hunts on that model, the harness that proves a change, and the direction that stays with you. Its links open one merged case end to end.

## [Connect your systems](https://perfloop.ai/docs/connect)

One guide per telemetry source and code host. Each guide lists the access to grant and the setup steps, then the data Perfloop reads and stores.

- **Telemetry sources.** [Axiom](https://perfloop.ai/docs/connect/axiom), [Prometheus](https://perfloop.ai/docs/connect/prometheus), [VictoriaMetrics](https://perfloop.ai/docs/connect/victoriametrics), [Pyroscope](https://perfloop.ai/docs/connect/pyroscope), [Loki](https://perfloop.ai/docs/connect/loki), [Google Cloud Profiler](https://perfloop.ai/docs/connect/gcp), [Datadog](https://perfloop.ai/docs/connect/datadog), [Polar Signals](https://perfloop.ai/docs/connect/polar-signals), [Grafana](https://perfloop.ai/docs/connect/grafana), and [Grafana Cloud](https://perfloop.ai/docs/connect/grafana-cloud).
- **Code hosts.** [GitHub](https://perfloop.ai/docs/connect/github).

## [Work with Perfloop](https://perfloop.ai/docs/work)

These pages assume [How it works](https://perfloop.ai/docs/how-it-works). They cover how the loop runs on a repository, what each case state means, how to steer the work and what Perfloop learns per repository from the way you steer it, how an Initiative gives it a direction, what Perfloop may start on its own, and how a coding agent works with it over MCP.

- **[The loop](https://perfloop.ai/docs/work).** The reference for its objects and results: hypothesis, case, candidate, claim, checks, verdict, and the production check.
- **[Case states](https://perfloop.ai/docs/work/states).** What each state means, and what happens when a case pauses, stops, or repairs: budget, time, replacement, conflicts.
- **[Steering and learning](https://perfloop.ai/docs/work/steering).** Feedback, scope, closing with a reason, and the lessons Perfloop keeps per repository from each.
- **[Initiatives](https://perfloop.ai/docs/work/initiatives).** One outcome over part of your system, the research on it, and what its page shows.
- **[Autonomy and limits](https://perfloop.ai/docs/work/autonomy).** The four controls per repository, research, Usage, and the Case limit.
- **[The MCP server](https://perfloop.ai/docs/work/mcp).** Login, connecting a coding agent, and every tool, from the server's own catalog.

Questions: [hello@perfloop.ai](mailto:hello@perfloop.ai?subject=Perfloop%20docs)