How publishing works.
Visual Truth edits locally. The source becomes durable code. Your existing hosting workflow publishes the website.
Publish a website edited with Visual Truth
This is the path most people need. Visual Truth does not replace Git, a production build, or your hosting provider.
- 1
Finish the visual edit
Check Desktop, iPad, and Phone. Confirm the selected element, layout, text, and spacing are exactly where you want them.
- 2
Choose Make It Code
Visual Truth writes a reviewable generated module containing the approved visual history. It does not deploy anything by itself.
- 3
Let Codex integrate it
Ask Codex to fold the generated values into the components and styles that own the page, then remove temporary runtime overrides.
- 4
Run the production checks
Build and test the project without the local editor. Review the finished site at the real production breakpoint sizes.
- 5
Publish with your host
Commit the approved source and use the same deployment workflow you already use—such as Netlify, Vercel, Cloudflare, or your existing website platform.
Do users publish Visual Truth?
No. Installing Visual Truth does not make you responsible for publishing or updating the plugin.
Only the plugin publisher prepares a signed release package and submits it through the OpenAI plugin portal. When a newer public version becomes available, users update the installed plugin from Codex.