> 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/knowledge-base-articles/entry-settings/common-settings/jump.md).

# Jump

Open a session through a jump host with Devolutions Agent, and set an RDP entry as a jump host, in the Jump section of Remote Desktop Manager.

The ***Jump*** section defines the jump host through which Remote Desktop Manager opens the session: Remote Desktop Manager first opens an RDP session to the jump host, and Devolutions Agent on the jump host then opens the session to the destination. For RDP entries, the section also sets the entry as a jump host. For the requirements and the setup of the jump host, see [Jump host](https://docs.devolutions.net/agent/jump-host).

Available for session entries and folders. In the entry properties, select ***Connection*** – ***Jump***. By default, the section is hidden in the simplified view of the properties; select ***Show all properties*** to display it.

### Jump connection

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Connect using Jump</strong></em></td><td><p>Shows the current jump configuration. Select the link to open the <em><strong>Jump</strong></em> window and choose how the jump host is found:</p><ul><li><em><strong>Off</strong></em>: no jump host. This is the default value.</li><li><em><strong>Inherited</strong></em>: the jump configuration of the parent folder.</li><li><em><strong>Session</strong></em>: an RDP entry. Select the vault in the <em><strong>Vault</strong></em> list, then select the entry in the <em><strong>Session</strong></em> field. Select <em><strong>Filter Jump Host only</strong></em> to list only the entries set as jump hosts. Selecting the user vault from an entry in a shared vault finds, for each user, the RDP entry of their user vault whose name matches the name you enter.</li></ul></td></tr></tbody></table>

Jumps are not supported in the user vault: for entries of the user vault, the section shows ***Not supported in user vault***. The setting is disabled when ***Disable Devolutions Agent jump*** is selected in [***Administration*** – ***System settings*** – ***Application***](https://docs.devolutions.net/rdm/ribbon-menu-bar/administration/system-settings/application.md).

### Jump host

Shown for RDP entries.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Is jump host</strong></em></td><td>Sets the entry as a jump host. The other settings of the group are enabled when this option is selected.</td></tr><tr><td><em><strong>Agent connection timeout</strong></em></td><td>Number of seconds to wait for Devolutions Agent on the jump host to answer, from -1 to 180.</td></tr><tr><td><em><strong>Force new jump host session for every jump</strong></em></td><td>Opens a new RDP session to the jump host for every jump instead of reusing an open one. The jump host must allow several sessions per user.</td></tr><tr><td><em><strong>Show wait for Devolutions Agent dialog</strong></em></td><td>Shows a window while Remote Desktop Manager waits for Devolutions Agent on the jump host.</td></tr></tbody></table>

To skip a jump host when the computer is on the local network, use the ***Jump host*** provider of the [VPN/tunnel/gateway](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/vpn-tunnel-gateway.md) section instead. See [Automatically detect and bypass jump host for direct connections in local network](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/automatically-detect-and-bypass-jump-host-for-direct-connections-in-local-network.md).


---

# 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/knowledge-base-articles/entry-settings/common-settings/jump.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.
