> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/chat/search-for-chat-messages.md).
# Search for chat messages
Find specific chats or messages in a chat.
There are two ways to use the search feature in Chat:
* You can use the **Search** option in the left sidebar to locate a specific chat or group.
* Additionally, you can use the magnifying glass icon 
within a specific chat to find what you are looking for.
### Find a chat from the chat list
To find a chat in your list of chats:
1. Open the **Chat** page.
2. In the left sidebar, type a keyword in the **Search** box. You can find a chat by chat ID, name, or specific message. All chats that meet your search criteria are displayed.
3. Select the chat to open it.
### Search for a message inside a specific chat
To search for a specific message within a chat:
1. On the **Chats** page, open the desired chat conversation.
2. Select the magnifying glass icon .
3. Enter the keyword you want to find (for example, invoice).
4. Browse through the highlighted matching messages.
5. Select **Close** to close the search bar.
---
# 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.platform.softwareone.com/modules-and-features/chat/search-for-chat-messages.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.