> For the complete documentation index, see [llms.txt](https://docs.mercuri.cx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercuri.cx/features/conversations-inbox/adding-and-managing-tags-from-the-conversation-list.md).
# Adding and Managing Tags from the Conversation List
You can add and manage tags directly from the **conversation list**, without opening individual conversations. This helps you organize chats more efficiently.
### **How to add tags for conversations?**
1. Locate the conversation in the conversation list.
2. Click on **Add Tags** (or **Manage Tags** if tags already exist).
3. Enter the required tag and save it.
***
### **How to manage tags for conversations?**
* Click on **Manage Tags** to:
* Add additional tags
* Edit existing tags
* Remove tags that are no longer needed
***
### How to filter conversations using tags?
You can also filter conversations based on tags to quickly find relevant chats.
To filter by tags:
1. Click on the **Filter** icon at the top of the conversation list.
2. Select the required tag(s).
3. The conversation list will update to show only conversations matching the selected tags.
This makes it easier to track, organize, and manage conversations, especially when handling a large number of chats.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.mercuri.cx/features/conversations-inbox/adding-and-managing-tags-from-the-conversation-list.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.