> For the complete documentation index, see [llms.txt](https://docs.yellowant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yellowant.com/managing-dashboard/console.md).

# Console

The console is the native iterface that YellowANt provides for people who want to use it for the following purposes:

1. Use it as the command center: In case you are not on any chat platform like Slack and Microsoft Teams, you can still use YellowAnt from this console. You can command apps and execute workflows directly from here.
2. Use it as logs: No matter which chat application you are using, everything you execute and use will be logged in the console as well. You can always go here and segregate a specific application to see what has been executed for that application. &#x20;

![](/files/-LC9THtO4udgHLFmFZBR)

*YellowAnt Console is useful as a standalone web interface and even a logging mechanism.*


---

# 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.yellowant.com/managing-dashboard/console.md?ask=<question>&goal=<endgoal>
```

`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.
