Versioning Camelia's work: list versions, explain changes, revert

Camelia treats your project like a versioned timeline, so you can review what changed and roll back safely. Three tools cover the workflow: listing versions, explaining changes, and reverting.

List versions

Ask Camelia to list versions and she returns the project's saved timeline — each entry with its short identifier, message, author, and when it was saved. This is how she (and you) find exactly which save you mean before comparing or reverting.

Explain changes

Ask "what changed?" and Camelia compares two saved versions, returning the added, modified, and removed files along with their content at each version, then describing the differences in plain language. You can name two specific versions, or omit them to compare the two most recent saves — handy right after a Save when you want a summary of what just happened.

Revert to a version

If you want to go back, Camelia can revert the project to an earlier saved version, restoring those files as the live project. The key detail: reverting is non-destructive. It's recorded as a new version, so nothing is lost and the revert itself can be undone. That means you can experiment freely — try a direction, and if it doesn't work out, roll back without fear of losing anything.

A typical flow

A natural sequence is: list versions to see the timeline, explain changes to understand what differs between two points, then revert if you decide an earlier state was better. Because every step is grounded in your real project history and every revert is itself saved, the whole timeline stays intact and auditable.

Use versioning whenever you want to compare directions, document what a Save contained, or safely return to a known-good state.