> Godmode v0.19.2 documentation · Reviewed 2026-11-17
> Source: https://godmode.build/docs/v0.19.2/launch

# Build and launch an app

Give your agent this guide with a request like:

```text
Build a booking-request site for my business.
Use my existing repository and hosting account where possible.
A visitor should submit a request and see a confirmation.
Do not accept payments yet. Ask before any new recurring charge.
Deploy it, test the visitor flow, and leave the URL and recovery steps.
```

Godmode supplies selected credentials and profile fields. Your coding agent builds and deploys through your tools and accounts.

## Check existing work and access

Read the project instructions, source, deployment settings, and existing work. Preserve a working app's architecture. Then run:

```sh
godmode help
godmode list
```

Read only the profile fields you need. Keep a suitable working login in the provider's own tool. Otherwise, read `godmode provider SLUG` and use only the needed saved credentials. Check the account and target resource with a read before changing them. See the [provider catalog](/docs/v0.19.2/providers).

## Build the visitor flow

Build the smallest complete version, including loading, empty, success, and error states. Check keyboard and phone use. Keep management credentials out of browser code and repositories; use the product's server secrets and bindings.

Use real product facts. Do not invent customers, availability, guarantees, endorsements, or staffing. Before collecting personal data, sending messages, or taking payments, settle the relevant consent and legal requirements.

## Confirm spending and public actions

Provider access can create real charges or public changes. Follow the authority already given; if no spending limit is set, keep new spend at zero.

A key does not authorize subscriptions, domain purchases, live payments, paid campaigns, or posts in the user's name. Prepare a concrete result before asking for an approval that is still needed. Sign-in, MFA, provider review, and legal or banking commitments stay with the account owner.

## Deploy and test

Deploy to the intended account and project. Record the source revision and deployed version. Open the HTTPS URL and complete the main action:

- For a form, confirm the request reaches its destination.
- For sign-in, complete authentication and return to the app.
- For payments, label test mode clearly and never count test payments as revenue.

Use test data, keep it separate from real customers, and clean up disposable test records.

## Save the release details

Leave the live URL, access requirements, repository, revision, actual test results, remaining limits, and exact recovery steps in the project's documentation or tracker. Use [Change an existing app](/docs/v0.19.2/changes) for later updates.
