> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xpanse/active-response/engines.md).

# Engines

Engines are installed in a remote network and allow communication between the remote network and the Cortex Xpanse tenant. You can run scripts and integration commands on an engine. It is possible to install a single engine or multiple engines.

You can install multiple engines on the same machine (Shell installation only) which is useful in a dev-prod environment where you do not want to have numerous engines in different environments, and to manage those machines.

{% hint style="info" %}

### Note

You cannot share a multiple engine installation with a single engine installation.
{% endhint %}

You can [install engines](/cortex-xpanse/active-response/engines/engine-installation.md) on Linux and Windows machines. After installing the engine, you can [configure](/cortex-xpanse/active-response/engines/configure-engines.md)and [manage](/cortex-xpanse/active-response/engines/manage-engines.md)engines, including setting a web proxy, adding and removing engines, configuring the number of worker, etc.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xpanse/active-response/engines.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.