Known Limitations

"System tray, browser fully closed"

A browser extension's code can only run while the browser process itself is running - there is no extension API that keeps code executing with the browser completely quit.

Sight behaves like a normal, always-ready background extension while Chrome is open: it doesn't need any tab open, and it survives Chrome sitting minimized or in the background. What it can't do is show a tray icon or fire reminders with Chrome fully closed - that's a platform boundary, not a bug.

To get literal "tray icon with the browser fully closed" behavior, you'd need a separate, small native companion app (built with something like Electron or Tauri, or even a lightweight script) that either:

• launches Chrome in the background on login (some OSes / Chrome settings support "open at login"), or
• runs independently of Chrome and shows its own tray icon/reminders, optionally talking to the extension over Native Messaging

That companion app would be a separate, standalone project from the extension itself.

Idle detection accuracy

As covered in Advanced Features, Chrome's idle API can only observe activity directed at the browser. If you're working in another application entirely while Chrome sits in the background, Sight may pause the timer even though you're actively working - there's no cross-application activity signal available to an extension.