> 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-agent/5.0/traps-agent-5.0-for-mac/use-the-traps-agent-for-mac.md).

# Use the Traps Agent for Mac

See the following to manage the Traps agent for Mac:

* Open the Traps application.

  Use one of the following methods:

  * Browse to the Traps application in Finder.
  * If you enabled access to the Traps console, click the Traps icon (

    ![icon-traps.png](/files/MZMVdW6hv3qExJAGNPEq)

    ) in the menu bar, and select **Open Console**.
* View status information about the Traps agent:

  ![traps-console-mac-status.png](/files/xDTqwHH6XuPYbl2Etqys)

  * **Version**—Displays the Traps agent version.
  * **Protection**—Displays the active policies in bold.
  * **Connection**—Displays the connection status and, if connected, includes the server to which the agent is connected.
  * **Last Check-in**—Displays the local time on the endpoint of the last check-in with the server.
* Manually connect to the server.

  The Traps agent periodically communicates with the server to send status information and retrieve the latest security policy. The Traps agent performs this operation transparently at regular intervals so it is not typically necessary to connect to the server manually. If your **Connection** status is **Not Connected**, you can manually retry your connection. This option is available if you do not want to wait for the automated communication interval to begin.

  To initiate a manual check-in with the server: On the home page of the Traps console, click **Check In Now**. If the agent successfully establishes a connection with the server, the **Connection** status changes to indicated the service to which the agent is connected.
* View and send logs.
  * Send logs—Click **Send Support File** to collect Traps logs. The logs can help you further analyze any recent security events and Traps issues that you encountered.
  * View logs—Click **Open Log File** to view logs generated by the Traps agent. The logs display in your default text editor in chronological order with the most recent logs at the bottom.
* View recent security events that occurred on your endpoint.

  ![traps-console-mac-events.png](/files/dtQ223h8aTci5laUq9H9)

  For each event, the Traps console displays the local **Time** an event occurred, the name of the **Process** that exhibited malicious behavior, the **Module** that triggered the event, and the mode specified for the type of event (Termination or Notification).
* View protected processes on the Mac endpoint.

  ![traps-console-mac-protection.png](/files/kD57XBFmbmNr4V3uVHfU)

  The **Protection** tab of the Traps console displays all running processes in which Traps is injected to prevent malicious execution or behavior. The Traps console also indicates the process ID (PID) associated with each process.
* Configure proxy communication.

  Traps can communicate with the Traps management service using the system proxy server that you define for the endpoint. For information on [How to Enter Proxy Settings](https://support.apple.com/guide/mac-help/enter-proxy-server-settings-on-mac-mchlp2591/mac), see the documentation for your Mac operating system version.


---

# 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-xdr-agent/5.0/traps-agent-5.0-for-mac/use-the-traps-agent-for-mac.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.