> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/reference/shared/version-history.md).
# Version History
Every time you make a meaningful change to an app or agent in Riff, the platform saves a checkpoint. Version History lets you look back at any checkpoint and restore it — so you can try things, change your mind, and recover if something goes wrong.
## Why this matters
When you're building or adjusting a procurement agent, you might make a change that has unintended effects — a new instruction that changes how the agent handles delivery exceptions, or a UI update that breaks a form. Version History means you're never one bad edit away from losing your work.
Think of it like track changes in a Word document, or the undo history in a spreadsheet — but for your entire app or agent.
## Viewing version history
Open an app or agent, then go to **Settings → Version History** (or click the history icon in the top toolbar). You'll see a list of saved checkpoints, each showing:
* **When** it was saved
* **Who** made the change (you or a teammate)
* **What changed** — a short summary of what was different
## Restoring a previous version
Click any checkpoint to preview what it looked like. If it's what you want, click **Restore this version**. The app or agent returns to exactly that state.
Restoring doesn't delete your more recent work — it's saved as a new checkpoint, so you can always come back to where you were.
## Automatic vs. named checkpoints
Riff saves checkpoints automatically as you work. You can also save a named checkpoint manually — useful before making a significant change you might want to roll back from.
To save a named checkpoint: go to **Settings → Version History → Save checkpoint now**, give it a name (e.g. "Before supplier portal redesign"), and click **Save**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.riff.ai/reference/shared/version-history.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
