> 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/rdm/knowledge-base/how-to-articles/use-custom-windows-terminal-over-console-host-in-powershell-session-entries.md).

# Use custom Windows terminal over console host in PowerShell session entries

Configure PowerShell session entries in Remote Desktop Manager to launch a custom Windows Terminal profile instead of Console host.

***PowerShell (local)*** and ***PowerShell (remote)*** entries can be configured to use Console host or Windows Terminal (with or without custom profile).

To use Windows Terminal over Console host, head over to a PowerShell session entry's ***General*** settings, and select ***Windows Terminal*** from the ***Application*** dropdown list located in the ***Terminal*** tab.

Then, click on ***Add***/***Update*** to effectuate the changes, and select ***Open session*** to launch a standard Windows Terminal.

### Using a custom Windows Terminal

Remote Desktop Manager also allows for a customized Windows Terminal using a separate ***Windows Terminal*** entry linked to a ***PowerShell (local)*** or ***PowerShell (remote)*** entry. Here is how to proceed:

1. Create a new ***Windows Terminal*** entry (***New entry*** – ***Session*** – ***Windows Terminal***).
2. In the ***Profile*** tab, customize the terminal's ***General*** settings, ***Appearance***, and ***Advanced*** parameters before clicking on ***Add***/***Update***.
3. In a separate ***PowerShell (local)*** or ***PowerShell (remote)*** entry, choose the newly created ***Windows Terminal*** entry from the ***Entry*** dropdown list.
4. Click on ***Add***/***Update*** to effectuate the changes, and select ***Open session*** to launch the custom Windows Terminal.


---

# 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/rdm/knowledge-base/how-to-articles/use-custom-windows-terminal-over-console-host-in-powershell-session-entries.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.