> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/manual-installation/macos-validation.md).

# macOS Installation Validation

Verify We360.ai MyZen agent installation on macOS — check running status and validate endpoint monitoring is active.

## Check Running Status

### Standard Mode

> **Note:** The app will not automatically start until the user logs out and logs back in.

1. Open **Activity Monitor**.
2. Search for `MyZenV2`.
3. Verify the **User** matches the current user.
4. If the processed are listed, the agent is running.

### Stealth Mode

> **Note:** The app will not automatically start until a lock/unlock cycle is performed. A restart is recommended.

1. Open **Activity Monitor**.
2. Search for `zs`. Also search for `svcmonitor`
3. Verify the **User** matches the current user.
4. If the processes are listed, the agent is running.

## Check Application Version

The **installer version** is the authoritative version indicator. The version displayed in the MyZen app window may differ. Check the Download Apps page in the portal for the latest version.

### Standard Mode

Read the version file:

```bash
cat /Applications/MyZenV2.app/Contents/MacOS/version.txt
```

Alternatively: right-click `MyZenV2.app` in Finder, select **Show Package Contents**, and navigate to `Contents/MacOS/version.txt`.

### Stealth Mode

Read the version file:

```bash
cat /usr/local/zs/zs.app/Contents/MacOS/version.txt
```

> **Tip:** Compare the installed version against the latest version shown on the **Download Apps** page in the We360.ai portal.


---

# 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.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/manual-installation/macos-validation.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.