> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/fr/commandes-powershell/debug-psudashboard.md).

# Debug-PSUDashboard

Debug-PSUDashboard est une applet de commande utilitaire qui connecte le débogueur de l'extension VS Code PowerShell Universal aux terminaux exécutés dans un tableau de bord.

### Résumé

Fournit une fonction utilitaire pour déboguer des scripts exécutant PowerShell Universal Dashboard.

### Syntaxe

```powershell
Debug-PSUDashboard [<CommonParameters>]
```

### Description

Fournit une fonction utilitaire pour déboguer des scripts exécutant PowerShell Universal Dashboard. Cette applet de commande s'intègre à l'extension VS Code PowerShell Universal pour connecter automatiquement le débogueur aux terminaux exécutés dans UD.

### Paramètres

### Sorties

### Exemples

#### Exemple 1

```powershell
New-UDElement -Tag div -Endpoint {
    Debug-PSUDashboard
}
```

Crée un élément qui invoque l'applet de commande Debug-PSUDashboard.


---

# 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.devolutions.net/powershell-universal/fr/commandes-powershell/debug-psudashboard.md?ask=<question>&goal=<user_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.