If your Terminal, Remote Viewer, or Process Explorer session disconnects after being idle or when the tab is in the background, you’re likely experiencing a browser-related issue, not a problem with your device or workspace. This guide explains why it happens and how to fix it.
Why Does This Happen?
Modern browsers (especially Google Chrome) try to save memory and battery by limiting activity in tabs that aren’t currently visible. When a Level tab is running in the background, Chrome may:
Pause or slow down background activity
Temporarily suspend network connections
Put the tab into a low-power state
Disconnect live sessions
Because remote features like Terminal and Remote Viewer rely on a continuous live connection, this can cause your session to time out. This behavior has become more common due to recent Chrome updates.
How to Fix It
In most cases, adjusting a few browser settings will resolve the issue.
Start by opening Chrome’s Performance settings by visiting chrome://settings/performance. This will work on all chromium based browsers, though Firefox/Safari might be different.
If Memory Saver is enabled, instead of turning it off entirely, we recommend adding your Level site to the “Always keep these sites active” list. Click Add and enter your Level site’s URL. You may also want to add any additional Level domains your team uses. This allows Chrome to keep your remote sessions active without increasing overall memory usage.
If you prefer, you can turn off Memory Saver completely, but keep in mind this may increase memory usage, especially on lower-end devices or computers with limited RAM.
While you're on the Performance settings page, also check whether Energy Saver is enabled. If so, turn it off, as it can limit background activity and interrupt live remote sessions.
If you regularly run long Terminal or Remote Viewer sessions, keeping the tab visible and active can also help prevent timeouts.
Turning off Memory Saver or Energy Saver may increase memory and power usage, particularly on devices with limited RAM or processing power. If you're using a lower-spec device, adding Level to the exclusions list is usually the better option.
Summary
If your session disconnects even while the tab is active, disconnects immediately, or behaves the same way across multiple browsers, please reach out to support. When you do, include your browser version, operating system, and a brief description of what you’re experiencing so we can investigate further.
Remote features require a steady, live connection to function properly. When a browser limits background activity, sessions may time out. Disabling Chrome’s Memory Saver and Energy Saver settings, or adding Level to the always-active list typically resolves the issue.
If you continue experiencing problems, our support team is happy to help.