What problem does it solve?
Pointing a domain you own at a Convex app requires coordinating DNS records at your registrar, attaching the custom domain to Convex, and rebinding auth origins — a multi-step process where a missed TXT record or stale auth origin breaks the site or sign-in.
Core Features & Use Cases
- DNS Record Automation: Detects already-authenticated provider CLIs (flarectl, aws, gcloud, doctl, vercel) and offers to create the CNAME/A and TXT verification records, or prints exact record values for manual entry.
- Custom Domain Attachment: Attaches the domain as a Convex custom domain, waits for verification, and confirms propagation with dig.
- Auth Origin Rebinding: Updates SITE_URL, RP_ID, and ORIGIN environment variables and re-publishes so passkey/OAuth sign-in keeps working on the new domain.
- Use Case: You deployed a Convex app at a *.convex.app host and want it served at app.example.com — the skill walks your registrar through the records, attaches the domain, and rebinds auth.
Quick Start
Point my domain app.example.com at my Convex deployment and update the auth origin so sign-in still works.