> 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/remote-desktop-manager-powershell/powershell-scripting/custom-powershell-commands.md).
# Custom PowerShell commands
Run a Custom PowerShell command on entries selected in the Remote Desktop Manager navigation pane to edit multiple sessions at once.
Custom Powershell command will act on currently selected entries in your ***navigation pane***. Use click and Ctrl+click to build up your list, or an [advanced search](https://docs.devolutions.net/rdm/ribbon-menu-bar/view/search/advanced-search) to select a great number of entries. After your selection is done, the command is available using either:
1. Right-click the entry or entries, then select ***Edit – Edit (special actions)***.
2. Once there, select ***Custom PowerShell command***.
3. A window appears in which you can write a snippet of code. Note that is the last line must always be `$RDM.Save();`.
4. Upon pressing ***Ok***, a summary dialog appears to indicate success or failure.
---
# 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/remote-desktop-manager-powershell/powershell-scripting/custom-powershell-commands.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.