> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/getting-started/frequently-asked-questions/endpoint-agent.md).

# Endpoint Agent

## What is the function of the endpoint agent?

The agent collects advanced telemetry from your endpoints to enable cyber threat detection and facilitate incident response. It provides complete visibility into endpoints, recording forensic-like evidence such as network connections, logins, processes, user actions, downloaded files, and much more. The agent can also be used to execute interactive threat-hunting queries and perform various incident response actions.

## What Operating Systems are Supported?

Check Agent Deployment Prerequisites /endpoint-agent/prerequisites.md

## How can we verify if an agent is online and reporting?

In the Analyst Console, under the endpoint menu, two dashboards are available:

* **Inventory of Agents**: conducts regular checks to confirm if agents are live and reporting.

## How do you remove an agent from the Console?

You must uninstall the agent directly from the endpoint.

## Can I run EDR and the visibility agent at the same time?

Yes, they can co-exist on the same endpoint. Just ensure that your EDR is not blocking the installation of the agent.


---

# 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.threatdefence.com/getting-started/frequently-asked-questions/endpoint-agent.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.