# Run helmut4 client in debug mode

## Disclaimer

{% hint style="danger" %}
**Important**\
The *<mark style="background-color:red;">connection speed & response will be significant slower</mark>*, as everything will be logged
{% endhint %}

If you need to debug the local helmut4 client on windows or macintosh clients you can do this with the following commands.

*Please keep in mind that this should only be used for debugging purpose not for daily use!*

## Windows

Open a command prompt (***with admin privileges***) and execute this command:

```batch
"C:\Program Files\MoovIT GmbH\Helmut4\jre\bin\java.exe" -jar "C:\Program Files\MoovIT GmbH\Helmut4\Helmut4.exe" --logging.level.org=DEBUG
```

## Macintosh

Open a terminal window and execute the following two commands (***with admin privileges***)

```bash
sudo chmod 777 /Applications/Helmut4.app/Contents/Resources/jre/bin/java
/Applications/Helmut4.app/Contents/Resources/jre/bin/java -jar /Applications/Helmut4.app/Contents/Resources/HelmutClient.jar --logging.level.org=DEBUG
```


---

# Agent Instructions: 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:

```
GET https://docs.helmut.de/helmut4-releases/v4.7.1/support/debug-or-log-collection/helmut4-client/run-helmut4-client-in-debug-mode.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.