Skip to main content
In repair mode, a production error that crosses its threshold gets a repair run. A coding agent works on the code of the deploy that failed, and floo proposes its fix as a draft pull request. You review the change in floo and approve its preview; floo checks the fix there, and you merge it from floo when it passes. Repair mode is off until you turn it on, and it is available only for apps in a floo-hosted GitHub repository. For any other repository, recommend mode runs the same agent and shows you its fix to apply yourself.

Turn it on

On the dashboard, open App → Alerts → Error routing → Edit, set Mode to Repair, and save. Over the HTTP API:
The error threshold and cooldown from Agent webhooks decide when an error gets a run. A webhook URL is optional in repair mode. When one is set, floo still POSTs every event to it.

What a run does

  1. Fix. A coding agent gets the failing deploy’s source and the event’s context: the error, its stack trace, and recent logs. It can read and edit files. It cannot run commands or reach the network.
  2. Draft PR. If the agent produces a fix and a way to reproduce the error, floo pushes it to a floo/repair-… branch and opens a draft pull request explaining the change.
  3. Review and approve. The fix’s preview does not build on its own. Under Alerts → Recent errors, choose Review changes on the event, read the diff, and choose Approve preview. The approval covers the commit you reviewed; a later push needs its own review.
  4. Verify. floo deploys that commit to a preview, replays the reproduction against it, and reads its logs. If the error does not come back, the fix is marked verified. If it does, floo closes the pull request.
  5. Merge. You decide. Choose Review changes again and then Merge fix. floo merges only the commit it verified, and merging deploys the fix like any other push to your default branch: to dev.
  6. Release. If your app has a prod environment, pushes never change it. Once the fix is live in dev, release it with floo promote --app <name>, as you would any other change.
From the CLI, the same steps are:
floo events diff prints the commit to pass to --commit. A preview that requires sign-in cannot be checked, so its run ends not_verified. The reproduction is never run against your live app.

Recommend mode

Recommend mode runs the same agent on the same errors, but stops at its fix. floo makes no branch or pull request and builds no preview, so it works with any repository, including one you connected yourself. Set Mode to Recommend, or send {"mode": "recommend"} to the same endpoint. When a run finds a fix, it ends recommended. Choose Review changes on the event, or run floo events diff EVENT_ID, to see:
  • what the agent found, in its own words;
  • its change, file by file;
  • the requests that reproduce the error. Before the fix they log it; after it, they shouldn’t.
floo hasn’t applied or tested a recommendation. Apply it yourself, or hand it to your own agent, then check it with those requests. A run costs the same as a repair run, minus the preview.

Start a run by hand

Events from before repair or recommend mode was on, or events the trigger skipped, can still get a run. Choose Start repair (or Recommend a fix) on the event under Alerts → Recent errors, or run:
An event gets one run. An app can have at most three runs queued or running at once.

Follow a run

The dashboard shows each event’s run under Alerts → Recent errors, with its preview link and, while a fix waits on you, Review changes. From the CLI:

What it costs

A run bills your organization for what it uses:
  • Model tokens, at the Claude Opus 5.5 rates on the pricing page. A run stops at 10 million tokens.
  • Build minutes for the run’s build, at your build rate.
  • The preview, like any other preview, once you approve it.
A run never takes longer than 60 minutes of agent work.

What it never does

  • Merge a fix or push to your default branch on its own. Only your Merge fix does that.
  • Merge a commit it did not verify.
  • Deploy a fix’s preview before you approve it.
  • Give the agent your app’s secrets, a shell, or network access.

Agent webhooks

Thresholds, cooldowns, and the event payload that starts a run.

Preview environments

How a PR’s preview is approved, deployed, and torn down.