A new open-source project on GitHub aims to close the gap between an app a coding agent can build in minutes and one that real people can use. GoLive, published under the repository golive-skill by developer mikehasa, is an Agent Skill paired with a zero-dependency Node.js command-line tool. It is designed to put an agent-built product online across hosting, database, domain, email and payments, using accounts the developer already owns. The project is in early alpha at version 0.1.0-alpha.8, and its repository page was published on 11 October 2026.
The gap between a built app and a live one
Coding agents have made it fast to produce working software. What they have not solved is everything that comes after: creating provider accounts, choosing hosting, provisioning a database, connecting a custom domain, configuring transactional email, wiring up payments and managing secrets. Each step usually means switching between dashboards and copying values by hand, and that is where launches often stall.
GoLive is built around that handoff. According to the GitHub repository, the skill detects what an app needs, plans the exact changes, waits for approval, applies them using the developer's own logins and then verifies what it can observe. It also records what it created, can re-check that record for drift on request and can remove those resources again.
How the workflow keeps you in control
The project's most emphasised principle is that nothing reaches a real account without an approved plan. The repository says apply refuses to run without the plan identifier and an explicit confirmation flag, and it re-checks the plan before writing. If a release or configuration changes after approval, the earlier sign-off no longer applies.
Riskier actions carry extra safeguards. DNS writes require their own confirmation, deletions need a separate flag, and live-mode steps such as live payments, production data or a real account require another. According to the source, that last requirement now also covers a project's first production deployment, because approving a plan alone used to be enough to write to production for the first time.
Credential handling is described in detail as well. Secret values are read only inside the running process and are never printed, passed as arguments or written to plans, state or reports. The repository is open about the fact that the local credentials file is plaintext, protected by file permissions at mode 0600 and kept outside the project, rather than stored in a system keychain.
The project also names a limit. The confirmation flags are arguments that the agent passes on the user's behalf, so an agent already logged in to a provider could make changes there without any GoLive plan. The repository separates what the code enforces from what is only an instruction the agent is asked to follow, a distinction readers evaluating the tool should keep in mind.
Rollback, teardown and what is left behind
Recovery is deliberately narrow. A failed check never triggers a rollback. Rollback is opt-in and limited to re-pointing production at an earlier deployment that GoLive itself recorded. Only Netlify supports this today. On Vercel, according to the repository, production must be corrected in the dashboard because the adapter cannot read what production is serving. Promotion and rollback are covered by mock tests but have not been validated live.
Teardown follows the same cautious logic. The repository says it removes only resources the tool can prove it created, re-reads the DNS zone and host project after deleting, and lists every leftover it cannot remove as a handoff. Examples include Supabase and Neon projects and the Resend sending domain. Removal also clears the baseline GoLive recorded for a resource, so a deliberate teardown is not later reported as drift.
What has been tested, and what has not
The project separates live evidence from code that is only mock-covered. Disposable live tests reportedly cover six journeys: hosting on Vercel and Netlify, databases on Supabase and Neon, custom-domain DNS with Porkbun and GoDaddy, transactional email through Resend, test-mode payments with Stripe, and Supabase authentication, plus the uninstall path. According to the repository, the test resources were deleted afterwards.
Several boundaries are stated plainly. Cross-pairings of providers have mock coverage rather than live proof. A new user's first-account setup and every application framework have not been validated. Cloudflare DNS is an experimental adapter, and the roadmap describes direction rather than finished capability.
- Hosting: Vercel and Netlify
- Database: Supabase and Neon
- Domain DNS: Porkbun and GoDaddy
- Email: Resend
- Payments in test mode: Stripe
- Authentication: Supabase
Installation and who it suits
Installation requires Node.js 20 or later, npm or npx, Git and a coding agent that can load skills and run commands. The repository says installation has been checked for Codex and Claude Code, and that other clients are unverified. The skill can be installed for all projects or for a single repository. It is also published to npm as golive@0.1.0-alpha.8 for offline installation, and it is listed on ClawHub for OpenClaw users, where it installs into a workspace's skills folder.
The installer does not connect accounts or deploy anything, so the first step carries little risk. Provider changes begin only after the agent presents a plan and the user approves it.
Outlook
GoLive targets developers who have built a product with an AI coding agent and want a controlled route to production without handing over unrestricted access. Its usefulness depends on the providers it supports today, and the alpha label means users should expect rough edges and should test on disposable resources first. The project's clear split between enforced controls and agent instructions offers a useful model for similar tools, and future releases will show whether provider coverage broadens.
Related: Run n8n on Vercel for Free With a Neon Database · Free n8n Workflow Builds Local Business Leads from Google Places
Comments (0)