;
};
Available only in [W\&B Multi-tenant Cloud](/platform/hosting/#wb-multi-tenant-cloud).
This page describes how to manage your conversations with ARIA: starting and resuming chats, queueing follow-up messages, adding context, granting network access, and giving feedback on responses. Context can include runs, workspace panels, W\&B Weave traces, and images. It also covers organizing your chat history by renaming, pinning, and deleting conversations.
## Start a new chat
To start a new chat, open ARIA, then click the pencil icon in the upper right corner of the chat window.
You can run multiple chats in parallel at a time. ARIA notifies you when it responds to a chat, even if you have closed the chat window.
Starting a new chat does not delete your previous conversations. To [view previous conversations](/aria/chat#view-chat-history), click **** (**Reveal chat history**) to open the chat history sidebar.
## Send a message
Type a message and press **Enter** to send it.
* Press **Shift+Enter** to add new lines.
* Click **+** to add images.
* To add a run reference, type `` and select a run from the list. Type to filter and fuzzy-search the list.
* For more flexibility, compose a more complex message in a text editor and paste it. Plain text is supported, and pasted `@` characters are not resolved to run references.
To cancel the current operation and *immediately* send the next [queued message](#queue-messages), press the stop icon to the right of the text input.
To help you stay in context, ARIA renders line plots and bar charts directly in the chat, with support for full-screen view. Hovering over a run in the workspace's **Runs** tab highlights the run's plots in ARIA, and hovering over a panel in ARIA highlights the run in the **Runs** tab.
## Queue messages
The message queue holds follow-up tasks and questions you send to ARIA while it works. ARIA runs each queued message in order using the full conversation as context. The next message runs as soon as the previous one finishes.
Use the queue to line up several steps at once and step away, rather than returning to the chat to send each one. For example, you might start with a comparison:
While ARIA works, send additional requests to the chat window. W\&B adds pending requests to ARIA's queue.
This example sends two messages at once:
```text title="Queued messages" theme={null}
Chart validation loss against learning rate for those runs.
Write up the comparison as a report I can share with my team.
```
The queue header shows how many messages are waiting. Each queued message has three controls:
* **Pencil icon** (): Edit the message before ARIA runs it. ARIA moves the message into the message box and removes it from the queue, so send it again to requeue it. This control is unavailable while the message box already holds a draft.
* **Up arrow icon** (): Run the message now instead of waiting its turn. ARIA stops what it's working on and runs this message next. The other queued messages keep their order.
* **Trash can icon** (): Delete the message from the queue.
Queued messages keep the context you attached to them, including [run mentions](/aria/chat#add-context-to-a-conversation) and [images](/aria/chat#add-an-image-to-a-conversation).
Queueing begins after your first message in a chat, because a queue needs a conversation to run against. The first message you send, and any message you send to an idle chat with an empty queue, goes to ARIA immediately. Each chat keeps its own queue, and the queues in chats you close keep running.
If ARIA needs a clarifying answer or your permission before it continues, the queue pauses until you respond. To run a queued message without responding first, click the up arrow icon next to it.
## Manage conversations
The following sections describe how to view, rename, pin, and delete your conversations.
### View chat history
To view previous conversations:
1. Open ARIA.
2. Click **** (**Reveal chat history**) to open the chat history sidebar. It's collapsed by default. The same control reads **Collapse chat history** while the sidebar is open.
3. Select a conversation to resume it.
Pinned conversations appear first, under a single **Pinned** header, not grouped by date. Unpinned conversations follow, grouped **Today**, **Yesterday**, **Last 7 Days**, **Last 30 Days**, then by month, then by month and year for conversations older than a year. Within each group, the most recently active conversation appears first.
Hover over a conversation row, or focus it with the keyboard, to reveal two controls:
* **** (**Pin chat** / **Unpin chat**): see [Pin a conversation](#pin-a-conversation).
* **** (**Chat actions**): opens a menu with **Rename chat** and **Delete chat**. See [Rename a conversation](#rename-a-conversation) and [Delete previous conversations](#delete-previous-conversations).
The chat history sidebar's **Customize** section also lists the ARIA automations you've created. See [Use automations with ARIA](/models/automations/create-automations/aria).
### Rename a conversation
When you send the first message in a new chat, ARIA generates a title for the conversation. The title shimmers in the chat history sidebar while ARIA writes it. If ARIA can't generate a title, the conversation keeps an excerpt of your first prompt as its title. ARIA titles a conversation only once. Follow-up messages don't change the title.
To give a conversation a different title:
1. In the chat history sidebar, hover over the conversation you want to rename.
2. Click **** (**Chat actions**), then select **Rename chat**. The title becomes an editable field.
3. Type a title, up to 255 characters.
4. Press **Enter** or click **** (**Save chat title**) to save. Press **Escape** or click **** (**Cancel rename**) to discard your change.
Clearing the field and saving replaces the title with an excerpt of your first prompt, or **Untitled conversation** if no excerpt exists. Saving whitespace-only input cancels the rename instead of clearing the title.
Renamed titles sync across your open browser tabs. You can also rename a chat from your phone. See [Chat with ARIA](/platform/hosting/monitoring-usage/mobile-app#chat-with-aria) in the mobile app docs.
### Pin a conversation
Pin a conversation to keep it at the top of the chat history sidebar instead of letting it slide down as new chats accumulate.
1. In the chat history sidebar, hover over the conversation you want to pin.
2. Click **** (**Pin chat**). The conversation moves under the **Pinned** header.
3. To unpin, click **** (**Unpin chat**) on a pinned conversation.
There's no limit on how many conversations you can pin, and pin changes sync across your open browser tabs. Pinning affects only your own conversation list, not what teammates with access to the same project see.
### Delete previous conversations
To delete a previous conversation:
1. Open ARIA.
2. Click **** (**Reveal chat history**) to open the chat history sidebar.
3. Hover over the conversation you want to delete, click **** (**Chat actions**), then select **Delete chat**.
4. In the **Delete this chat?** dialog, click **Delete** to confirm. You can't undo this action.
## Undock chat window
You can undock the chat window into a separate window, which allows you to view ARIA's response side-by-side with your project data.
To undock the chat, click the undock icon in the upper right corner of the chat window next to the close (**X**) button.
## Add context to a conversation
Attach runs, workspace panels, and Weave traces and evaluations to a chat to give ARIA the exact context for your question. Each item appears in the message box as a removable tag. You can attach several items to a message. Adding context doesn't send the message on its own. When you're ready, click **Send**.
When you add context from a page, ARIA adds it to the conversation that's open in the chat window. If no conversation is open, ARIA starts a new one.
### Mention a run
Type `@` in the message box and select a run. For example, you can ask ARIA to analyze a specific run by including the run's name in your prompt:
```text title="User prompt" theme={null}
Analyze the run @run-20230615_123456-abcdefg and summarize the results
```
You can also add a run from the workspace's **Runs** table. Hover over the run, click its **action ()** menu, then select **Ask ARIA**.
### Add a workspace panel
To attach a workspace panel to a chat:
1. In your workspace, hover over the panel and click its **action ()** menu.
2. Select **Ask ARIA**. ARIA opens with the panel attached.
3. Type your question, such as `Why does loss spike after step 2,000?`, then send it.
**Ask ARIA** appears in panel menus in workspaces you can edit. It doesn't appear in panels in reports.
### Add Weave traces and evaluations
In Weave, click the ARIA button to attach traces, evaluations, or evaluation results to a chat. Hover over the button to see its label, such as **Ask ARIA about this trace** or **Ask ARIA about these evals**. The button appears in these places:
* **Traces** or **Evals** table: Select one or more rows. The button appears in the table toolbar and attaches every selected row.
* **Trace or evaluation details page**: The button appears in the page header.
* **Evaluation comparison**: When you compare evaluations and view an example's details, the button attaches the predictions and scores for that example.
ARIA uses the attached traces and evaluations to answer your question. For example:
```text title="User prompt" theme={null}
Why did the model score lower on these examples than in the previous evaluation?
```
## Add an image to a conversation
Click the plus icon (`+`) in the lower left corner of the chat window to add an image to your conversation. You can then ask ARIA to analyze the image or provide information about it.
## Grant network access
When a task needs a domain that ARIA's sandbox blocks, ARIA asks you for network access and waits for your answer. For example, a task that installs a Python package needs `pypi.org` and `files.pythonhosted.org`. By default, the sandbox where ARIA runs code can reach W\&B services but blocks most other domains on the internet.
The request appears in the chat under **The agent is requesting network access**. It shows the reason for the request and lists the requested domains, all selected. Respond to the request in one of these ways:
* To grant access, clear any domains you don't want to allow, then click **Grant access**. ARIA continues its work and can reach the granted domains.
* To deny access, click **Deny**. ARIA continues without the extra access.
While a request is waiting, you can't send messages, and queued messages don't run.
Code that runs in the sandbox can send data to any domain you grant. Grant access only to domains you trust.
Granted domains stay available for the rest of the conversation until you revoke them. Each new chat starts with only the default access. You can't add domains yourself. ARIA requests them when a task needs them.
### Review or revoke network access
After you grant access in a conversation, **** (**Manage network access**) appears in the message box, next to the plus icon (`+`).
To revoke access:
1. Click **** (**Manage network access**). A list of the conversation's granted domains opens.
2. Clear the domains you want to revoke.
3. Click **Update access**.
W\&B sends ARIA a message listing the revoked domains, and ARIA runs without them from then on. You can't change network access while ARIA is working.
## Provide feedback
Click the thumbs up or thumbs down icon at the end of the response to provide feedback on ARIA's response. Your feedback helps W\&B improve ARIA's performance and accuracy.
For information about how W\&B handles data usage for ARIA, see [Governance and security](/aria/governance).
## Queue messages
The message queue holds follow-up tasks and questions you send to ARIA while it works. ARIA runs each queued message in order using the full conversation as context. The next message runs as soon as the previous one finishes.
Use the queue to line up several steps at once and step away, rather than returning to the chat to send each one. For example, you might start with a comparison: