Skip to content
Using Codexe

Working with the AI

How the project chat changes existing files, what follow-ups cost, voice input, next-step suggestions and how to ask for fixes that work.

Updated

On this page
  1. Follow-ups edit, they don't regenerate
  2. Code in the chat
  3. What follow-ups cost
  4. Asking for fixes
  5. Voice input
  6. Images and files in the chat
  7. Suggestions
  8. When the chat is paused
  9. Rate your result

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).

While it verifies, the progress box in the chat says what it is doing (compiling, starting a test server, the test players at work) and the buttons that need the finished project, such as Compile, Try it now and Preview, show that they are loading. The files arrive with the reply when the check is over, usually within one to three minutes.

#Code in the chat

Without a plan the assistant changes your code but does not print it in the chat: it describes what it changed in words, and it will not put source code in configuration files, logs or scripts. Ask it for any change; to read the full code, see the plans or download the project.

#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 and the Create page have a microphone button, on every plan and in every current browser. Pick a language (or let Codexe detect it), speak, and press the square to stop: what you said appears in the message box, where you can correct it before sending. A recording can last up to 2 minutes. Voice input is free on every plan, up to a daily allowance of transcribed audio (UTC day):

PlanVoice input per day
Free30 min/day
Pro2 h/day
Business2 h/day
Enterprise2 h/day

When today's allowance is used, the microphone says so and you can keep typing; it resets at midnight UTC.

#Images and files in the chat

Attach screenshots, mock-ups or code to a chat message the same way as on the Create page, within the same per-plan limits.

#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.

Working with the AI | Codexe Docs