> For the complete documentation index, see [llms.txt](https://windows.help.formit.autodesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://windows.help.formit.autodesk.com/plugins/how-to-develop-plugins/advanced-development/debugging.md).

# Debugging

Debugging a FormIt plugin requires different procedures depending on the engine you are debugging. (For more information on engines check the [previous section](/plugins/how-to-develop-plugins/advanced-development/client-side-vs-web-side-engines.md))

### **Client-Side (FormIt) Debugging**

To debug in FormIt-side code, which applies to both toolbar- and panel-based plugins, you can add a line in the code to pop the desktop application's built-in JS debugger:

`debugger`

![](/files/CDu1LvrNmePB4Oh8BYsz)

### **Web-Side (HTML) Debugging**

Panel-based FormIt plugins offer HTML-based UI debugging, since the panels are fundamentally HTML websites with styling and scripts.

To debug HTML-side code for plugins built into a panel, including scripts and styling:

* **FormIt for Windows 2021.1 and newer**
  * Right-click on the plugin HTML page and click "Debug" to display the application's built-in HTML debugger.

![](/files/NCIMzLjmUW7dteJyXCNw)

* **FormIt for Web**
  * Use shortcut F12, or Ctrl + Shift+ I, to pull up the browser's HTML debugger.

![](/files/adkoJVdOcChpB1C4hvaF)


---

# 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://windows.help.formit.autodesk.com/plugins/how-to-develop-plugins/advanced-development/debugging.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.