> 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/april-2026/april-3-2026.md).

# April 3, 2026

Hey Storylaners! The RepX training page is live in the product dashboard.

### 📖 Train your RepX agent

Login to Storylane and head to the [RepX Dashboard](https://app.storylane.io/repx-dashboard/training). From here, you can now add content that RepX learns based on which RepX generates answers. From the training page in the dashboard, you can now<br>

* **Add and delete webpages**, and view or remove that RepX crawls to learn about your products
* Add, edit, or delete **FAQs**
* Add and remove **Storylane demos** your agent can present
* Add and delete **images** your agent presents
* Set **display instructions** for demos and images that guide RepX in deciding when a demo or an image can be presented along with answers
* **Search content** your agent has been trained on


---

# 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/april-2026/april-3-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.