Loading...

The Report at the End of a Build Run

How a Build run closes: which of your requirements are in, what is not built yet, and the security check on plugins and mods.

It is written after the files, not before

When a run in Build mode has written files, the reply ends with a short report. It is built from what actually happened in that run — which files were written, and a reading of the code in them — not from the plan the AI made before it started. That is the point of it: a plan can promise a feature that never reached a file, and this cannot.

Making the report costs nothing. No AI is asked anything; it is a check over your files. Chat mode writes no files, so it has no report.

When your message was a list

If your message asked for two or more separate things — bullet points, numbered lines, or sentences such as "players must…" and "only the owner can…" — each one becomes a numbered requirement: R1, R2 and so on, up to 24. The report then goes through them one at a time.

Under Verification: there is one line per requirement, saying where it lives:

• R2 lock a chest → LockListener — found in the code — the check looked for it in the files and found it
• R4 wording of the messages → messages.yml — planned and written, but not something the check can test by reading code
• R6 protect item frames → nothing — NOT BUILT

When something is missing, the closing sentence opens with the count — "5 of your 7 requirements are in; the ones below are not built yet." — and words such as complete or finished are taken out of it, so a run never signs off as done over a feature that is not there.

"Not built yet", and how to get the rest

Under the list, Not built yet: names each missing requirement with its reason:

• left for a later run — the plan put it off on purpose
• no file in this run implements it — nothing in the plan covered it
• its file was not written in this run — the file it needed failed, or the run ran out of time before reaching it
• on plugin and Fabric mod projects, a short line saying what the check could not find in the code

The list ends with "Send continue and I'll build these next." Sending continue starts a new run for exactly those lines; you do not have to describe the project again. It is billed like any run, and the files already written are not written again.

"Problems found in the generated code"

A Build run that writes Java can end with Problems found in the generated code: as well, whether or not your message was a list. These are mistakes a compiler is happy with:

• a value the code stores that nothing ever reads back, so the feature depending on it does nothing
• a %placeholder% wrapped in % twice, so players see the raw %placeholder% instead of a name or a number

Only the files written in that run are checked, so an old file is never blamed for a new request.

The Security check, on plugins and mods

On a plugin or mod project, every Java or Kotlin file the run wrote is also read against 27 fixed safety rules — running an operating-system command built from player text, opening a network port with no secret, making a player an operator from code, gluing chat text into an SQL query, a password or token written into the code, stopping the whole server process, turning off HTTPS checks, and the rest. The line reads one of two ways:

• Security check: N security holes to fix before this goes on a server:
• Security check: no security holes found. N things to review: — riskier patterns that also have honest uses, each marked Heads-up —

Every item names the file and the line, what is wrong and the fix. Up to ten are listed, then …and N more. A clean scan adds no line at all. Holes that are safe to rewrite automatically have already gone through the repair round after the build check, so what you are reading is what is left.

Reading it does not fix it

Nothing on either list changes until you ask. Say what you want in Build mode — "fix the security holes from the security check", or "build R4 and R6" — and the AI works from the same report. That is a normal run and costs credits like any other. A hole in a jar you have already put on a server stays there until you upload a new one.

Where to next

• Before the build starts: Plans & Questions — The plan the report is checked against.
• If the jar is missing: Cloud Build — The build check line that sits in the same reply.
• When the build failed: Auto-Fix — The repair rounds, and when they are billed.
• If the run stopped early: When a Generation Is Cut Off — What "send continue" costs.

19 of 37 in Code Studio (IDE) · Last checked 12 September 2026 · Previous: Watching the AI Work