ChatGPT Sites + Convex

Build the complete application, validate both halves, and publish it unless the user explicitly requests local-only work.

Choose the workflow

• Default: durable shared Site. When the user asks to publish, deploy, share, ship, or provide a URL without explicitly requesting a temporary preview, use Convex Cloud production and complete the Sites lifecycle through a confirmed live .chatgpt.site URL.
• Existing Site update. When the user asks to update, republish, or publish the latest version, preserve the existing Sites project_id, current access policy, and canonical current_live_url. Reuse the confirmed production Convex URL. Deploy Convex again only when backend code, schema, components, schedules, actions, or backend environment requirements changed; obtain fresh production consent immediately before that deployment. Always rebuild, scan, save, deploy, poll, call get_site, and run live QA for the new Sites version.
• Local-only development. Use accountless Agent Mode only when the user explicitly wants localhost development without publishing. It creates no shareable URL.
• Temporary preview. Use an isolated, expiring Convex Cloud dev deployment only when the user explicitly requests a temporary preview. Label it non-production and report its expiration.

Do not stop a publication workflow after local validation, cloud linking, Site registration, an access change, or environment configuration. Continue through the saved Sites version, deployment, nonempty get_site.current_live_url, and live QA unless a real authorization or platform blocker prevents progress.

Non-negotiable architecture