Skip to content

Change your app

Follow-up changes, messages while a build runs, coming back in a new chat, versions, and starting again from the original.

An app is never finished after the first build. Every change is a follow-up: you write what to change in the same chat, Vibe Coder plans just that change, builds it, runs the checks again and deploys the new version at the same link.

Ask for a change

Type in the composer (Reply or refine…), for example:

  • "Add a weekly summary screen with the number of days each habit was done."

  • "Make the colours calmer and the buttons bigger."

  • "Habits should have an optional reminder time."

  • "The streak resets wrongly when I skip Sunday: weekends should not count."

The follow-up gets its own plan card (only this change, not the whole app again), its own checks, and a new deploy. The preview keeps showing the current version with Updating your app… until the new one runs.

Be specific about what and where. When something is wrong, say what you did, what you expected and what happened instead; a screenshot attached with the paperclip helps.

Change course while it builds

You do not have to wait. Type while a build runs: the message is queued (the agent reads it at its next step) and Vibe Coder takes it into account before its next move. To throw the build away instead, click Stop generating and write the new request.

Come back later

Open the project from Projects (or the sidebar) to continue in its latest chat. If the project was idle for more than 30 minutes, the first build or opening the preview restores its sandbox in about a minute (Restoring your previous session…).

You can also start a new chat about an existing app ("in my habit tracker, add…", or "where is my habit app?"). Vibe Coder finds the app by name. If the app is deployed and has changed since its first version, it asks once:

  • Continue from the last version: build on what is deployed now (usual);

  • Start from the original version: go back to the first deployed version, with its description, and build from there. Later versions are not deleted.

Versions and branches

Every follow-up is saved on its own branch in the app's repository; the first build is the app's main version. Vibe Coder keeps snapshots of the last three deployed versions for the question above. See Download the code and git.

What Vibe Coder remembers

Between chats, Vibe Coder keeps a short project memory (what the app is, its screens, its data, the decisions you made) and your personal memory (your preferences). It reads both at the start of every build, so you do not need to repeat yourself. See Settings and memory.

Last updated 18 Nov 2026

Change your app | REM Vibe Coder · REM Platforms Blog