Building

Reviewing changes

Accept, reject, diffs, versions and rollback — nothing lands in your project without you.

Updated 21 Sept 2026

Qyant never writes to your project on its own. Everything the model produces is a proposal; this page is about how you act on it.

The review panel

When a response finishes, its file changes appear as a list: created files, updated files and deletions, each with a coloured marker in the file tree. Click any file to see the diff — added lines, removed lines, with the surrounding context.

You have three choices per change set:

  • Accept all — every file is written, the project's version increments, the sandbox receives the files and the preview reloads.
  • Reject — the whole proposal is discarded. The chat keeps the model's message so you can refer to it in your next prompt.
  • Per-file — accept some files and reject others from the diff view. Accepted files become one version; rejected ones are dropped.

Until you choose, the proposal stays pending and the preview keeps running the last accepted version.

Versions

Every accepted change set — and every manual save in the editor — creates a new version: a full, immutable snapshot of the project's files. The version number is shown in the project header (v13) and in each review card (v12 → v13).

Rolling back

Open the project's version history and choose Revert on any earlier version. Reverting creates a new version whose contents match the old one, so history is never rewritten and you can always come forward again. The sandbox is synced and the preview reloads immediately.

Reviewing well

  • Read the deletions first. Removed lines are where surprises hide.
  • Check lib/db.ts and schema changes carefully. Database changes are the hardest to undo once real data is in.
  • Reject early. If the direction is wrong, reject and re-prompt; don't accept and then ask for a fix on top.
  • Trust but verify the preview. Accepting reloads the preview in a few seconds — click through the feature before the next prompt.

What happens to .env

The model can read the variable names in your .env but never the values of managed secrets (DATABASE_URL is shown to it as <managed-by-qyant>). When you accept a change that touches .env, Qyant restores the real values before writing. See Environment variables.