# Editor

The editor controls within the PowerShell Universal admin console provide a rich editing experience for PowerShell users. You will be able to take advantage of IntelliSense, formatting and parser error support.&#x20;

## IntelliSense

![IntelliSense](https://3638551245-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M6jY7sXTmhiAIMGYw_m-887967055%2Fuploads%2FS3yEkXyGgnr1l5yGNmCn%2Fimage.png?alt=media\&token=9976d818-d4e8-496e-beab-19fd72a95cfd)

All editors within PowerShell Universal will provide IntelliSense. You should be able to complete commands, parameters, built-in variables, and paths.&#x20;

There are a couple of caveats with IntelliSense.&#x20;

**IntelliSense runs within the PowerShell Universal server**

It does not rely on a configured environment to function. It runs within the PowerShell server process so will be using the current version of PowerShell 7 referenced by the server.&#x20;

**Universal Modules are Available**

Modules provided with PowerShell Universal are automatically included. You will see IntelliSense for the following modules.&#x20;

* Universal
* UniversalDashboard
* UniversalDashboard.Charts
* UniversalDashboard.CodeEditor
* UniversalDashboard.Editor
* UniversalDashboard.Map
* UniversalDashboard.Style

**Modules included in PSModulePath are Available**

Any module installed into a PSModulePath will be available in IntelliSense.&#x20;

**Live Variables are Not Supported**

You will have access to built-in variables such as `ConfirmPreference` and `Host` but will not see variables specific to PowerShell Universal. &#x20;

## Formatting

![Formatting](https://blog.ironmansoftware.com/images/formatting.gif)

You can use the `Invoke-Formatter` command of `PSScriptAnalyzer` within your scripts. You will need to install `PSScriptAnalyzer` to your PSModulePath in order to use this functionality. You can format by right clicking within the editor and selecting Format or by pressing F8.&#x20;

## Syntax Errors

Syntax errors will be shown as red squiggles within the editor. Hovering over them will provide information about why the syntax error is present.&#x20;

![Syntax Errors](https://3638551245-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M6jY7sXTmhiAIMGYw_m-887967055%2Fuploads%2F5LjWXBJrhBToBd0hBnGu%2Fimage.png?alt=media\&token=f93655a1-2bc6-4940-a641-e99f7d22d0ce)


---

# Agent Instructions: 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:

```
GET https://docs.powershelluniversal.com/master-1/development/editor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
