> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/aikido-device-protection/miscellaneous-aikido-endpoint/endpoint-information-for-support.md).

# Report a Problem / Device Protection Support

When contacting Aikido Support about Aikido Device Protection, please include the information below. This helps us troubleshoot issues faster and avoid unnecessary back and forth.

### Report a problem (recommended)

The easiest way to send diagnostics is directly from the app. Aikido will automatically attach agent diagnostics data (never personal data, deleted after debugging).

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-33b19b39e789c661968a42d497da740f93d7e244%2FScreenshot%202026-08-18%20at%2014.22.41.png?alt=media" alt=""><figcaption></figcaption></figure>

1. Open the Aikido Endpoint Protection app
2. Go to the **Help** tab
3. Click **Report A Problem**
4. Add any additional notes about the issue (optional)
5. Leave your email if you'd like us to follow up (optional)
6. Click **Submit Report**

### Run the diagnostics command (fallback)

If the app is not accessible, run this command and attach the diagnostics logs. We only keep this data for as long as we need it to fix the problem.

{% tabs %}
{% tab title="macOS" %}
{% code overflow="wrap" %}

```bash
sudo /Applications/Aikido\ Endpoint\ Protection.app/Contents/Resources/scripts/submit_diagnostics
```

{% endcode %}
{% endtab %}

{% tab title="Windows" %}
{% code overflow="wrap" %}

```powershell
& "C:\Program Files\AikidoSecurity\EndpointProtection\scripts\SubmitDiagnostics.ps1"
```

{% endcode %}
{% endtab %}

{% tab title="Linux" %}
{% code overflow="wrap" %}

```bash
sudo aikidoctl diagnostics
```

{% endcode %}
{% endtab %}
{% endtabs %}

### Find the diagnostics zip if the upload fails

If the report or the diagnostics command can't reach Aikido, the zip is still saved on the device. Attach it to your email or support ticket manually.

| Platform | Location                                                                                                |
| -------- | ------------------------------------------------------------------------------------------------------- |
| macOS    | `/Library/Logs/AikidoSecurity/EndpointProtection/aikido-endpoint-protection-logs-<timestamp>.zip`       |
| Windows  | `C:\ProgramData\AikidoSecurity\EndpointProtection\logs\aikido-endpoint-protection-logs-<timestamp>.zip` |
| Linux    | `/var/log/aikidosecurity/endpoint-protection/aikido-endpoint-protection-logs-<timestamp>.zip`           |


---

# 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://help.aikido.dev/aikido-device-protection/miscellaneous-aikido-endpoint/endpoint-information-for-support.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.
