Credentials. The agent needs your DNS and email provider credentials, which golive reads in-process and stores in a plaintext file at mode 0600 outside your repo.
Who it is forA founder whose app already runs on a test URL and who needs a real domain and email that the user's own DNS provider controls.
The problemDNS and email settings are easy to get wrong by hand, and a DNS change can affect other services on the domain.
The outcomeThe domain resolves to the live app, transactional email is sent through Resend, and the agent reports what was changed and what still needs a human.
What you need first
- Node.js 20+, npm/npx and Git installed
- A coding agent that can load skills and run commands (README checks Codex and Claude Code)
- Accounts you own with the providers you plan to use, such as Vercel, Supabase, Netlify, Neon, Porkbun, GoDaddy, Resend or Stripe
- Logins for those providers in a terminal you control, since the agent relies on them
Steps
- Confirm the domain is registered with Porkbun or GoDaddy, the two DNS providers this project lists for custom-domain DNS.
- Ask the agent in chat to add the domain and Resend email, and review the DNS changes in the plan.
- Approve the DNS writes only after the plan names the zone and records you expect, since DNS writes need explicit confirmation.
- Send a test transactional email from the app and check that it arrives.
- Ask the agent to report anything golive could not verify, so you can finish those steps yourself.
Prompt for your agent
Use the golive skill in the repo <repo-path> to plan a custom domain DNS change through Porkbun or GoDaddy and transactional email through Resend. Show the zone and each record in the plan before any write, then report what was applied and what remains manual.
Caveat. The README names Porkbun, GoDaddy and Resend as covered in disposable live tests, and the broader roadmap is direction, not a claim that everything is built.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page