6bb030802e
* fix(sync): guard against caching empty state over good data (#7892) A local data-loss report (blank app after an overnight gap, no sync, on Android) surfaced a robustness hole: a transient hydration/IndexedDB glitch could leave NgRx in its initial empty state, which would then be written back over the good state cache and, on the next compaction, prune the very ops needed to recover — turning a recoverable hiccup into permanent loss. - Add `hasMeaningfulStateData()` as the single source of truth for "does this state contain user data?" (task / non-INBOX project / non-system tag / note). Reused by `SyncLocalStateService.hasMeaningfulStoreData()` which previously duplicated the predicate. - Snapshot save (`saveCurrentStateAsSnapshot`) and compaction (`_doCompact`) now skip when the live state has no meaningful data, refusing to overwrite the cache (and, in compaction, refusing to prune ops) against empty state. Skipping is always safe: the op-log is the source of truth and replay reconstructs the true state, including legitimate full wipes. - Hydrator: when the state cache is invalid/corrupt but the op-log is intact (lastSeq > 0), replay the log from the start instead of dropping straight to recovery-to-empty. Adds unit tests for the new predicate; existing snapshot/compaction/ hydrator/sync-local-state specs still pass. * test(sync): cover empty-state guard in snapshot/compaction specs (#7892) Adjust the existing snapshot and compaction specs for the new empty-overwrite guard, and fix the new predicate spec's fixture. - has-meaningful-state-data spec: use the real SYSTEM_TAG_IDS values (TODAY / EM_URGENT / EM_IMPORTANT / KANBAN_IN_PROGRESS) so the "default/initial state" and "system tags only" cases are accurate. - snapshot spec: default the state mock to meaningful data so the clock-pruning / compactedAt / entity-key tests still exercise the save; add a dedicated test that an empty state is skipped. - compaction spec: default mockState to meaningful data; convert the former empty-state tests to assert the guard skips saveStateCache and op deletion; give the entity-key-extraction states a live task so they pass the guard. All affected unit specs pass (152). * docs(sync): clarify compaction empty-state guard trade-off (#7892) Correct the `_doCompact` guard comment: the previous wording ("the next compaction with real state handles it") overstated safety. A store that is genuinely empty-but-active never gets its old synced ops pruned while it stays empty, so the op-log can grow. Document this as an accepted trade-off rather than implying it always self-heals. No behaviour change. https://claude.ai/code/session_01Lwt1t6AFwJGX6gNsuGoZXN * test(sync): cover hydrator corrupt-snapshot op-log replay (#7892) The headline #7892 fix — the hydrator discarding a corrupt/invalid state-cache and replaying the op-log when lastSeq > 0, instead of dropping to recovery-to-empty — had no test, and the two pre-existing "invalid snapshot handling" tests asserted the old unconditional-recovery behaviour without pinning lastSeq. Under Karma's randomized order a bled-in lastSeq > 0 made one of them take the new replay branch and fail. - Pin lastSeq = 0 in the two recovery tests so they deterministically exercise the (now conditional) recovery-to-empty branch, and rename them to state that precondition. - Add a test proving an invalid snapshot with lastSeq > 0 discards the snapshot, does NOT call attemptRecovery, and replays the full op-log via bulkApplyHydrationOperations. - Add a test for the lastSeq === 0 recovery branch. Hydrator spec: 67/67, stable across repeated randomized runs. https://claude.ai/code/session_01Lwt1t6AFwJGX6gNsuGoZXN * test(sync): fix perf integration spec for empty-state compaction guard (#7892) `performance.integration.spec.ts > should compact operations efficiently` stubbed `getAllSyncModelDataFromStore` (which compaction does not call) and left the shared `getStateSnapshot` default returning an empty store. With the new empty-state guard, compaction now correctly skips an empty state, so `loadStateCache()` returned null and the test failed. Give the test a task-bearing `getStateSnapshot` so compaction runs. No production change. All six compaction/snapshot integration specs pass (78). https://claude.ai/code/session_01Lwt1t6AFwJGX6gNsuGoZXN * test(sync): cover empty-state compaction guard against real IndexedDB (#7892) - add A/B integration test proving an empty live state cannot overwrite a good on-disk state cache or prune ops (real IndexedDB, not spies) - clarify in hasMeaningfulStateData JSDoc that the narrow scope is deliberate and only ever used in the safe (skip-not-overwrite) direction --------- Co-authored-by: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .air | ||
| .devcontainer | ||
| .github | ||
| .husky | ||
| .signpath/policies/super-productivity | ||
| .vscode | ||
| android | ||
| build | ||
| docs | ||
| e2e | ||
| electron | ||
| eslint-local-rules | ||
| fastlane | ||
| ios | ||
| nginx | ||
| packages | ||
| scripts | ||
| snap/hooks | ||
| src | ||
| tools | ||
| .browserslistrc | ||
| .dockerignore | ||
| .editorconfig | ||
| .env.example | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .gitpod.yml | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc.json | ||
| .stylelintrc.mjs | ||
| AGENTS.md | ||
| angular.json | ||
| ARCHITECTURE-DECISIONS.md | ||
| capacitor.config.ts | ||
| CLAUDE.md | ||
| CONTRIBUTING.md | ||
| docker-compose.e2e.fast.yaml | ||
| docker-compose.e2e.yaml | ||
| docker-compose.supersync.yaml | ||
| docker-compose.yaml | ||
| docker-entrypoint.sh | ||
| Dockerfile | ||
| Dockerfile.e2e.dev | ||
| Dockerfile.e2e.dev.fast | ||
| electron-builder.yaml | ||
| eslint.config.js | ||
| funding.json | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| ngsw-config.json | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| SECURITY.md | ||
| tsconfig.base.json | ||
| tsconfig.json | ||
| webdav.yaml | ||
An advanced todo list app with timeboxing & time tracking capabilities that supports importing tasks from your calendar, Jira, GitHub and others
🌐 Open Web App or 💻 Download
💻 Downloads & Install
For all current downloads, package links, and platform-specific notes:
check the wiki
✔️ Features
- Keep organized and focused! Plan and categorize your tasks using sub-tasks, projects and tags and color code them as needed.
- Use timeboxing and track your time. Create time sheets and work summaries in a breeze to easily export them to your company's time tracking system.
- Helps you to establish healthy & productive habits:
- A break reminder reminds you when it's time to step away.
- The anti-procrastination feature helps you gain perspective when you really need to.
- Need some extra focus? A Pomodoro timer is also always at hand.
- Collect personal metrics to see, which of your work routines need adjustments.
- Integrate with Jira, Trello, GitHub, GitLab, Gitea, OpenProject, Linear, ClickUp and Azure DevOps. Auto import tasks assigned to you, plan the details locally, automatically create work logs, and get notified immediately, when something changes.
- Basic CalDAV integration.
- Back up and synchronize your data across multiple devices with Dropbox and WebDAV support
- Attach context information to tasks and projects. Create notes, attach files or create project-level bookmarks for links, files, and even commands.
- Super Productivity respects your privacy and does NOT collect any data and there are no user accounts or registration. You decide where you store your data!
- It's free and open source and always will be.
And much more!
Note
The web version has some limitations: See the Web App vs Desktop comparison for more details.
📖 Documentation and Guides
Getting Started
- Getting started guide (article)
- Video walkthrough (YouTube)
- Eat the frog prioritizing scheme
Starting Point in Wiki:
First steps •
Reference •
How-To
Productivity Tips:
Keyboard Shortcuts •
Short Syntax
Need Help?
Visit the discussions page
See the bottom of the README for more information on the documentation.
Advanced Topics
Here are some other topics covered in the official wiki:
Development:
Run dev server •
Package the app •
Build for Android •
Run with Docker
Data Management:
User Data •
Issue Providers •
Sync Providers
Customization:
Plugins •
Themes
APIs:
Sync Server •
Plugins •
REST
Community
The development of Super Productivity is driven by a wonderful community of users and contributors. Thank you all so much for your support!
👀 Check out our awesome curated list of community-created resources about Super Productivity
♥️ Contributing
If you want to get involved, please check out the CONTRIBUTING.md
There are several ways to help.
-
Spread the word: More users mean more people testing and contributing to the app which in turn means better stability and possibly more and better features. You can vote for Super Productivity on Slant, Product Hunt, Softpedia or on AlternativeTo, you can tweet about it, share it on LinkedIn, reddit or any of your favorite social media platforms. Every little bit helps!
-
Provide a Pull Request: Here is a list of the most popular community requests and here some info on how to run the development build (wiki). Please make sure that you're following the commit message format and to also include the issue number in your commit message, if you're fixing a particular issue (e.g.:
feat: add nice feature #31). -
Answer questions: You know the answer to another user's problem? Share your knowledge!
-
Provide your opinion: Some community suggestions are controversial. Your input might be helpful and if it is just an up- or down-vote.
-
Provide a more refined UI spec for existing feature requests
-
Make a feature or improvement request: Something can be done better? Something essential missing? Let us know!
-
Translations, Icons, etc.: You don't have to be a programmer to help; learn how to contribute translations!
-
Create custom plugins or custom themes
Special Thanks to our Sponsors!!!
Recently support for Super Productivity has been growing! A big thank you to all our sponsors, especially the ones below!
-
Agentic AI Quality Engineering via:
(If you are, intend to or have been a sponsor and want to be shown here, please let me know!)
Code Signing
Windows binaries are signed. Free code signing is provided by SignPath.io, certificate by SignPath Foundation.
Documentation: Manual versus Automated
There are two wikis: the official one hosted in by GitHub autonomously generated variant using DeepWiki.com. The manually curated version is a more stable and approachable resource designed to help you understand the app from a more human-focused perspective whereas DeepWiki is optimized for explaining the code itself with little regard for context beyond that.
Official Wiki
It is preferable to maintain local documentation rather than rely on an external service. It also preferable that the documentation is updated in tandem with the code changes as demonstrated in this commit.
Changes to files within ./docs/wiki are linted in CI before being automatically
sync'd to the repository's official Wiki hosted by GitHub.
Migrating to Docusaurus is a long-term goal once the content and structure of the wiki has matured and the remaining "legacy docs" have either been reworked or removed. There are some automations in development to help reduce the difference between the published docs and the state of the code while retaining a human-in-the-loop.
DeepWiki.com
If you have very specific questions about how the code works or why a bug might be producing
a particular message it might be useful to
. It can help "cite your sources" when discussing functionality and code that you don't fully
understand as part of feature requests or bug reports.
This automated reference does come with some significant drawbacks:
- Intent: Describes what code does, not why decisions or tradeoffs were made.
- Staleness: Will *always* lag behind the code.
- Code-Focused: Does not provide guides or conceptual explanations.
- Cost: Potential future cost and higher resource usage than static docs.