Working with the AI

After the first generation, the project chat is the main way to change a project.

#Follow-ups edit, they don't regenerate

When you ask for a change ("make the cooldown configurable", "add a /delhome command"), the AI edits the files that need to change and leaves the rest alone. It works from the project's current files, including the edits you made yourself in the editor.

For buildable projects, Codexe verifies the result again after a chat change, exactly as it did for the first generation (building, repairing if needed).

#What follow-ups cost

Every chat message is billed like a generation, by what the model reads and writes. Because only the affected files are rewritten, a targeted follow-up usually costs much less than a new project. The cost of each message is shown in the chat.

#Asking for fixes

The most useful fix requests describe what happened, not only what you want:

• Good: "When a player without permission runs /home, nothing happens. They should get the no-permission message from config.yml."
• Less useful: "fix permissions".

If a build fails, use Fix with AI in the Compile result instead of copying errors by hand. See Auto Repair.

#Voice input

The chat has a microphone button that transcribes speech with your browser's speech recognition, in the language you choose from its menu.

#Suggestions

For your first few messages, the chat shows short next-step suggestions for your project type ("add a config file", "add tab completion"…). Clicking one only fills the message box, so you can edit it before sending.

#When the chat is paused

The chat is paused while Codexe is verifying or repairing the project, so a change can't collide with a repair in progress. It also refuses a new message while another of your projects is generating.

#Rate your result

After a generation you can give a thumbs up or down. It helps us see which kinds of projects need work.