> For the complete documentation index, see [llms.txt](https://docs.osmos.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.osmos.io/osmos-chat.md).
# Osmos Chat
No more wrangling complex queries or digging through endless documentation – with Osmos Chat, everything you need is at your fingertips in a familiar chat box interface. Whether you're monitoring pipeline activity, checking uploader health, or seeking assistance with Osmos tasks, our natural language queries make it a breeze.
Engage with Osmos Chat to ask questions, search documentation, provide information, and conquer various Osmos challenges effortlessly. From querying pipeline stats to troubleshooting errors, Osmos Chat has you covered.
Users can view data, download, filter, and add/remove columns from the table. Users can also drill back to the originating source such as the pipeline, uploader, or connector.
Here are some examples to get you started.
* How many pipelines ran this month?
* Show me a list of Uploader jobs from the last week
* How do I combine two columns?
* List pipelines with errors since 4/1/24. Display name, records successful, skipped, failed.
*If you are hungry, you can always ask for a delicious pizza recipe!* 🍕
---
# 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.osmos.io/osmos-chat.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.