> 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/november-2026/november-5-2026.md).

# November 5, 2026

Fewer tabs. Fewer tools.

Six updates to help you build and share demos with less back-and-forth.

***

### 🔍 Zoom in HTML demos

Track and zoom now works in HTML demos, the same way it does in screenshot demos. Zoom in on a specific element to draw attention to the part of the screen that matters.

1. Open an HTML demo in **Guide** mode and add a guide to the element you want to highlight.
2. Select **Zoom** in the toolbar.
3. Set the zoom level and position.

<figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FhKVNR6fYmBBNWWjiVdvH%2FDarkened%20Storylane%20Zoom%20demo%20editor%20(1).png?alt=media&amp;token=98bcd96d-a539-4570-b940-2ccab540014a" alt=""><figcaption></figcaption></figure>

Useful for dense screens and small UI details that get lost at full size.

***

### 🎙️ Voiceover upgrade

The voiceover panel now runs on the **v3** model, up from v2, and supports **audio tags**, so you can shape how a line is delivered, not just what it says.

<figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FrI7ZILi1GywOPWXBzXmK%2FVoiceover%20editor%20with%20highlighted%20audio%20tags.png?alt=media&amp;token=8b4466b3-7a9d-4842-9325-92e47e91db90" alt=""><figcaption></figcaption></figure>

Open the voiceover panel on any step to try it.

***

### 🌐 Auto-select language

Demos with translations can now open in each viewer's language automatically.

1. Open **Languages** in the editor header.
2. Toggle on **Auto-select by browser language**.

<figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FWgqVuM1lb0IYd4pZmBh0%2FBrowser%20language%20auto-select%20highlighted.png?alt=media&amp;token=a57de62c-f442-4a90-b988-23dc54b5af7e" alt=""><figcaption></figcaption></figure>

When a viewer's browser language matches a version of your demo, that version loads for them. Everyone else sees the default language, and viewers can still switch languages in the player.

{% hint style="info" %}
Auto-select only works for languages you've added. Add more from the same panel with **Add language**.
{% endhint %}

***

### ✂️ Cut in the video editor

Remove the parts of a video step you don't need. Trimming handles the start and end of a clip. Cut handles everything in between.

{% @storylane/embed subdomain="app" linkValue="5e7tmradpxqi" url="<https://app.storylane.io/share/5e7tmradpxqi>" %}

1. Open a video step and select the **scissors** icon to enter cut mode.
2. Cut the clip at the points you want.
3. Exit cut mode.
4. Select any segment to delete it or change its playback speed.

***

### 🤖 MCP updates

Your AI client (Claude, ChatGPT, or Microsoft Copilot) can now do more with Storylane:

* **List themes and labels** - see what's available in your workspace.
* **Create AI Hubs** - build a hub for a prospect from your demos, using their company name and an optional note on use case or audience.
* **Deals** - list CRM deals, pipelines, and stages.
* **Create alerts** - set up alerts for demos or hubs, with Slack channels, Slack users, and CRM stages referenced by name. If a name is ambiguous, your AI client asks you to pick instead of guessing.

Try this prompt:

> Create an AI Hub for Acme Corp, focused on their sales team and CRM integrations.

{% hint style="info" %}
Deals tools require a connected HubSpot or Salesforce integration.
{% endhint %}

Full setup and tool list: [MCP docs](https://docs.storylane.io/integrations/integrations-and-data-flow/mcp). Ready-to-paste prompts: [storylane.io/mcp](https://www.storylane.io/mcp).

***

#### ⏭️ Skippable lead forms

Not every viewer is ready to share their details on the spot. You can now add a skip option to your lead forms so they keep watching instead of leaving.

1. Open the lead form step > Edit guide > Config >  toggle on **Allow skipping lead form**.

<figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FlRpP6O2al8kJ4Y3cJhQe%2FLavender%20outline%20highlights%20Skip%20for%20now.png?alt=media&amp;token=32eb19a7-3d07-4d54-9243-facb3fd8a60c" alt=""><figcaption></figcaption></figure>

Viewers see a Skip for now link under the form and continue the demo without submitting.

{% hint style="info" %}
Viewers who skip don't submit their details, so they won't be captured through that form.
{% endhint %}

***

Thanks for trusting us.\
If you have any questions, feel free to reach out at <support@storylane.io>.


---

# 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/november-2026/november-5-2026.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.