> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/changelog/updates-in-october-2022/october-10-2022.md).

# October 10, 2022

### **Improvements**

* **Autoplay demo for CTA link**: If the primary CTA button in the demo links to an external website, the demo will take the user to that link and not replay the demo flow. 
*  **Walkthrough widget resizes in image demos:** When the walkthrough widget is moved around in the demo editor, the size will not get resized automatically. 
* **Widget display in demos:** All widgets will be seen while viewing an image or HTML demo in preview mode and in multiple flows. 
* **Widget animation in the demo player:** The transition time was changed between widgets in a demo making the widget animation smoother. 
* **Resume demo tooltip:** If a user leaves an active demo session, a pop-up message "Resume Demo" is shown when they come back to that tab. This message disappears after two seconds or the user can dismiss it as well. 


---

# 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.storylane.io/changelog/updates-in-october-2022/october-10-2022.md?ask=<question>&goal=<user_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.