Settings - Keep tab on disconnect doesn't work for SSH session

Settings - Keep tab on disconnect doesn't work for SSH session

avatar

Hi Support Team,

I have found that setting Keep tab open on disconnect doesn't work for ssh session type. No matter if i select it or not, if host i have connected is restarted or have connection issue, tab closes itself.

I have checked it on version 2026.2.18 but i think same was on previous versions.

Regards,
Marcin

All Comments (2)

avatar

Hi Marcin,

Thank you for reporting this.

I looked into it on my side and found that the Keep tab on disconnect button in the Actions ribbon does not work for SSH sessions. It changes appearance when you click it, but the change never reaches the running session, which is why it makes no difference whether you select it or not. We will report this to our development team for further investigation.

In the meantime, the setting does work for SSH from a different place. Go to File > Settings > Entry types, and on the General tab set Disconnect action to Keep tab open, then save. With that set, my SSH tab stayed open after the connection ended, retitled "Disconnected", and I could bring it back with Reconnect from the tab's right-click menu.

Could you try that and let me know whether it holds on your end? Your scenario is an unexpected drop (host reboot or network loss) rather than a clean logout, so I would like to confirm it behaves the same way for you.

Best regards,

Alexis Geller Peiro

avatar

Hi marwoz79,

You were right, and this turned out to be a real bug on our side rather than a
configuration issue. Thanks for reporting it.

Here's what was happening: RDM has historically stored the disconnect action in
two different places. SSH, Telnet, serial, and tunnel entries keep it with their
terminal settings, while RDP, VNC, and everything else keep it with the general
entry settings. Both appear in the interface as the same "Disconnect action"
field, so there's no way to tell them apart. The Keep tab on disconnect button
in the Actions ribbon was only ever writing to the second one—so on an SSH
session, the button would light up, but the running session was reading the other
value. The tab closed regardless of what the button showed.

That's also why the workaround Alexis gave you works: File > Settings > Entry
types > Disconnect action sets the global default, and that one is read by SSH
sessions.

We've fixed the underlying cause rather than just the button. In an upcoming
release:

- Keep tab on disconnect works on SSH, Telnet, serial, SSH tunnel, and port
forward sessions, and the button correctly reflects the entry's real setting.
- Telnet sessions honor the disconnect action at all. They were previously
always closing, whatever you set.
- The same fix applies on macOS, where the per-entry Disconnect action field had
the same problem, so even the workaround only half-worked there.
- Setting Disconnect action on a folder and leaving entries on Inherited now
behaves correctly when nothing in the folder chain overrides it.
- Linux, macOS, iOS, and Android now use the same global default as Windows, so
the Entry types setting applies consistently across platforms.

To answer Alexis's question directly: yes, this covers unexpected disconnections
— a host reboot, a dropped network, an SSH service restart. The tab stays open,
retitled "Disconnected", and you can bring the session back with Reconnect from
the right-click menu.

Until the fix ships, the Settings > Entry types approach is the reliable one,
and it does apply to unexpected drops.

Thanks again for flagging this—it was quietly affecting more than just SSH.

Regards

David Hervieux