> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/enable-debug-webview-for-embedded-safari-in-remote-desktop-manager-macos.md).

# Enable debug WebView for embedded Safari in Remote Desktop Manager macOS

Enable Safari debug WebView in Remote Desktop Manager macOS to inspect embedded web pages and troubleshoot JavaScript issues directly.

Debugging a web page rendered within a WebView can be an invaluable exercise, especially when it comes to meticulously examining its layout, diving into the intricacies of its design, or addressing confusing JavaScript complications. Follow these steps to enable debug WebView for embedded Safari in Remote Desktop Manager macOS.

### Enable Safari Developer Tools

1. Open ***Safari***.
2. Select ***Safari – Preferences***.
3. Go to ***Advanced***.
4. Check ***Show Develop menu in menu bar***. The ***Safari Developer Tools*** are now available from the ***Develop menu in the menu bar***.

### Enable debug WebView for embedded Safari

1. Close Remote Desktop Manager.
2. From the Terminal (Terminal.app), run the following command: `defaults write com.devolutions.remotedesktopmanager WebKitDeveloperExtras -bool true`
3. Open Remote Desktop Manager and navigate to the website in the embedded browser.
4. Back in Safari, go to ***Develop – Name of your local machine***. The website is now listed under the local machine.
5. Click the website name to open the ***Safari Developer tools***.


---

# 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.devolutions.net/rdm/knowledge-base/how-to-articles/enable-debug-webview-for-embedded-safari-in-remote-desktop-manager-macos.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.