> 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/keep-tabs-open.md).

# Keep tabs open

Keep a Remote Desktop Manager tab open after disconnecting to restart a remote device or quickly resume interrupted work later.

Remote Desktop Manager offers you the possibility of keeping a tab open even when disconnected, allowing you to restart a remote device or simply keep your worksapce set up to quickly resume after a work interruption.

### Workflow

Your session must be running in embedded mode. Once your session is open, you will notice the ***Keep tab on disconnect*** option in the ***Settings*** section of your ***Actions*** tab.

Enable the ***Keep tab on disconnect*** to be able to perform a logoff or restart while keeping the tab present. A panel will replace the content of the session.

This panel offers multiple actions:

* Close: You changed your mind and want to close the tab.
* Connect: Connect the session.
* Connect When Available: Pings the host until it becomes available, then connects the session.

If you wish to have the option enabled by default, edit your session and set the ***Keep tab page opened on disconnect*** option in ***Files - Options - Types*** to ***Yes***.


---

# 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/keep-tabs-open.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.