FIX Chrome Suspending OpenClaw Web UI: 3 Solutions (2026)

Key takeaways

• OpenClaw’s WebSocket connects to a local backend. When Chrome discards the tab, that connection drops silently with no error.
• Fastest fix: add localhost to Chrome’s “Always keep these sites active” list at chrome://settings/performance.
• Local LLMs increase memory pressure until Chrome overrides its own exception list. An extension-level whitelist is more reliable.

You switch away from the OpenClaw Web UI to do something else, come back, and the tab has reloaded. Your session context is gone and the agent has disconnected from the backend. OpenClaw’s web UI maintains a WebSocket connection to a local Node.js backend. When Chrome discards the background tab, that connection drops silently — no error until you return and find a blank reload screen. This happens because Chrome treats localhost tabs the same as any other background tab: expendable under memory pressure.

Quick Diagnosis

Fix 1: Add Localhost to Chrome’s Active Sites List

Chrome’s native exception list is the quickest fix and costs nothing:

1. Navigate to chrome://settings/performance
2. Under Memory Saver, click Add next to “Always keep these sites active”
3. Enter localhost — Chrome will protect any localhost URL from discarding
4. If OpenClaw uses a specific port (e.g., localhost:3000), add the full address

Note: Chrome’s native list can be overridden under severe memory pressure. If you are running a local LLM alongside Chrome, that memory competition makes this less reliable — see the extension-level fix below.

Fix 2: Keep the OpenClaw Tab Visible

Chrome throttles and discards hidden tabs more aggressively than visible ones:

1. Right-click the OpenClaw Web UI tab
2. Select Move tab to new window
3. Position the window so it remains partially visible — this reduces throttling likelihood

Fix 3: Disable Background Timer Throttling (Advanced, Increases Battery Usage)

1. Navigate to chrome://flags
2. Search for “background timer”
3. Disable Throttle expensive background timers if present
4. Click Relaunch

This is a diagnostic step. If it resolves the disconnection, background timer throttling was the cause. Note this increases battery drain and may be renamed or removed in future Chrome versions.

Using Whitelist Rules to Protect Specific Tabs

For local AI workloads specifically, Chrome’s memory pressure heuristics work against you: Ollama, LM Studio, and similar inference engines consume large amounts of RAM, which makes Chrome more aggressive about discarding background tabs — not less. This is where the extension-level whitelist is more reliable than Chrome’s native setting.

1. Open the SuperchargePerformance popup while on the OpenClaw Web UI tab
2. Click the whitelist toggle to mark the current site as “never suspend”
3. The tab is excluded from chrome.tabs.discard() calls entirely

The extension simultaneously suspends other inactive tabs — news sites, reference pages, social feeds — freeing RAM that would otherwise compete with local LLM inference. Fix 1 is enough for most setups; this matters most when RAM is tight from running inference alongside Chrome.

Technical Background

OpenClaw’s Web UI is a Single Page Application (SPA) that maintains continuous WebSocket state with the local Node.js backend. The backend routes AI model responses, manages message bridges, and holds conversation context.

When Chrome discards a background tab, it terminates the renderer process completely. This destroys:

• The active JavaScript heap (all client-side state)
• All open WebSocket connections (no graceful close — the connection simply drops)
• Any pending callbacks or event listeners waiting for backend responses

The next tab focus triggers a full page reload. The SPA reinitializes from scratch, requests a new WebSocket connection, and the backend must re-establish context — if it can. Any messages processed while the UI was discarded are typically lost.

For local AI workloads specifically, Chrome’s memory pressure behavior is more aggressive because local inference engines (Ollama, LM Studio) consume large amounts of RAM. Chrome’s heuristics see high memory usage and become more aggressive about discarding background tabs — the opposite of what you need.

Related Articles

• Keep ChatGPT Running in Chrome Background Tabs — same fix for cloud AI tools like ChatGPT and Claude
• Fix ChatGPT Network Error in Chrome Background Tabs — diagnosing the WebSocket error when suspension hits
• Chrome Using Too Much RAM? Fix High Memory in Task Manager — reducing Chrome’s footprint to give local inference more headroom