> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/reference/servoy-developer/debugger/debug-explorer.md).
# Debug Explorer
The Debug Explorer or Perspective comes in handy when trying trying to step through code to resolve bugs and figuring out the flow of business logic.
To jump into the Debug perspective we can start by setting up a breakpoint. By double clicking on the line number where we want the debugger to start inspection. Once we do that and the client reaches that point in the code, the "Perspective Switch" dialog should appear asking if we want to switch.
Selecting "Switch" will bring us over to the debug perspective.
The default view of the Debug Perspective
Once we've launched the perspective you will see that the line which the debugger has stopped on will be highlighted. From here you can step line by line and debug the function or activity.
The Debug Panel shows the entire thread of code up to the highlight point. You can click on a line to switch to different JavaScript files. This helps keep track of your place if we are debugging in a deeply nested function.
Within the debug perspective we can also use our mouse to hover over variables or objects within our code. It will allow you ti view the current values or properties as they are in that point in the execution.
---
# 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.servoy.com/reference/servoy-developer/debugger/debug-explorer.md?ask=&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.
