When the build finishes you land on the draft review. It shows everything the plugin will be before anything is saved:
- The validator's verdict. Every draft goes through the platform validator, the same one that checks uploaded plugins. It catches forbidden imports, missing capabilities and code that does not parse. Each blocking error and warning is listed with its code.
- A sandbox test. The draft is started in the platform sandbox and its handlers are called, so you can see it loads and runs without crashing. When the test cannot run, the page says so and only the static checks apply.
- The slash commands with their options, exactly as Discord will register them when a server installs the plugin.
- The plugin's pages, rendered by the platform's own engine with sample data. A designed site can be checked page by page at desktop and phone width.
- The source: the full
manifest.jsonand__main__.py.
Fix it with AI
If the validator flags anything, Fix these with AI runs a paid pass that fixes exactly those findings. You do not write a prompt, and you do not have to save a broken draft first. You watch the fix on the same live page and come back to the review for another look.
What to do with the draft
- Run it on my server saves the plugin and installs it privately on one of your servers in one click. See Test it on your server.
- Create plugin from this draft saves it as a new plugin with a draft version, v0.1.0. From the plugin's Versions tab you can browse the source, download the zip, upload a fixed zip as a new version and submit it for review. Nothing is published until you submit it.
- Download files gives you the plugin as a zip to finish by hand.
- Regenerate with different prompt takes you back to the composer to try again.
Until you save it, the draft also waits under Saved builds.