Skip to content
Getting started

Codexe glossary

Short definitions of the terms used across Codexe and its docs, including Ready, verification, Compile, Auto Repair, tokens, credit restoration and web search.

Updated

On this page
  1. Ready
  2. Verification
  3. Compile
  4. Auto Repair
  5. Not verified
  6. Needs a fix
  7. Tokens (credits)
  8. Free daily refill
  9. Credit restoration
  10. Token pack
  11. Web search
  12. Reasoning effort
  13. Project knowledge

The words Codexe uses, in one or two sentences each. New to Codexe? Start with What is Codexe?. Every term links to the page that explains it in full.

#Ready

A project is Ready when its current files have passed Codexe's own check: a successful build with a valid JAR for plugins and mods, or a clean load on a real test server for datapacks and Skript. For Discord bots, websites and Blockbench models there is nothing to build, so Ready means the generation finished. See The project lifecycle.

#Verification

Verification is the check Codexe runs before calling a buildable project Ready: it builds or test-loads the files and, if that fails, repairs them and tries again. It happens automatically after generation and after chat changes, and it doesn't use your tokens. See Verifying and repairing.

#Compile

Compile runs a real, fresh build of a project's current files and shows the log, the errors and the resulting JAR. It is free and available for Java plugins and mods. See Compile.

#Auto Repair

Auto Repair is Codexe fixing build or load errors itself, using the exact compiler or loader errors. It runs during verification, and again when you press Let Codexe try again or Fix with AI on files it delivered; those repairs are free. See Auto Repair.

#Not verified

Not verified ("Generated, but not compiled" or "not test-loaded") means Codexe couldn't run the check, for example because the build service was busy or a Skript add-on isn't on the test server. The project isn't known to be broken; it just hasn't been checked. See Not verified.

#Needs a fix

Needs a fix means Codexe tried several repairs and the build still fails. The files are all there, and you can let Codexe try again for free, describe the problem in the chat or edit the files. See Project failed or needs a fix.

#Tokens (credits)

Tokens are the unit Codexe measures AI usage in; some dashboard labels call them credits, and it is the same balance. Generating and chatting use tokens; Compile, downloads and Codexe's own repairs don't. See Credits and tokens.

#Free daily refill

On the Free plan your balance is topped back up to 50,000 tokens once 24 hours have passed since the last top-up, the next time you open Codexe. See The free daily allowance.

#Credit restoration

Credit restoration gives back the tokens of a project's first generation automatically when it ends without anything usable because of a problem on Codexe's side. See Credit restoration.

#Token pack

A token pack is a one-time purchase that adds tokens to your balance, on any plan including Free. See Token packs.

Web search lets the AI look things up online while it works. It is available on Business and Enterprise, for GPT-6 and GPT-5.5 Pro models, and each completed search adds 25,000 tokens. See Web search.

#Reasoning effort

Reasoning effort is how much the model thinks before answering; choosing it is a Pro feature. See Models and reasoning effort.

#Project knowledge

Project knowledge is a set of extra instructions the AI reads on every request in a project, up to 5,000 characters, on Pro and above. See Project settings.

Codexe glossary | Codexe Docs