An approval gate between agents and your cloud bill
It exists because coding agents build apps in minutes but still need a human login, a plan, and permission to push them live.

What it does
GoLive is an open-source skill for coding agents like Codex and Claude Code that handles the unglamorous work of taking an application live. It inspects your repository to detect what infrastructure the app needs—hosting, databases, domains, email, payments—then plans the exact provider changes, asks for your explicit approval, and applies them using your own account credentials. After deployment, it verifies what actually works, records what it created in an ownership document, and can later check for drift or tear everything down.
The interesting bit
The clever part is not the automation; it is the bureaucracy. GoLive forces the agent to show you the destination names, resource settings, and cost before touching anything, and it stores API keys in a local credentials file rather than dumping them into chat logs. It treats infrastructure as something an agent can orchestrate but never fully own.
Key highlights
- Supports Vercel and Netlify for hosting, Supabase and Neon for databases, with live-tested paths including DNS via Porkbun and GoDaddy, email via Resend, and Stripe test-mode payments.
- Runs entirely on your machine with no GoLive account, hosted backend, or product telemetry; credentials stay local and never pass through the agent’s chat context.
- Includes a
teardownpath that plans and requires approval before destroying resources, plus agolive statuscommand for read-only drift detection. - Offers a best-effort guided flow for providers outside the built-in adapters, though with less verification coverage.
- Currently at
0.1.0-alpha.3; the README is explicit that cross-pairings beyond the live-tested journeys have only mocked coverage.
Caveats
- Only a handful of provider pairings have been live-tested end-to-end; other combinations and application frameworks are currently unvalidated.
- The alpha requires you to handle initial provider signups, browser logins, and identity checks manually before the agent can proceed.
- Experimental adapters for Cloudflare DNS and Supabase Auth configuration exist but are not as thoroughly exercised as the core hosting and database paths.
Verdict
Worth a look if you are already using Claude Code or Codex and want an audit trail between your agent and your cloud providers. Skip it if you need broad provider support or a fully hands-off deployment today; this is still early alpha with a narrow, well-documented test matrix.
Frequently asked
- What is mikehasa/golive-skill?
- It exists because coding agents build apps in minutes but still need a human login, a plan, and permission to push them live.
- Is golive-skill open source?
- Yes — mikehasa/golive-skill is open source, released under the MIT license.
- What language is golive-skill written in?
- mikehasa/golive-skill is primarily written in TypeScript.
- How popular is golive-skill?
- mikehasa/golive-skill has 879 stars on GitHub.
- Where can I find golive-skill?
- mikehasa/golive-skill is on GitHub at https://github.com/mikehasa/golive-skill.