> 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/august-2026/august-12-2026.md).

# August 12, 2026

Hey Storylaners! Big one this time. You can now run demos in any language, manage your entire demo library from Claude or ChatGPT, and give viewers unified media controls across every demo type.

### 🤖 MCP

Connect Claude, ChatGPT, Cursor, or any MCP-compatible AI client to Storylane and manage your demo library with natural language.

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

What you can do from your AI client:

* Analyze demo performance, leads, and account engagement
* Create demos from screenshots or screen recordings
* Personalize demos for specific accounts or personas
* Generate and manage trackable share links
* Publish demos and manage your library

**Connect in 3 steps**

1. Copy the Storylane MCP server URL from the [docs](https://docs.storylane.io/integrations/integrations-and-data-flow/mcp)
2. Paste it into your AI client as a custom connector
3. Sign in to Storylane and approve access

***

### 🌐 Multi-language demos

{% hint style="info" %}
Available upon request for Premium Plan+ customers. Please contact your CSM to enable it.
{% endhint %}

One demo. Every language. No duplicate copies.

Add language versions to any demo — AI translates the guide content, you review it in context, and viewers switch languages themselves in the player.

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

**How it works:**

1. Open any demo and click **Languages** in the editor header
2. Click **Add language** and select a target language and AI voice
3. Review the AI-generated translation in context
4. Accept changes — the version is saved and the Languages badge updates in the header
5. Manage all versions from the Languages panel — preview, sync with source, set a default, or delete

Viewers see a language selector in the player. One link covers every market.

{% hint style="info" %}
Keeping translations in sync: use **Sync with original** in the Languages panel whenever the source demo is updated.
{% endhint %}

***

### ▶️ Unified play bar

All media controls — play, pause, scrub, mute, duration — are now in a single persistent bar at the bottom of every demo.

<figure><img src="/files/8fsVATIudhgPHmjuk3Zh" alt=""><figcaption></figcaption></figure>

The play bar appears automatically on any step that has video, voiceover, or avatar content.

* **Nav bar on** — the play bar inherits your brand colors and sits alongside chapter and progress controls
* **Nav bar off** — the play bar appears in neutral colors, functional without drawing attention

No settings to change — it works automatically based on your existing nav bar configuration.

***

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 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.storylane.io/changelog/august-2026/august-12-2026.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.