The Codexe project workflow

Every Codexe project follows the same path regardless of target: describe it, generate it, read it, refine it, build it, then keep it private or publish it. A project is a persistent workspace, not a one-shot answer - you can come back to it later and keep working.

The first generation creates the whole project at once: source files, build descriptor, manifest and configuration. Files stream in as they are produced, so you can start reading before the run finishes.

Generation status is tracked on the project. A project is GENERATING while the model is working and READY once the files are complete. Only ready projects can be published to the gallery.

The project chat is the main way to change a generated project. Ask for a specific change - “add a per-world toggle to the config”, “the cooldown should be configurable”, “this throws on 1.20, fix the API call” - and Codexe edits the existing files in place instead of regenerating from scratch.

The workspace includes a full code editor. You can edit any file directly, and your edits become part of the project - the next chat request works against what is actually in the tree, including your manual changes.

For Java targets - Spigot, Paper, Folia, BungeeCord/Velocity, Forge and Fabric - Codexe can compile the project on the platform and produce the artifact. That matters because it is the difference between code that looks right and code that actually builds: compile errors surface inside the workspace, and you can ask the assistant to fix them.

Targets that need no compilation - datapacks, Skript, static sites, Discord bots - are ready to use as soon as generation finishes.

You can download the complete project as a ZIP at any time, or push it to GitHub. Downloads include the full source tree, not just the built artifact.

Codexe can also start from code you already have. Uploading a ZIP of an existing project imports the file tree and detects the project type from its structure - for example a plugin.yml marks it as a Bukkit-family plugin, fabric.mod.json as a Fabric mod - so the assistant applies the right knowledge when you ask for changes.

Projects are private by default. When you are ready to show one off you can make it unlisted (link-only) or public (listed in the gallery). See sharing and profiles for what each level exposes.