# Repair

> **Historical. This product is retired.** This page describes the earlier browser-testing product and is kept only as history. Its service, API, console and accounts are closed: do not run the install commands or call the endpoints shown here.

A repair prompt for whoever fixes it, and a re-check that proves the fix.

- **Outcome:** You can turn a Failed into a checked fix.
- **Does not do:** Vraelis writes the prompt and checks the fix. It never edits your code.

When a run fails, Vraelis writes a repair prompt: what should have happened, what happened instead, how to reproduce it, and the evidence. It is written so a person or a coding agent can act on it directly.

## The division of labor

Whoever fixes it diagnoses the cause and makes the change. Vraelis does not edit code. Once the fix is deployed, a re-check runs the same approved plan again as its own run, and an earlier record is never overwritten.

> **Where the prompt goes.** Back to whoever asked: in the answer an AI assistant gets over MCP, in the CLI's output (`--repair-prompt` prints only the prompt), in the API response, and on the run report. A re-check is started by a person, a CI job or an assistant. Nothing re-checks on its own.

> **Preserved history.** Every result is kept. A later Verified does not erase an earlier Failed.

---

Vraelis documentation, Earlier references. https://docs.vraelis.com/repair