> ## Documentation Index
> Fetch the complete documentation index at: https://whip.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# How to edit your app on Whip

> Change anything about your Whip app by chatting in the same conversation. Every edit makes a new version, and the AI protects your existing work as it goes.

To edit an app on Whip, keep chatting in the same conversation. Tell the AI what to change the way you'd text a friend — "make it dark mode," "add a timer," "fix the scoring" — and it updates your app. Each edit creates a new [version](/building/versions-and-history), and the AI protects your existing work as it makes changes.

## What you can change by chatting

There's no separate edit mode — editing *is* the conversation. Here are the kinds of messages that work well:

<CardGroup cols={2}>
  <Card title="Style and vibe" icon="palette">
    "Make the background sunset orange," "use a rounded, playful font," "give it
    a dark theme." Look-and-feel changes land fast.
  </Card>

  <Card title="New features" icon="plus">
    "Add a streak counter," "let me sort the list by date," "add a confetti
    blast when I win." Build up your app one feature at a time.
  </Card>

  <Card title="Fixes" icon="wrench">
    "The total isn't adding up," "the button is off-screen on my phone." Describe
    what's wrong and the AI fixes it.
  </Card>

  <Card title="Content" icon="type">
    "Change the title to 'Taco Tuesday,'" "swap the sample questions for these,"
    "remove the last section." Edit words and data directly.
  </Card>
</CardGroup>

<Tip>
  One change at a time works best. Ask for the big thing, see the result, then
  ask for the next. It's faster than one giant message — more on this in [prompt
  tips](/building/prompt-tips-and-ideas).
</Tip>

## Every edit makes a new version

Each time you edit, Whip builds a fresh [version](/building/versions-and-history) of your app and adds it to your chat timeline as a card with its own icon and title. Your older versions stay put — nothing is overwritten. If an edit isn't what you hoped for, just ask the AI to go back to the previous version, and it builds a fresh one that returns to it. The AI is careful to protect what already works while it makes your requested change.

<Note>
  Editing draws from the same daily pool as building and remixing — up to 50 a
  day. It resets on its own; the full picture is in [build limits & failed
  builds](/building/build-limits-and-failed-builds).
</Note>

## Rate the AI's replies

See a thumbs-up and thumbs-down on the AI's messages? Tap one to send feedback. Thumbs-up asks an optional "what did you like?" note; thumbs-down lets you pick a reason and add details. It's optional, and it helps Whip improve — it doesn't change your app.

## Editing an app you've already published

You can keep editing an app after it's public — your live app doesn't change the instant you send a message. Here's how a change goes live:

<Steps>
  <Step title="Edit like normal" icon="message-circle">
    Send your change in chat. Whip builds a new version while your currently
    published version stays live and untouched.
  </Step>

  <Step title="Wait for it to complete" icon="check">
    Once the new version finishes building, it's ready — but not yet public.
  </Step>

  <Step title="Make it the live one" icon="rocket">
    Set the new version as your active version and re-publish it so the community
    sees your update. Full walkthrough in [publish your
    app](/sharing/publish-your-app).
  </Step>
</Steps>

## If an edit fails

Edits fail occasionally, and it's rarely a big deal. Whip retries automatically behind the scenes, and a failed edit never wipes your app or your history. The simplest fix is to **send another message** — repeat the request, or reword it — to pick up from where it left off. The complete rescue guide lives in [build limits & failed builds](/building/build-limits-and-failed-builds).

## Common questions

<AccordionGroup>
  <Accordion title="Will editing break my app?" icon="shield-check">
    The AI protects your existing work while it edits, and every version is saved
    — so if a change isn't right, you can [ask it to go back to an earlier
    version](/building/versions-and-history).
  </Accordion>

  <Accordion title="How many edits can I make?" icon="infinity">
    As many as you like, within the shared [daily
    limit](/building/build-limits-and-failed-builds) that building, editing, and
    remixing all draw from. It resets automatically.
  </Accordion>

  <Accordion title="Does editing a published app change it live right away?" icon="globe">
    No. Your published version stays live until you publish the new version
    yourself. Your audience only sees changes when you're ready.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Versions & history" icon="history" href="/building/versions-and-history">
    Browse and open any earlier version of your app.
  </Card>

  <Card title="Publish your app" icon="rocket" href="/sharing/publish-your-app">
    Push your latest version live for the whole community.
  </Card>
</CardGroup>