Convex Domains
ConvexOfficialPublished by Convex
- Skill
- Workflow
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The convex-domains skill provides a structured procedure for mapping a custom domain to a Convex application. It guides users through identifying the correct target URL, configuring necessary DNS records (CNAME and TXT verification) at their registrar, attaching the domain to the Convex platform, and updating authentication settings to ensure the app remains functional under the new domain.
What it does
- Identifies the correct target hosting or HTTP action URL for the Convex deployment.
- Offers automated DNS record creation using pre-authenticated CLI tools like AWS, Cloudflare, or Vercel.
- Provides manual instructions for DNS configuration if automated tools are unavailable or declined.
- Attaches the custom domain to the Convex app and verifies propagation using DNS lookup tools.
- Updates authentication origin variables to prevent login failures after the domain change.
- Verifies the final setup, including HTTPS serving and redirect configurations.
When to use it
- When you want to replace the default Convex domain with a custom domain you own.
- When you need to ensure that authentication flows remain secure and functional after a domain migration.
- When you require a step-by-step process to manage DNS records across various providers like Route53, Cloudflare, or Google Cloud DNS.
Advantages
- Reduces manual errors by providing specific, concrete DNS record values rather than placeholders.
- Maintains security by leveraging existing user-authenticated CLI tools instead of requesting credentials.
- Ensures critical post-migration steps like auth origin rebinding are not overlooked.
- Provides verification steps to confirm DNS propagation and HTTPS functionality.
Usage examples
- “Help me point my custom domain example.com to my Convex app.”
- The agent identifies the target URL, provides the specific CNAME and TXT records to add to your registrar, and outlines the steps to update your auth origin.
- “I want to use my Cloudflare-managed domain for my Convex project.”
- The agent detects your authenticated Cloudflare CLI, offers to automatically create the necessary DNS records, and guides you through the final domain attachment.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/convex/convex-domains/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip convex-domains.zip -d .agents/skills
Documentation by Convex
<!-- 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.
Files
- ATTRIBUTION.mdAdded by AutoGineer852 B
- LICENSELicence file added by AutoGineer10.7 KiB
- SKILL.md2.4 KiB
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Convex
- Publisher
- Convex (Official)
- Source
- convex/agent-skills · skills/convex-domains · commit f60629d
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Convex.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download convex-domains.zip