> For the complete documentation index, see [llms.txt](https://burkeholland.gitbook.io/vs-code-can-do-that/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://burkeholland.gitbook.io/vs-code-can-do-that/master/exercise-4-debugging/before-you-start.md).

# Before you start

This is the point at which we begin to turn the dial on VS Code from "Editor" to "IDE". 

This is also the most dense part of the workshop. Debugging configurations can be tedious and tricky. If you get frustrated, don't feel bad. You're not alone. Work your way through these exercises and I promise that you will understand far more than most people about VS Code's debugging abilities.

Open the "exercise-4-debugging" folder. It will tell you that there is a workspace file and ask if you want to open it. Select "Yes".

![](/files/-Lm0xIUn8MTe3GkYW_rW)

There are 4 projects in this folder. You will work through each one. As you do, be aware of which project you are working with. It's easy to get confused during this exercise because there are 4 projects within which to work.


---

# 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://burkeholland.gitbook.io/vs-code-can-do-that/master/exercise-4-debugging/before-you-start.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.