The project lifecycle
What each project status means (Generating, Checking, Building, Fixing, Ready, Not verified, Needs a fix, Failed) and why Codexe verifies before calling a project Ready.
Updated
On this page
A project is Ready when its current files have passed Codexe's own build (plugins and mods) or load test (datapacks and Skript); for Discord bots, websites and Blockbench models, Ready means the generation finished. A project always has exactly one status. This page explains each one, what Codexe is doing, and what you can do.
#The short version
- Generatingthe AI writes the files
- Verifyingbuild or test-load
- Repairingfix errors, rebuild
- Readycurrent files passed
For buildable projects (Spigot/Paper/Folia/BungeeCord plugins, Fabric/Forge mods, datapacks and Skript), Ready means the files you're looking at passed Codexe's own build or load test. For other types (Discord bots, websites, Blockbench models) there's nothing to compile, so Ready means the generation finished.
#Generating
The AI is writing the project. Files appear as they're produced. If the reply is cut off in the middle of a file, or a file the AI planned never arrives, Codexe continues the generation internally before moving on. You don't pay for this continuation.
#Verifying and repairing
While Codexe checks a buildable project, a banner shows the current step:
| Banner | What is happening |
|---|---|
| Checking project… | Confirming the files match the platform you asked for |
| Writing remaining files… | Completing files the first reply left unfinished |
| Building… | Compiling (plugins, mods) or loading on a test server (datapacks, Skript) |
| Fixing an issue… | The build failed; the AI is repairing the reported errors |
| Verifying… | Building again after a fix |
| Finalizing… | Saving the verified result |
Repairs use the exact compiler errors and the real library signatures from the build, not guesses. Fixing doesn't use your credits. See Auto Repair.
While a project is being verified, the chat and Compile are paused for that project, so a change can't collide with a repair in progress. They come back as soon as verification ends.
#Ready
The current files passed. For plugins and mods that means a successful build that produced a valid JAR with the right descriptor (plugin.yml, fabric.mod.json, mods.toml…). For datapacks and Skript it means the files loaded on a real test server without errors.
Ready describes the exact files that were verified. If you edit a file yourself afterwards, those edits haven't been built yet. Press Compile to check them. Changes made through the chat are verified again automatically.
#Not verified ("Generated, but not compiled")
Sometimes Codexe can't run the check: the build service was busy, a dependency repository didn't answer, or a Skript script uses an add-on the test server doesn't have. The project isn't known to be broken; it just hasn't been checked. Everything is available to you, and you can press Compile for a real answer. Codexe also retries these projects automatically for a while.
#Needs a fix ("Codexe couldn't finish verifying this project automatically")
Codexe tried several repairs and the build still fails. All the files are there and you can keep editing them. You can:
- press Let Codexe try again (free), which runs a fresh round of repairs without using credits (once per project per day, up to three projects a day), or
- describe the problem in the chat, or fix it yourself in the editor.
See Project failed or needs a fix.
#Failed
The first generation produced nothing usable: no files at all, a provider error, or a project on the wrong platform that couldn't be regenerated. When that happens to a project's first request, the tokens it used are restored automatically and the page shows a Try again button. See Credit restoration.