Keep ChatGPT Running in Chrome Background Tabs (2026)

Key takeaways

• Background tab throttling breaks ChatGPT’s WebSocket keep-alive. Chrome kills the heartbeat and the generation dies mid-response.
• Fastest fix: add chatgpt.com and chat.openai.com to Chrome’s “Always keep these sites active” at chrome://settings/performance.
• Under RAM pressure, Chrome overrides its own exception list. An extension whitelist is more reliable. Same fix for Claude, Gemini, DeepSeek.

You send a long prompt to ChatGPT, switch tabs to do something else while it generates, and come back to a red “Network Error” — or worse, the tab has fully reloaded and your prompt is gone. Chrome throttles JavaScript timers in background tabs to save battery. When the tab is throttled hard enough, the WebSocket keep-alive signal fails. The AI server detects the missed heartbeat, assumes you disconnected, and stops the generation. The fix is straightforward: tell Chrome not to treat the AI tab like a disposable background tab.

Quick Diagnosis

Fix 1: Use Chrome’s Built-in Active Sites List

Chrome’s Memory Saver has a native exception list:

1. Navigate to chrome://settings/performance
2. Under Memory Saver, click Add next to “Always keep these sites active”
3. Add chatgpt.com and chat.openai.com
4. For other AI tools, also add claude.ai, chat.deepseek.com, gemini.google.com

This prevents Memory Saver from discarding these tabs, but Chrome’s native throttling of background JavaScript timers may still apply under some conditions.

Fix 2: Move the AI Tab to a Separate Visible Window

A tab that is visible in a window — even a small one moved to the side — is less aggressively throttled than a fully background tab.

1. Right-click the ChatGPT tab
2. Select Move tab to new window
3. Resize the window and place it where it is partially visible

Fix 3: Test the Throttling Flag (Advanced)

Chrome has flags controlling background timer throttling. These flags may be renamed or removed across Chrome versions.

1. Navigate to chrome://flags
2. Search for “background timer”
3. If Throttle expensive background timers or similar appears, set it to Disabled
4. Click Relaunch

Note: Disabling this flag increases battery drain on laptops. This is a diagnostic step — if the Network Error stops, background throttling was the cause.

Whitelisting ChatGPT to Prevent Suspension

Fix 1 (Chrome’s built-in list) handles this for most people. SuperchargePerformance offers a complementary approach: selective persistence — protect the tabs that need to stay alive and suspend everything else.

SuperchargePerformance’s per-site whitelist:

1. Add chatgpt.com (or claude.ai, chat.deepseek.com) via the extension popup
2. Those tabs are excluded from suspension — never passed to chrome.tabs.discard()
3. All other inactive tabs get suspended, freeing RAM and CPU for the AI tab
4. The WebSocket stays alive because the tab’s JavaScript engine keeps running

This is more reliable than Chrome’s native list under severe memory pressure, where Chrome can override its own exceptions. But for most users with 16 GB RAM and fewer than 30 tabs, Fix 1 alone is sufficient.

Technical Background

Real-time AI streaming uses WebSockets or Server-Sent Events (SSE) — persistent connections where the server pushes data to the browser as the response generates.

Chrome applies two background optimizations that can break these connections:

1. Timer throttling: Background tab JavaScript timers are aligned to fire once per minute rather than on their normal schedule. If a WebSocket heartbeat is expected every 5-30 seconds and Chrome delays it by 60 seconds, the server times out the connection.

2. Tab discarding: Under memory pressure, Chrome terminates the renderer process for background tabs entirely. This kills the WebSocket immediately, with no graceful close.

Both behaviors are intentional energy-saving features. The fix is not to disable them globally but to exclude specific tabs from them while they apply to everything else.

Related Articles

• Fix ChatGPT Network Error in Chrome Background Tabs — diagnosing the specific network error this causes
• Prevent Chrome from Suspending the OpenClaw Web UI — same problem for local AI tools running over localhost
• Disable Chrome Efficiency Mode for Specific Tabs — control throttling settings at the tab level