Brooklyn Nicholson 8ccb4c2cee perf(desktop): scope background-throttling opt-out to live streaming ... The process-wide disable-background-timer-throttling / disable-backgrounding-occluded-windows switches plus a static backgroundThrottling: false on every chat window pinned each renderer's document.visibilityState to 'visible' for the life of the window. Every visibility-gated backstop poll and clock tick in the renderer became an always-on timer: an idle, minimized Hermes burned ~20% CPU around the clock, on battery too. Throttling is now a runtime dial. A small controller (stream-throttle.ts) rides the merged hermes:active-work reports the quit guard already receives: while any turn is in flight every chat window gets setBackgroundThrottling(false) — a live answer keeps painting while blurred, occluded, or minimized, exactly as before — and once all turns settle (plus a 5s trailing window so the final flush lands at full cadence) Chromium's default throttling returns and hidden windows go quiet. disable-renderer-backgrounding stays: process priority only, no timer semantics, and it keeps hidden streaming fast.		2026-07-31 00:38:11 -05:00
..
bootstrap-installer	test(installer): pin own-pid adopt for desktop-prewritten update marker	2026-07-30 17:57:13 +07:00
desktop	perf(desktop): scope background-throttling opt-out to live streaming	2026-07-31 00:38:11 -05:00
shared	refactor: drop the shared subpath export, keeping package.json untouched	2026-07-28 03:54:49 -05:00