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

# Change an existing app

Name the behavior to change and the flow that must keep working.

```text
Show the selected date on the booking confirmation.
Keep the existing hosting and data model.
Verify the confirmation on mobile and on the deployed site.
```

## Check the current app

Read the project instructions and current diff. Reproduce the behavior, find the code that controls it, and check the existing deployment target.

If you need credentials, use the [task's pinned Godmode setup](/docs/v0.20.0/agents#pin-a-task-to-one-setup). Read the provider guide, then verify the intended account and resource with a read.

## Make the change

Reuse the current components and conventions. Keep unrelated edits intact. For a data change, check compatibility with the current app and verify recovery before any destructive migration.

## Test and deploy

Test the changed behavior and an adjacent flow. Review the diff. If the task includes deployment, confirm the reviewed revision is live in the intended project, then repeat the user action there.

## Record the result

Save the changed behavior, test results, revision, and live URL when applicable. If the new release fails, follow [Recover a failed deploy](/docs/v0.20.0/recovery).
