Rollback

After your app is generated, you can continue improving it from AgentQ Chat. You can request new features, bug fixes, and UI tweaks in ongoing iterations.

To keep these iterations safe, AgentQ supports rollback for project updates.

Why this matters

Not every update behaves perfectly on the first try. Rollback gives you a fast way to recover a stable version.

How rollback works

Each project update is tracked with version history.
When you request a new feature or UI change in AgentQ Chat, a small rollback button appears with that update message.
If you do not like the result, or something breaks, you can roll back to the previous state.
This works because projects are version controlled with Git under the hood.

Typical workflow

Open your project in AgentQ Chat.
Request a new feature, bug fix, or UI improvement.
Review the updated app behavior.
If the result is not acceptable, click the rollback button for that update.
Confirm the project is restored to the previous working state.

When to use rollback

A new feature introduces unexpected behavior.
A bug-fix update causes regression in another flow.
A UI change does not match your expected design.
You want to quickly return to the last stable version while refining requirements.

Best practices

Test core user flows after each update.
Make focused, incremental requests instead of large bundled changes.
Use rollback quickly when an iteration clearly misses the mark.