# Debug Mode

The debugger can be enabled via URL commands if needed in public facing applications with a combination of two url keys:

* `debugMode:boolean` - Control to turn the debugger on/off
* `debugPassword:string` - The secure password to use to enable the debugger

Please see the [configuration](/essentials/configuration.md#debug-mode) on how to add the default debug mode and debug password.  If your debug password is validated and you turn on debug mode a secured cookie will be stored for you and you will be able to visualize the debugger.  Once you turn it off, then it will remove this cookie for you.

```
https://myapp.com/cbdebugger?debugmode=true&debugpass=mys3cret3key
```

{% hint style="warning" %}
Please note that you can also add a `cbSecurity` rule if needed and add further security, which we recommend.
{% endhint %}


---

# 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://cbdebugger.ortusbooks.com/advanced/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.