> For the complete documentation index, see [llms.txt](https://docs.polarity.io/integrations/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polarity.io/integrations/build-an-integration/debugging/web-inspector.md).

# Web Inspector

Polarity includes a remote web debugger which can be used to run the Chrome web inspector on each of the Polarity application windows.  The inspector allows you to view any client side javascript errors, network requests, and the DOM structure of the page.  By default the inspector is disabled.  To turn it on first navigate to your Polarity folder.

{% tabs %}
{% tab title="Windows" %}

```
%localappdata%\Polarity\PolarityX
```

{% endtab %}

{% tab title="macOS" %}

```
~/Library/Preferences/Polarity/PolarityX
```

{% endtab %}

{% tab title="Linux" %}

```
~/.config/Polarity/PolarityX
```

{% endtab %}
{% endtabs %}

If it doesn't already exist, you will need to create a file called `config.json` in this folder.

{% hint style="info" %}
When creating the file, particularly on Windows, ensure the file does not have a hidden extension (e.g., a hidden `.txt` extension).
{% endhint %}

After creating the file, open it up and add the following.

```javascript
{
   "webDebugger": true,	
   "webDebuggerPort": 9999
}
```

Restart the Polarity client, open up the Chrome web browser and navigate to `http://localhost:9999`

You will be presented with three different "Inspectable Pages" you can connect to with the inspector.  Click on the page called **Polarity - Notifications**. This will connect the Chrome Inspector to the Overlay Window.

For more information on the Chrome web inspector please see <https://developers.google.com/web/tools/chrome-devtools/>


---

# 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://docs.polarity.io/integrations/build-an-integration/debugging/web-inspector.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.