> 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/putty.md).

# PuTTY

Configure PuTTY entries in Remote Desktop Manager, including session mode, protocol, host, port forwarding, post-login commands, and application options.

This article details the many settings and options available for ***PuTTY*** session entries in Remote Desktop Manager.

{% hint style="warning" %}
***PuTTY*** is a deprecated entry type. To create one, enable ***Show deprecated entries*** in the ***New entry*** window, as described in [Deprecated entries](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/deprecated-entries.md). Converting existing PuTTY entries to a terminal session type is recommended.
{% endhint %}

{% hint style="info" %}
PuTTY is a Windows application. In Remote Desktop Manager for macOS, PuTTY entries cannot be created or opened, but existing PuTTY entries remain editable so vaults shared with Windows users keep working.
{% endhint %}

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located. Click the browse button to select a folder, or click the add (<em><strong>+</strong></em>) button to create a new one.</td></tr><tr><td><strong>Display</strong></td><td><p>How the entry opens:</p><ul><li><strong>External</strong></li><li><strong>Embedded (tabbed)</strong></li><li><strong>Undocked</strong></li></ul><p>With <em><strong>External</strong></em> or <em><strong>Undocked</strong></em>, additional lists let you choose the monitor and the virtual desktop where the window opens.</p></td></tr><tr><td><strong>Host</strong></td><td>Where the host of the entry comes from. <em><strong>Host configured</strong></em> uses the <em><strong>Host</strong></em> entered in the <em><strong>General</strong></em> tab. <em><strong>Linked</strong></em> uses a host entry from the vault selected in the <em><strong>Vault</strong></em> list. <em><strong>Inherited</strong></em> uses the host of a parent folder.</td></tr><tr><td><strong>Credentials</strong></td><td>How the credentials of the entry are provided. Select a credential mode from the list. When the credentials do not come from the entry itself, the <em><strong>Username</strong></em> and <em><strong>Password</strong></em> of the <em><strong>General</strong></em> tab are disabled.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Mode</strong></td><td><p>How the PuTTY connection is configured:</p><ul><li><strong>Session</strong> — Open a session saved in PuTTY, identified by its name.</li><li><strong>Embedded session</strong> — Open a session saved in PuTTY, and store a copy of its settings in the entry when the entry is saved.</li><li><strong>Use these settings</strong> — Configure the connection with the settings of this entry.</li></ul></td></tr><tr><td><strong>Session</strong></td><td>With the <em><strong>Session</strong></em> and <em><strong>Embedded session</strong></em> modes, the name of the saved PuTTY session to open. Required in those modes. With the <em><strong>Use these settings</strong></em> mode, an optional saved PuTTY session whose settings are loaded before the settings of this entry.</td></tr><tr><td><strong>Protocol</strong></td><td><p>The connection protocol. Visible only with the <em><strong>Use these settings</strong></em> mode:</p><ul><li><strong>Default</strong></li><li><strong>SSH</strong></li><li><strong>Telnet</strong></li><li><strong>rLogin</strong></li><li><strong>RAW</strong></li><li><strong>Serial</strong></li></ul></td></tr><tr><td><strong>Host</strong></td><td>The host name or IP address of the remote computer, with its <em><strong>Port</strong></em> (default 22). Disabled when the host does not come from the entry itself. With the <em><strong>Use these settings</strong></em> mode, the host is required, unless it comes from a linked or inherited host, and the field is hidden when <em><strong>Protocol</strong></em> is set to <em><strong>Serial</strong></em>.</td></tr><tr><td><strong>Serial line</strong></td><td>The serial line to connect to, with its <em><strong>Speed</strong></em> (from 1 to 200000, default 9600). Visible only when <em><strong>Protocol</strong></em> is set to <em><strong>Serial</strong></em>.</td></tr><tr><td><strong>Username</strong></td><td>The username used to log in. With the <em><strong>Use these settings</strong></em> mode, hidden when <em><strong>Protocol</strong></em> is set to <em><strong>Serial</strong></em>.</td></tr><tr><td><strong>Password</strong></td><td>The password used to log in. With the <em><strong>Use these settings</strong></em> mode, hidden when <em><strong>Protocol</strong></em> is set to <em><strong>Serial</strong></em>. Unavailable when a policy disables password saving in vaults.</td></tr><tr><td><strong>Port forwarding</strong></td><td>The list of port forwarding rules, in the <code>L/R source-port [host:]dest-port</code> format. Type a rule, then click <em><strong>Add</strong></em>. Select a rule, then click <em><strong>Delete</strong></em> to remove it. Visible only with the <em><strong>Use these settings</strong></em> mode, when <em><strong>Protocol</strong></em> is not set to <em><strong>Serial</strong></em>.</td></tr><tr><td><strong>Show debug information (embedded)</strong></td><td>Show debug information in the session. Available only when the entry opens embedded.</td></tr></tbody></table>

### Post-login

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Automatic {ENTER} after command</strong></td><td>Send <kbd>Enter</kbd> after each command.</td></tr><tr><td><strong>Command 1</strong> to <strong>Command 5</strong></td><td>The commands to send once the session is open, in order. Click the <em><strong>Help</strong></em> button next to <em><strong>Command 1</strong></em> to open the typing macro help.</td></tr><tr><td><strong>More commands</strong></td><td>Additional commands sent after <em><strong>Command 5</strong></em>. Use a line for each command.</td></tr><tr><td><strong>Delay</strong></td><td>The delay between commands, in milliseconds (from 500 to 50000, default 500).</td></tr></tbody></table>

### Advanced

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Application</strong></td><td><p>The application used to open the session:</p><ul><li><strong>PuTTY</strong></li><li><strong>PLink</strong></li><li><strong>Default</strong></li><li><strong>KiTTY</strong></li></ul></td></tr><tr><td><strong>Portable mode</strong></td><td>Use KiTTY in portable mode. Available only when <em><strong>Application</strong></em> is set to <em><strong>KiTTY</strong></em>.</td></tr><tr><td><strong>Verbose</strong></td><td>Start PLink in verbose mode. Available only when <em><strong>Application</strong></em> is set to <em><strong>PLink</strong></em>.</td></tr><tr><td><strong>Internet protocol</strong></td><td><p>The IP version used for the connection:</p><ul><li><strong>Default</strong></li><li><strong>IPv4</strong></li><li><strong>IPv6</strong></li></ul></td></tr><tr><td><strong>Other parameters</strong></td><td>Additional command-line parameters passed to the application.</td></tr><tr><td><strong>Full screen (embedded mode only)</strong></td><td>Open the session in full screen. Available only when the entry opens embedded.</td></tr></tbody></table>

### See also

* [Putty embedded mode](https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/putty-embedded-mode.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/putty.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.
