> For the complete documentation index, see [llms.txt](https://guides.livingwriter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.livingwriter.com/desktop-app-+-web-version/version-history.md).
# Version History
The Revision History is where you can find the various versions of your manuscript, both current and past. This invaluable tool allows you to recover old and recent versions of your writing, ensuring that you can easily track changes and restore previous iterations as needed.
You can find it at the top, under the ''Revision'' tab:
When clicked, you will now see in the right sidebar all the available versions and sub-versions of your manuscript:
You can revert to an old version, delete it, edit it, and copy it. Additionally, you can check the Local Versions, which reflect the most recent changes applied to your manuscript and are typically available for around 48 hours.
---
# 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://guides.livingwriter.com/desktop-app-+-web-version/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.
