> 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-xdr/protect-your-endpoints/install-and-manage-endpoints/set-up-endpoint-protection/change-an-agent-type.md).

# Change an agent type

You can change the agent type of installed Cortex XDR agents from Targeted to Standard. Standard is the full Cortex XDR agent, so the change adds all Cortex XDR capabilities to the endpoint, such as real-time event collection and active prevention. You don't need to reinstall the agent, and you can change the agent type for multiple endpoints at a time.

To change the agent type, you need a [Cortex XDR ONE license](https://cortex-docs.paloaltonetworks.com/cortex-xdr/learn-about-cortex-xdr/cortex-xdr-license-plan.md#cortex-xdr-license-variants).

{% hint style="info" %}
**Note**

* After the change, the agent uses the settings on the **Standard** tab of the profiles in its policy, instead of the **Targeted** tab. Before you change the agent type, review the Standard tab of each profile in the policy, so the endpoint gets the protection and settings you expect.
* The **change agent type** action is only available when switching from a Targeted agent type to Standard. Switching from a Standard agent type to Targeted, or switching to or from a Cloud Optimized agent requires uninstalling the existing agent and deploying the new agent type using a fresh installer.
* Before you change the agent type, make sure the agent version is 9.4 or later. To change an AES standalone agent on version 9.3, uninstall it and then install a Targeted agent on version 9.4 or later.
  {% endhint %}

### Change agent type from Targeted to Standard (full XDR)

#### Change the agent type from All Endpoints

1. Go to **Inventory** → **Endpoints** → **All Endpoints**.
2. Select one or more endpoints with the Targeted agent type, right-click, and select **Endpoint Control** → **Change agent type**.
3. Review the summary. It shows how many endpoints will change from Targeted to Standard, and how many can't be changed because of an incompatible agent type. Endpoints that can't be changed are skipped.
4. Click **Change**.

#### Change the agent type from the Action Center

1. Go to **Investigation & Response** → **Response** → **Action Center**, and click **New Action**.
2. Select **Change agent type**.
3. Select the target endpoints. Only endpoints that are eligible for the action are listed.
4. Review the action summary and confirm.

#### Track the change

To track the change, go to the **Action Center** and find the **Change agent type** action.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xdr/protect-your-endpoints/install-and-manage-endpoints/set-up-endpoint-protection/change-an-agent-type.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.
