Support

Most problems with WindoM fall into one of a handful of shapes. Try the matching fix below first - if none of them helps, open an issue on GitHub or email yehudabriskman@windom.app.

Google Calendar keeps disconnecting#

If you connected Calendar before 26 October 2026 and found it disconnected roughly a week later, that was a configuration fault on our side rather than anything you did. Google expires access for applications whose consent screen is still in testing after seven days, and WindoM's was. It is published now, so a connection made today stays connected.

Reconnect once from Settings → Apps → Calendar → Connect and it should hold.

Signing in appears to work, then signs me out#

Fixed in 1.5.1. A failure in any one connected service - Calendar, Spotify - was being read as the whole session having expired, which signed you out moments after signing in. The more services you had connected, the faster it happened.

Check you are on 1.5.1 or later at chrome://extensions. Chrome usually updates extensions within a few hours, and Update on that page forces it.

Spotify ignores the first press of a button#

Also fixed in 1.5.1. Play, pause, next and previous all reached Spotify correctly, but the dashboard went on showing the state from just before the command for up to fifteen seconds - so it looked as though nothing had happened, and pressing again appeared to fix it.

A "this app isn't verified" screen when connecting Google#

Expected, and safe. WindoM's verification with Google is in review. Until it completes, Google shows that warning for applications it has not finished reviewing. You can continue past it, and the extension only ever asks to read your calendar - the exact permissions are listed in the privacy policy.

Removed deliberately in 1.5.0. Reading mail needed a Google permission class that carries a mandatory annual third-party security assessment costing several hundred to several thousand dollars a year. That is not sustainable for a free extension, so the widget was withdrawn rather than funded by changing what WindoM does with your data.

Weather shows the wrong place#

WindoM asks the browser for your location and falls back to a rough lookup from your IP address, which can be some distance out on a VPN or a mobile connection. Set a city by hand in Settings → Weather.

Settings did not follow me to another computer#

Settings sync through your Chrome profile, so both machines need to be signed in to the same Chrome account with sync enabled. Background images, cached weather and tab history are deliberately excluded - they are large, and they stay on the device that made them.

Reporting something else#

To get a problem fixed quickly, include:

The WindoM version from chrome://extensions
Your Chrome version and operating system
What you did, what happened, and what you expected instead
Anything in the console - right-click the new tab, Inspect, then the Console tab. Errors there are usually the whole answer.

WindoM is open source, so you can also read the code for any behaviour described here: github.com/YehudaBriskman/WindoM. Reviews and bug reports on the Chrome Web Store listing are read too, though GitHub is the faster route - the store gives no way to reply with a follow-up question.