> 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/de/plattform/plugins.md).

# Plugins

Aktivieren und konfigurieren Sie optionale Plugins in PowerShell Universal über appsettings.json oder Umgebungsvariablen, um die Plattform zu erweitern.

Plugins sind Funktionen, die nicht standardmäßig aktiviert sind. Eine öffentlich verfügbare Plugin-API wird derzeit entwickelt und mit einer zukünftigen Version von PowerShell Universal veröffentlicht. Nachfolgend finden Sie eine Liste der Plugins, die mit PowerShell Universal v4.2 und später ausgeliefert werden.

## Plugins aktivieren

Plugins werden in `appsettings.json` oder über Umgebungsvariablen aktiviert. Informationen dazu, wo diese Optionen konfiguriert werden, finden Sie unter [App-Einstellungen ](/powershell-universal/de/config/settings.md). Alle an der Konfiguration vorgenommenen Änderungen erfordern einen Neustart des PowerShell Universal-Dienstes.

```json
{
    "Plugins": [
        "SQL",
        "PowerShellUniversal.Language.CSharp"
    ]
}
```

##


---

# 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/de/plattform/plugins.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.