> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/experience-editor/experience-management/loading-an-autosave.md).

# Loading an autosave

The autosave feature automatically saves a copy of your experience as you work. To load an autosave file, complete the following steps:

1. Open the ENGAGE app and log in.
2. On the menu screen, select **Create & Edit**.
3. On the **Creator Tools** page, select **Experience Editor**.
4. Select **Load Scene**.
5. From the **Load from Auto-Save** list, select a file.

{% hint style="info" %}
If you have not entered a value in the Title field of the save settings, the autosave files are named with the time and date when they were saved.
{% endhint %}

![Location of the Load from Auto-Save list](/files/Xvr48Kgfk5dHhkFqkgto)


---

# 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://docs.engagevr.io/engage/experience-editor/experience-management/loading-an-autosave.md?ask=<question>&goal=<endgoal>
```

`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.