fix(sessions): keep streaming live when the window is backgrounded

Streamed agent events are committed to the conversation store via a short
setTimeout flush in the renderer. Chromium clamps and (when the window is
occluded/hidden) freezes renderer timers, so while the app is backgrounded that
flush never runs: streamed events pile up unflushed and only render in a burst
when the timer thaws on refocus. This is why a waiting/looping agent appears to
hang and its messages all appear at once after the user sends a follow-up.

Set backgroundThrottling: false on the main window so renderer timers keep
running at full speed while backgrounded, letting live streaming flow during
long-running agent runs.

Generated-By: PostHog Code
Task-Id: d38d3951-6357-4d57-809c-74d47581a163

Author: posthog[bot]

apps/code/src/main/window.ts

@@ -215,6 +215,16 @@ export function createWindow(): void {
     webPreferences: {
       nodeIntegration: false,
       contextIsolation: true,
+      // Keep the renderer running at full speed when the window is backgrounded
+      // or occluded. Chromium otherwise clamps (and, once the window is hidden,
+      // effectively freezes) renderer timers, which stalls the setTimeout-based
+      // flush that commits streamed agent events to the conversation store. That
+      // stall is what makes a waiting/looping agent appear to hang while
+      // backgrounded — its messages pile up unflushed and only render in a burst
+      // when the window is refocused (e.g. by sending a follow-up). Disabling
+      // throttling keeps live streaming flowing while the app sits in the
+      // background during long-running agent runs.
+      backgroundThrottling: false,
       preload: path.join(__dirname, "preload.js"),
       enableBlinkFeatures: "GetDisplayMedia",
       partition: "persist:main",