> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/labeling/labeling-editor-interface/llm-chat-labeling-editor.md).
# LLM Chat Labeling Editor
Overview of the text labeling editor in Ango Hub
Ango Hub provides a labeling editor with which users can have live conversations with LLMs, and with which existing LLM conversations can be annotated.
The LLM Chat Labeling Editor is opened when a user opens a LLM Chat-type asset. For more information on how to create and/or import such assets, please [read this docs page](/data/importing-assets/creating-and-importing-llm-chat-assets.md).
{% hint style="info" %}
This article will exclusively go over Ango Hub’s LLM Chat labeling interface. Features common to all labeling editors are instead [explained here](/labeling/labeling-editor-interface.md).
{% endhint %}
## Overview
### Supported Labeling Tools
The text labeling editor supports following labeling tools:
**Tools**
* Message
**Classifications**
* Radio
* Checkbox
* Single-Select Dropdown
* Multi-Select Dropdown
* Single-Select Tree
* Multi-Select Tree
* Text
**Relations**
* Single Relation
* Group Relation
## Pre-Existing Conversations and Live Conversations
As outlined in [the docs page on creating LLM Chat-type assets](/data/importing-assets/creating-and-importing-llm-chat-assets.md), there are two possible types of LLM Chat assets: "pre-existing" and "live" conversations.
Pre-existing conversations are conversations which already happened outside of the Ango Hub platform and you import them to be annotated.
Live conversations start empty, and the annotator has a live conversation with your LLM directly from Ango Hub.
### How to chat with your LLM live from Ango Hub
{% hint style="info" %}
This functionality is not available on private cloud and on-premise deployments of Ango Hub.
{% endhint %}
Once the LLM Chat-type assets have been created, if they are empty (of the "live" type), when the user enters the asset, they will be greeted with an empty message UI:
To prompt the LLM, enter your text in the text area labeled *Enter prompt here...* and hit Enter or the Send button. The LLM will receive your prompt and answer.
#### Entering Markdown and LaTeX in prompts
You may use Markdown and, between dollar signs, LaTeX in your prompts. To preview the final, formatted version of your prompt, click on the "Markdown" icon to the left of the prompt text area:
If the model's outputs also contain Markdown or LaTeX, they will automatically be formatted. To view a message's output in plain text (unformatted), click on the *Switch to Raw Text* button below the message:
## How to Annotate LLM Chats on Ango Hub
Regardless of whether the chat is a pre-existing one or a live one, from the *Tools* section on the left-hand side of the screen, select a [*Message*](/labeling/labeling-tools/tools/message.md)-type tool. Then, click on the chat message you would like to classify. The classifications that have been nested under the Message-type tool will appear, and you will be able to answer them.
Click on *Save* or *Submit* when you are done.
---
# 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.imerit.net/labeling/labeling-editor-interface/llm-chat-labeling-editor.md?ask=&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.
