> 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-23-2026.md).

# October 23, 2026

### **🧩 New JavaScript function: `setContext`, for passing visitor information to RepX**

Your website often knows something about a visitor before they start chatting, like their name, their email, or what they entered in a form. `setContext` passes those details to RepX so it can use them in the conversation. You can pass:

* Default variables: name, email, and phone number
* Custom variables: any you’ve created in Settings → Variables (For example: pain-point, product, etc)
* Free-form context: anything else you want RepX to know about the visitor

A few ways to use it:

* Skip asking for an email if they’ve already submitted a form on your website.
* Ask different qualifying questions based on a visitor’s role or job title that they might have shared with you.
* Change the conversation flow for visitors based on geo, product, company size, etc.

[See the docs](https://docs.storylane.io/repx-chat/advanced/javascript-functions) to understand how you can pass context.

### **🛠️ Other improvements**

**Custom widget position:** Use `window.Repx.setOffset({ bottom: 20, right: 20 })` to change the widget’s position, if it hides anything on your website. Negative values move it in the opposite direction.


---

# 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-23-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.
