[TimeToBuildBob]

Summary

Adds an opt-in setting, "Only report while the browser is focused"
(default off, so existing behavior is unchanged), that stops heartbeats
while no browser window has OS focus and resumes immediately when focus
returns.

• Listens for windows.onFocusChanged; WINDOW_ID_NONE pauses heartbeats,
  refocus sends an immediate heartbeat so the gap ends right away instead of
  waiting for the next alarm tick.
• On every alarm tick, re-polls windows.getLastFocused() as a fallback,
  since focus-change events are unreliable on some Linux window managers
  (noted in the issue).
• Gates heartbeatAlarmListener, tabActivatedListener, and
  tabUpdatedListener on the new check so no heartbeat is sent while paused
  and the setting is on.

This repo has no existing unit-test framework (no jest/vitest, no test
script, CI only builds/lints) — there's nothing to extend here, so
verification is: npx tsc --noEmit clean, npx vite build --mode production clean, pre-commit hooks clean. Manual Chrome/Firefox
verification (switching apps for a couple minutes and checking for a gap in
the bucket, as suggested in the issue) still needs a human with a desktop
browser — happy to iterate on review feedback.

Fixes #140.

Test plan

• npx tsc --noEmit — clean
• npx vite build --mode production — clean
• pre-commit hooks — clean
• Manual verification in Chrome and Firefox against :5600 (maintainer/reviewer, no desktop browser available in this environment)

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; the previous browsing-time issue is fixed, and no new actionable issues were found.

Summary

The PR adds an opt-in setting to stop reporting while the browser is unfocused. The latest changes fix how missed focus events are handled:

• Browser heartbeats pause when no browser window has focus.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Heartbeat alarm] --> B[Poll browser focus]
  B --> C{Pause setting enabled?}
  C -->|No| D[Send normal heartbeat]
  C -->|Yes| E{Focus state}
  E -->|Focus just lost| F[Clear stored data without sending]
  E -->|Still unfocused| G[Skip heartbeat]
  E -->|Focus just returned| H[Send heartbeat with pulsetime zero]
  E -->|Still focused| D

Loading

_{Reviews (4) · Last reviewed commit: "fix(heartbeat): don't stamp poll-detecte..." · Reviewed by Greptile}

[TimeToBuildBob]

Fixed both Greptile findings in b178771:

P1 — Short pauses can disappear

Root cause: on refocus, sendInitialHeartbeat used the same tab data as the last pre-pause heartbeat. With AW's 100s pulsetime, any unfocused interval shorter than that would be merged away, making the user appear continuously active.

Fix: on focus loss, send a standard-pulsetime heartbeat to close the AW event at exactly the focus-loss time, then clear the cached heartbeat data. On focus gain, sendInitialHeartbeat is called with pulsetime=0, which tells AW to create a new event at the exact refocus time — no merging regardless of gap length.

P2 — Startup heartbeat ignores pause

Root cause: refreshWindowFocus() was fired-and-forgotten (line 88) concurrently with the clientReady startup chain, so the initial heartbeat could fire before the focus state was updated from the startup default of isWindowFocused=true.

Fix: refreshWindowFocus() is now chained immediately before sendInitialHeartbeat in the startup sequence. Additionally, sendInitialHeartbeat itself now checks shouldPauseForUnfocus() as a safety net — if the browser is unfocused when it fires, the heartbeat is skipped.

[TimeToBuildBob]

@greptileai review

[TimeToBuildBob]

@greptileai review

[TimeToBuildBob]

Addressed the remaining P1 ("Polled focus skips gap handling") in 25abb19.

When the alarm poll detects a focus loss that the focus-change event missed, it now closes the AW event at the poll time and clears the stored heartbeat data, the same as the event path. Refocus then starts a fresh event instead of merging across the gap.

Verified: npx tsc --noEmit passes on 25abb19. Re-triggered Greptile on this head.

[TimeToBuildBob]

@greptileai review

[TimeToBuildBob]

CI-green and mergeable (Greptile 5/5) — waiting only on a maintainer click.

This PR is ready to merge, but the bot has pull-only access to this repo and can't self-merge — surfacing it here so it isn't lost. The monitoring loop will stop re-flagging it now that this note is posted.

[TimeToBuildBob]

Rebased onto current master and pushed 8e399b3 with an explicit lease on the previous head.

The heartbeat conflict now preserves both group-only tab updates from master and the opt-in focus gate. The integration tests also caught an ordering regression: awaiting the pause setting before taking the tab snapshot let subsequent tab mutations leak into earlier events. The pause checks now run inside the serialized heartbeat queue, preserving synchronous snapshots and queue order.

Verified locally:

• All 40 tests pass (node --test tests/*.test.*), including four added cases for opt-in suppression, default-off behavior, polled loss/refocus and event-driven loss/refocus.
• TypeScript compilation and Chrome/Firefox production builds pass.
• Pre-commit checks pass.

Native browser/OS-focus verification remains outstanding; these are deterministic production-module tests with browser/storage/client stubs, not an installed-extension check. CI is running on the new head.