Auto Repair
How Codexe repairs build errors during delivery, the free "try again" and "Fix with AI" repairs, and when a fix goes through the chat instead.
Updated
On this page
Auto Repair is Codexe fixing build or load errors itself, using the exact errors from the build. It happens in two situations, and knowing which is which tells you whether a fix is free.
#1. Internal delivery repair (free)
While Codexe verifies a buildable project, a failed build doesn't reach you as a broken project (every step, in order). Codexe:
- reads the exact compiler or load errors,
- looks up the real signatures of the library classes involved, from the same JARs the build used, so the fix matches the actual API version,
- asks a repair model to change only what is needed,
- builds again.
It keeps going for several rounds while the number of errors keeps dropping, and if it gets stuck it makes one more attempt with a stronger model. You see this as Fixing an issue… and Verifying… on the project.
This work is Codexe's cost, not yours. It doesn't use your tokens or count as a prompt.
#2. Repairs you start
| Where | Button | What it costs |
|---|---|---|
| Project that ended as "needs a fix" | Let Codexe try again (free) | Free |
| Failed Compile, files unchanged since delivery | Fix with AI | Free (same internal repair) |
| Failed Compile, files changed by you or by chat | Fix with AI | A normal chat message (tokens) |
| Anything else | Describe the problem in the chat | A normal chat message (tokens) |
The free "try again" is limited to once per project per day, and three projects per day per account.
Why the difference? If the files are exactly what Codexe delivered, the failure is Codexe's responsibility. Once the project has changed, the fix is new work on your version, like any other request.
#When repair stops
Codexe stops repairing when the errors stop decreasing, the same error keeps coming back, or a time or effort limit is reached. The project then shows Codexe couldn't finish verifying this project automatically. All the files are still there. See Project failed or needs a fix.
#What repair can't fix
- Behaviour. Repair fixes code that doesn't build. It can't know that a feature works differently from what you meant; tell the chat.
- Infrastructure problems. If the build couldn't run at all (a dependency repository timed out, the build service was busy), there's nothing to repair. The project is marked not verified instead and retried later.
- Unsupported Skript add-ons. If a script needs an add-on the test server doesn't have, Codexe reports it instead of rewriting your script.