FusionTermIdle timeout and reconnect
Open sessions nobody is using are a security risk, so FusionTerm can close them after a while without input. Set your account-wide defaults in Settings → Idle timeout & reconnect.
Windows (RDP) sessions
| Setting | Default |
|---|---|
| Disconnect after inactivity | 10 minutes |
| Warn before disconnecting | 60 seconds before |
| Retry a failed reconnect | up to 2 times |
"Inactive" means no keyboard or mouse input in that tab. Screen changes and network traffic don't count, and FusionTerm never records which keys you press.
Retries wait a little longer each time and only happen after network problems — a wrong password is never retried.
SSH sessions
| Setting | Default |
|---|---|
| Disconnect after inactivity | Never |
| Warn before disconnecting | 60 seconds before |
If you set a timeout, tick Keep the session open while the terminal is showing output so a tail -f or a running deployment isn't cut off. Sessions using tmux keep their programs running after a disconnect anyway.
The warning
Before disconnecting, the tab shows Still there? with a countdown. Click Stay connected, or just type or move the mouse in it.
After a disconnect
Press R on the tab (or click Reconnect) to connect again. Press Esc to cancel a reconnect that's in progress.
Per server
Override the default for one server in its settings: Advanced → Disconnect when inactive (Use default, Never, or a time).