> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/project-settings/version-history.md).
# Version history
The Version History feature allows restoring different versions of a project.
#### Saving
* By default, auto-save functionality is enabled in projects, meaning the project automatically saves every minute when changes are detected.
* If auto-save is disabled, projects can be manually saved using **Ctrl+S**.
* Additionally, the project is automatically saved when navigating back to the dashboard.
All saved versions can be restored through Version History.
To access Version History:
1. Open the Menu and select "Version History"
2. On the right-hand panel, a list of all saved project versions will appear
\
Each version entry includes two icons:
* 
allows downloading a version file
* 
enables restoring the version directly onto the canvas
{% hint style="danger" %}
Downloaded version files are securely protected and can only be utilized by technical support
{% endhint %}
{% hint style="success" %}
These files help with troubleshooting and should be provided when contacting support
{% endhint %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.vectary.com/documentation/project-settings/version-history.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.