Super Productivity
Open-source to-do list and time tracker for personal task management
Super Productivity's feed shows a docs commit, not a release, since August.
◆Recent moves
- 29d ago
Docs commit records repeat and time-block capture gaps
A branch tag on a documentation commit recording known capture gaps for repeat tasks and time blocks. Not a release.
View source ↗ - 2mo ago
Tracked task in the tab title; Android gets URL-scheme actions
A repair-weighted patch closing out the 18.21 device-surface push: legacy data migration, reminders no longer blocking overdue repeating-task cleanup, and sync repair reliability with privacy hardening, plus SuperSync maintenance of older operations. The additions are small but one points outward, as URL-scheme task actions give Android automations a way to drive the app.
View source ↗ - 2mo ago
SuperSync adds opt-in live presence; Android beta crash fixed
The second half of the device-surface pair: presence is opt-in, so a device can show it is actively tracking without exposing more than that. The rest is repair — an Android beta startup crash, credential handling during device migration, and sync deployments that terminate orphaned concurrent index builds.
View source ↗ - 2mo ago
SuperSync gains a device list with remote sign-out
The release that turned SuperSync from a sync engine into an account surface, adding a connected-device list with the option to sign other devices out. A full worklog export and focus-mode state on the local API landed alongside it.
View source ↗ - 3mo ago
Dialog fills move to theme tokens; callout markup corrected
A styling correction with no behavioural change: dialog fills move onto theme tokens and callout markup is brought back in line with its contract. Presentation-layer tidying that sits outside the sync and plugin work driving this line.
View source ↗ - 3mo ago
Encrypted-only sync enforced; local REST API now needs a token
The hardening release that set the defaults this line builds on, enforcing encrypted-only SuperSync uploads and putting a bearer token in front of the local REST API. Both are fail-closed choices that the later device-management work assumes rather than revisits.
View source ↗