Repository navigation
Getting Things Done v0.5.1
Getting Things Done v0.5.1
Swipeable cards now cover all four workbench views, including the standalone questions that previously stayed in the list layout.
Changes
- Use the same card/list preference for tasks, calendar events, clarification candidates and standalone questions, projects, waiting items, review steps and recent summaries.
- Include standalone questions in search, filters and sidebar counts, while preserving their answer drafts across card navigation and reloads.
- Keep completed standalone replies in expandable history. Saving a new answer opens and selects its processing result immediately.
- Preserve navigation while a saved answer waits for its state refresh; a slow response no longer breaks the reply-history deck.
- Distinguish recurring calendar occurrences by their series ID and start time so that later occurrences remain reachable.
- Retain review checkboxes and card positions across navigation and refresh.
- Keep the selectable list layout and the existing success feedback timing: 0.4-second hold + 0.3-second fade.
Downloads
- Getting-Things-Done-v0.5.1-macos-arm64.zip — macOS 14+ Apple Silicon app with the precompiled EventKit bridge. Requires Python 3.11+.
- Getting-Things-Done-v0.5.1-source.zip — matching source, tests and documentation.
- Getting-Things-Done-v0.5.1-Toy-demo.zip — the compatible standalone demo with synthetic data. Its web content is unchanged from v0.5.0; this correction affects the private workbench.
- SHA256SUMS — checksums for all three archives.
Private data and model settings remain in their existing locations. The app is ad-hoc signed and is not notarized.
Verification
The workbench and card/Toy browser scenarios cover the full clarification/confirmation workflow, the newly connected collections, standalone answer processing during a delayed refresh, repeated calendar occurrences, list fallback and a 390 px layout. Python tests, JavaScript syntax checks, native builds and strict signature checks use isolated or synthetic state; no real model calls or Apple task writes are required.
The packaged app is separately opened after extraction to a different path, using its own UI resources and prebuilt bridge. Physical mobile-device acceptance and notarization are outside this release's verification.