> 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/development.md). # Development - [Debugging Scripts](https://docs.devolutions.net/powershell-universal/development/debugging-scripts.md): Debug PowerShell Universal scripts using Wait-Debugger, the integrated debugger console, or Visual Studio Code across jobs, apps, and APIs. - [Editor](https://docs.devolutions.net/powershell-universal/development/editor.md): Learn how the PowerShell Universal editor provides IntelliSense, code formatting, syntax error highlighting, and PSScriptAnalyzer integration. - [Hangfire](https://docs.devolutions.net/powershell-universal/development/hangfire.md): View the Hangfire job execution dashboard in PowerShell Universal to diagnose scheduled jobs, running jobs, and failures affecting automation execution. - [Logging](https://docs.devolutions.net/powershell-universal/development/logging.md): Configure PowerShell Universal logging with Serilog, covering system and user log targets, Write-PSULog, log levels, and streaming logs to an ELK stack. - [Profiling](https://docs.devolutions.net/powershell-universal/development/profiling.md): Enable the PowerShell Universal performance profiler to diagnose slow dashboards, APIs, and jobs using Measure-PSUBlock and the profiler results dashboard. - [Visual Studio Code Extension](https://docs.devolutions.net/powershell-universal/development/visual-studio-code-extension.md): Manage PowerShell Universal APIs, apps, and scripts from Visual Studio Code using the official extension, including connections and the virtual file system. --- # 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/development.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.