convex-domains
get-convex/agent-skills
Point your own domain at a Convex app with DNS records, custom-domain attachment, and auth-origin rebinding.
What is convex-domains?
This skill guides you through configuring a custom domain you own to serve a Convex app. It handles DNS record creation (via authenticated CLI or manual instructions), custom-domain attachment in Convex, and re-binding auth origins if your app uses authentication.
- Identify the target hosting URL (Convex static hosting or HTTP actions deployment)
- Detect and offer to auto-create DNS records via authenticated CLI (Cloudflare, Route53, Google Cloud DNS, DigitalOcean, Vercel)
- Provide exact DNS record values (CNAME/A and TXT verification) for manual registrar entry if no CLI is available
- Attach the custom domain to your Convex app and wait for DNS verification
- Rebind auth origins (SITE_URL, RP_ID, ORIGIN) if your app uses authentication, then re-deploy
- Verify HTTPS serving and apex-to-www redirects
How to install convex-domains
npx skills add https://github.com/get-convex/agent-skills --skill convex-domains- An existing domain registered at any provider (Cloudflare, Route53, Google Cloud DNS, DigitalOcean, Vercel, or other)
- Access to your registrar's DNS settings (either via authenticated CLI on your machine or direct dashboard access)
- A published Convex app (static site or HTTP actions deployment)
How to use convex-domains
- 1.Provide your domain name and confirm which Convex app/deployment it should point to
- 2.If you have an authenticated CLI (flarectl, aws, gcloud, doctl, vercel), the skill will detect it and offer to create DNS records automatically—review and confirm the commands before they run
- 3.If no CLI is available or you prefer manual entry, copy the exact CNAME (or A/ALIAS at apex) and TXT verification record values and add them at your registrar
- 4.Wait for DNS propagation (typically minutes to hours) and verify records with dig +short
- 5.If your app uses authentication (passkeys/OAuth), update auth-origin environment variables (SITE_URL, RP_ID, ORIGIN) to your new domain and re-deploy
- 6.Test that your domain serves the app over HTTPS and any apex redirects work correctly
Use cases
- Move a production app from *.convex.app to your branded domain without downtime
- Set up OAuth or passkey authentication with a custom domain as the auth origin
- Migrate an existing domain to point at a new Convex deployment
- Configure DNS records automatically if you have a CLI authenticated with your registrar
- Manually add DNS records at your registrar when no CLI is available
- Developers deploying Convex apps to production
- Teams managing custom domains across multiple registrars
- Apps using Convex authentication that need a branded domain
- DevOps engineers automating domain configuration
convex-domains FAQ
No. The skill only uses CLIs already authenticated on your machine (like flarectl or aws). Credentials stay in the tool and are never shared or echoed.
The skill will provide the exact DNS record values (host and value strings) for you to add manually at your registrar's dashboard.
Usually minutes to hours, depending on your registrar and TTL settings. You can verify with dig +short to check if records have landed.
If your app uses authentication (passkeys, OAuth), the auth origin must match your domain. Changing the domain without updating auth-origin environment variables will break sign-in.
Yes—if no authenticated CLI is available, the skill provides exact record values for manual entry at any registrar's dashboard.
Full instructions (SKILL.md)
Source of truth, from get-convex/agent-skills.
name: convex-domains description: "Point a domain you already own at your Convex app (DNS records, custom-domain attach, auth-origin rebind)."
<!-- GENERATED from convex-agents content/capabilities/domains.json — do not edit by hand. -->Set up a custom domain with your own provider
Walk the user's own registrar through pointing their domain at the Convex app: identify the target (hosting or deployment URL), create the DNS records, attach the custom domain, and rebind the auth origin if the app uses auth.
Workflow
- Identify the target: the published site host (for
*.convex.appstatic hosting) or the deployment's HTTP actions URL. - Detect an ALREADY-AUTHENTICATED DNS CLI for the user's provider and OFFER to create the records automatically: Cloudflare →
flarectl dns create(note:wrangleritself doesn't manage DNS records) or the CF API via their token env; Route53 →aws route53 change-resource-record-sets; Google Cloud DNS →gcloud dns record-sets create; DigitalOcean →doctl compute domain records create; Vercel DNS →vercel dns add. Check auth read-only first (flarectl user info/aws sts get-caller-identity/doctl account get); show the exact commands and get a yes before running. - If no authed CLI (or the user declines), tell the user exactly which records to create at THEIR registrar: the CNAME (or A/ALIAS at the apex) plus the TXT verification record — with concrete host/value strings, not placeholders.
- Attach the domain as a Convex custom domain (dashboard or CLI) and wait for verification; note DNS propagation can take minutes to hours. Verify records landed with
dig +short. - If the app uses auth (passkeys/OAuth), rebind the auth origin (SITE_URL / RP_ID / ORIGIN env vars) to the new domain and re-deploy/re-publish.
- Verify: the domain serves the app over HTTPS, including the apex → www redirect if configured.
Rules
- Never ask for or handle registrar credentials. A CLI already authenticated on the user's machine is fine — the credential stays in the tool; never install a CLI or run its login/auth flow for this, and never echo tokens.
- DNS changes on a live domain are user-visible: show the exact commands and confirm before running them; verify afterwards with dig.
- Always include the TXT verification record, not just the CNAME.
- Rebinding the domain changes the auth origin — re-publish after, or sign-in breaks.
Related skills
More from get-convex/agent-skills and the wider catalog.
convex-env
Set and manage Convex deployment environment variables and secrets securely.
convex-expert
Convex backend specialist for queries, mutations, actions, schemas, and real-time functions.
convex-explain-app
Analyze your Convex app's data model, functions, auth, and request flows without modifying it.
convex-improve-convex-plugin
Send your coding session to Convex for AI-powered system improvements and quickstart refinement.
convex-insights
Query Convex app logs and health in natural language with evidence-backed answers and dashboard links.
convex-launch-readiness
Unified backend readiness score with prioritized fix plan—run all Convex audits, dedupe findings, and dispatch fixes.