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

# Build and launch an app

Give your agent a visitor action, a deployment target, and a clear test to run. If the task needs provider access, paste a [scoped Godmode note](/docs/agents#pin-a-task-to-one-setup) into the conversation.

```text
Build a booking-request site using my existing repository and hosting project.
A visitor should submit a request and see a confirmation.
Skip payments. Ask before taking on a new recurring charge.
Deploy it, submit a test request, and record the live URL and rollback steps.
```

## Check existing work and access

Review the project's instructions, source, and deployment settings. If you need Godmode, use the scoped task note or capture the command prefix with `godmode active --command`. Run `help` with that prefix to see the available key names and profile fields.

Use a working provider login or selected keys from Godmode. Verify the account and project with a read before making changes. See the [provider catalog](/docs/providers).

## Build the visitor flow

Complete the main action, including its success and error states. Check that a visitor can finish it on a phone and with a keyboard. Put private runtime credentials in the deployment's secret store.

## Confirm spending and public actions

Use the authority given in the task. Confirm domain purchases, recurring charges, live payments, or public messages before proceeding if the user has yet to authorize them. The account owner handles sign-in, MFA, and provider review.

## Deploy and test

Deploy to the intended project, then open its live URL. For the booking site, submit a test request, check the confirmation, and verify that the request reached its destination. Keep test records separate from customer activity.

## Save the release details

Record the live URL, source revision, deployment ID, observed result, and rollback steps in the project. See [Change an existing app](/docs/changes) for the next release.
