> 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/repx-updates/october-2026/october-1-2026.md).

# October 1, 2026

### **🎭 New video avatars and voices**

#### Advanced video avatars, powered by Anam

RepX now supports several more advanced video avatars from Anam, available in Settings.

<img src="https://1495528283-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FALMQQuRpzht4qmQBwJJz%2Fuploads%2FjWQG7s9Dveaw2KjOZU8L%2Funknown.png?alt=media&amp;token=6bae4eec-809e-4f24-a224-48db7b688bdf" alt="" height="401" width="705">

#### Configurable voices, powered by Cartesia

You can choose a voice for each RepX agent in Settings from a library of thousands. Search by language or voice name, pick from accents like American, British, and Australian English, and play a sample before you save.

<img src="https://1495528283-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FALMQQuRpzht4qmQBwJJz%2Fuploads%2F51cptikiTGJdPz5udiW0%2Funknown.png?alt=media&amp;token=659446d5-6a53-4fa7-bba2-56a3fa6001fb" alt="" width="375">

### **🖥️ Immersive view**

Immersive View gives RepX a full-page experience. Use it as a dedicated page, or embed it as a section within any page so RepX sits alongside your content instead of in a floating widget. [See it on Backstory’s site](https://www.backstory.ai/ask-now).

Find the embed code under Settings → Embed.


---

# 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/repx-updates/october-2026/october-1-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.
