> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/data-flows/agents/agents-view.md).

# Agents View

Monitor the health of all your distributed agents from a central overview in the Connectware Admin UI.

The **Agents View** allows you to monitor the name, version, status, and hostname of your agents. The list shows both online and offline agents.

* To open the **Agents View**, click **System** > **System Status** and click the **Agents** tab.

<figure><img src="https://2858848828-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F38tgcn74JQcOsNlglPZq%2Fuploads%2Fgit-blob-b79a0392f28540dabca8dcfa0369e8b4c9c5d33d%2Fagents.png?alt=media" alt=""><figcaption><p>Agents View</p></figcaption></figure>

Here is an overview of the functions of the **Agents View**.

**Name**

* The unique identifier of the agent.

**Version**

* The current Connectware version number of the installed agent.

**Status**

* The current operational state of the agent: online or offline.

**Hostname**

* The network hostname or address where the agent is running.

**Delete**

* Removes offline agents from the list. Select one or more offline agents and click **Delete** on the toolbar. Online agents cannot be deleted.


---

# 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.cybus.io/2-6-1/data-flows/agents/agents-view.md?ask=<question>&goal=<user_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.
