> 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/february-2025/february-10th-2025.md). # February 10th, 2025 Hi there, Storylaners! 👋 We know your time is valuable—that’s why we’re rolling out features to streamline your demo creation and make your demos more engaging. Introducing... ### **Storylane Desktop App for Mac** Say hello to high-quality recording with the new **Storylane Desktop App**! Now, you can **record any screen, any app, any time**—without being limited by browser extensions. Whether you're switching between apps, navigating through complex workflows, or showcasing product features across multiple screens, the **desktop app captures everything smoothly**. Try this interactive demo to see how it works below 👇 {% @storylane/embed subdomain="app" linkValue="ltrq1gundqac" url="" %} ### **Lily AI's Image Generator** No more searching or manual uploads! With **Lily AI’s Image Generator**, you can create **high-quality, on-brand visuals** in just a few clicks. 🔹 **Instant AI-generated images**—Just describe what you need.\ 🔹 **Effortless image creation**—No design skills required.
Try this interactive demo to see how it works below 👇 {% @storylane/embed subdomain="app" linkValue="acp246gefznr" url="" %} Stay cool and happy demoing! ✌️ --- # 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/february-2025/february-10th-2025.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.