ActivityWatch v0.14.1: UI polish and a critical Windows data fix
ActivityWatch v0.14.1 restores the Windows data path, but does not merge Local and Roaming histories when both exist. Read the recovery caveat before upgrading; the release also improves category management, UI polish, and server reliability.
ActivityWatch v0.14.1 is out today. It includes 35 fixes and five features in aw-webui, 16 fixes in aw-server-rust, and five fixes plus optional API-key authentication in the Python server, alongside updates to the desktop shells, watchers, and shared libraries.
Windows upgrade caveat (updated October 12): v0.14.1 restores the original data location, but does not merge histories when both Local and Roaming contain databases. The earlier version of this post overstated the recovery. Read the cases below before upgrading.
The Windows data path fix
v0.14.0 changed aw-server-rust’s default data directory on Windows from %LOCALAPPDATA% to %APPDATA% (the Roaming directory). This affected classic Qt installations using the optional Rust server and the Tauri distribution. The default Python server, macOS, and Linux are not affected by this directory regression.
For affected installations, historical data could appear missing: it was still on disk, but the application was looking in a different location. v0.14.1 restores %LOCALAPPDATA%. The release notes link the directory fixes in aw-server-rust and aw-tauri, but recovery depends on what is already in those folders:
- No existing Local database: the Roaming data can migrate back to Local automatically.
- Both locations contain databases: the old Local history becomes active again. Events recorded by v0.14.0 remain in
%APPDATA%\\activitywatch\\aw-server-rust; they are not merged into the active history. Seeing your older history again does not mean the newer events have been recovered.
If you are still running v0.14.0 with those newer events visible, export them from the web UI before upgrading. Keep backups of both data directories; do not delete one or overwrite one database with the other as a substitute for merging. If you have already upgraded and newer events appear missing, preserve both directories and follow the open Windows recovery issue.
Complete dual-database recovery is still outstanding. This post is not verification of a Windows runtime recovery test, and v0.14.1 should not be described as recovering all history automatically.
Categories got a serious overhaul
Category management and the bundled presets received several improvements:
Layered category sets. You can now import a category preset and layer it on top of your own rules instead of replacing them. The new “Add on top of mine” option in the import dialog handles the merge. Edits made while layered — renames, deletions — now persist correctly across reloads.
Geography-free preset. There’s an optional preset that omits geography-based categories, useful for research setups or privacy-sensitive environments.
Category colors are softer. The default palette was replaced with lower-saturation alternatives, which look better in both light and dark mode without breaking anyone’s stored defaults.
The category builder’s ignored words now persist. Previously they were lost on reload.
UI polish: 35 fixes
The aw-webui version bundled with v0.14.1 includes 35 bug fixes, many addressing layout and display correctness:
- The sunburst category chart now fits labels inside their rings instead of clipping them
- Timeline rows have consistent labels for synced (multi-device) buckets
- Dark mode gets correct color-scheme handling for embedded iframes (custom visualizations were showing white-on-white)
- The top-applications view now colors each app by its dominant category rather than a generic palette
- The time spiral scales to fit narrow screens
- The work report counts sessions correctly using break time
- Category graph nodes are now labeled
These aren’t headline features, but they’re the kind of friction that accumulates into “I should use a different tool.” v0.14.1 removes a lot of it.
aw-server reliability: 5 fixes and optional authentication
The Python server received fixes that address correctness issues in long-running deployments:
- Heartbeats now invalidate the event cache when they insert events. Previously, a bucket’s event list could be stale after a heartbeat, causing the UI to show outdated data until the next full reload.
- Merged heartbeat events are replaced by ID rather than by the latest timestamp.
- Malformed client input returns HTTP 400 instead of HTTP 500.
- Import errors return descriptive messages and roll back the failed import instead of leaving partial state.
The Python server also gains optional API-key authentication, matching aw-server-rust.
aw-server-rust: 16 bug fixes
The Rust server includes 16 fixes. Notable ones:
- Re-importing an updated export replaces events in place rather than creating duplicates
-
Re-import deduplication works against the privacy-filtered form of events
- The datastore infers schema version when a restored database has
user_version=0(affects databases created by certain migration paths) - The schema v3→v4 key-value migration is now idempotent (can run multiple times safely)
- CSV exports prefix data keys that collide with reserved column names (
id,timestamp,duration) - Events with negative duration and heartbeats with negative pulsetime are rejected at the API boundary rather than silently stored
- The JNI datastore on Android is opened exactly once
Where to get it
Release page — Windows, macOS, Linux, and the Tauri experimental distribution.
ActivityWatch is free and open source. AW Pro is an optional subscription ($5/mo or $50/yr) that funds ongoing development. If ActivityWatch is part of your workflow, it’s the direct way to keep it maintained.