The change concerns already-open views only. Anyone with working time or personal to-dos open in several browser tabs or on several devices could, after a change, initially still see a stale display.
When working time was started on a phone or a to-do was checked off in another browser, an open tab showed the new state only after reloading. The data was correct; only the already-open view had not yet updated.
Updates without reloading
Now the server reports changes to open pages through Server-Sent Events, or SSE. Those pages update their display when something changes in another browser. No one needs to reload manually.
The technology behind this does not need to matter to users. What matters is simple: an open page stays current, even when the change happens elsewhere.
Two small, frequent cases
For working time, this applies to start, pause and stop. Someone can leave the page open on a laptop and pause on a phone while away; the open tab then shows the correct status too. There is no moment of guessing which indicator is right.
The same applies to the personal to-do list. When a thought is added on a phone or an item is completed, the change appears in other open browsers as well. The list can remain what it is meant to be: a simple, dependable place for things that do not need to stay in your head.
A detail that should not stand out
The improvement adds no new interaction. No one needs to start a sync or configure anything. It simply removes an unnecessary step: reloading an already-open view to update it.
This is the kind of technical improvement that ideally earns a quick “of course.” Then it gets out of the way and people return to their actual work.