> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/convai-unreal-engine-plugin/editor-window/browse-samples-and-content.md).

# Browse samples and content

Check the current Samples area in the Convai Editor window and understand how sample projects will be surfaced in future updates.

The Samples area in the Convai Editor window is reserved for future sample projects and templates. In the current plugin version, the header dropdown for **Samples** shows a **Coming Soon** message, and the Samples page is not a complete sample download or launcher workflow.

### Prerequisites

* Convai Unreal Engine plugin installed and enabled.
* Convai Editor window available from **Window > Convai > Open Convai Editor** or the **Convai Editor** toolbar button.

### Current behavior

The current UI contains static sample cards used by the editor window. The card data includes example names such as **Neural Nexus Game**, **Classroom Demo**, **Train Station Demo**, **Fire Station Demo**, **Space Demo**, and **Forest Demo**.

{% hint style="info" %}
The current Samples page does not open levels, Blueprints, or downloadable projects when a card is selected. Future plugin updates are expected to add sample projects and templates to this area.
{% endhint %}

### What to use today

Use the getting started guides when building or testing a scene today. The current Samples page does not provide a complete demo level or a sample launcher workflow.

For the first working scene path, follow [Add your first Convai character](/api-docs/plugins-and-integrations/convai-unreal-engine-plugin/getting-started/add-your-first-convai-character.md). For the core Actor and Component setup used by that path, see [Scene components reference](/api-docs/plugins-and-integrations/convai-unreal-engine-plugin/getting-started/scene-components-reference.md).

### Future sample content

When Convai adds sample projects to the Convai Editor window, this page will list the exact sample names, what each sample demonstrates, and the steps to open or import them. Until then, avoid relying on the Samples area as a setup path for production projects or support reproduction steps.

### Next steps

{% content-ref url="/pages/62jSGyEcDL1LUmbU2yXD" %}
[Add your first Convai character](/api-docs/plugins-and-integrations/convai-unreal-engine-plugin/getting-started/add-your-first-convai-character.md)
{% endcontent-ref %}

{% content-ref url="/pages/TAMFvBX6DiCF3cUBeYtP" %}
[Scene components reference](/api-docs/plugins-and-integrations/convai-unreal-engine-plugin/getting-started/scene-components-reference.md)
{% endcontent-ref %}


---

# 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.convai.com/api-docs/plugins-and-integrations/convai-unreal-engine-plugin/editor-window/browse-samples-and-content.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.