Will Be Done
Local-first task manager with a visual weekly timeline
Alternative to: todoist, ticktick, super productivity
v0.11.0
2026-08-20What’s new
Public API and access tokens
Will Be Done now has a versioned HTTP API for scripts and integrations. Its 48 bearer-authenticated operations cover spaces, projects, project sections, tasks, task templates, checklists, daily lists, scheduled tasks, and the stash.
Create, inspect, copy, and revoke API tokens from Space Settings. Interactive API documentation is available at /api/docs, with the OpenAPI document at /api/openapi.json.
Sync and storage reliability
Sync now uses protocol v4. Uploads and downloads are staged, checksummed, and applied atomically. The protocol also handles lost responses, client and server backup restoration, clock skew, and permanent tombstones.
Existing databases migrate when they open. The backup loader still accepts the older category and projection formats.
Related PRs: #77, #79, #84, #88.
Database and deployment options
SQLite remains the default. Self-hosted installations can now use Turso Cloud or the new Rust-based tursod service.
This release also adds Redis-backed sync notifications, shared Redis rate limiting, Fly.io deployment configurations, and a guarded SQLite-to-tursod migration workflow. API rate limits are enabled by default.
App and website changes
- Checklist rows now have an accessible delete action on desktop and touch devices. #90
- Stashed tasks retain access to their details, with regression coverage added. #91
- The quick-add window loads less application infrastructure.
- Flatpak installations can open or focus the main window through
will-be-done-show. - Space deletion controls no longer lose clicks to card navigation.
- Daily-list restoration and legacy backup handling received more fixes.
- The landing site has clearer navigation and product information. #92
- The landing site now has release pages, RSS, structured metadata, and automated GitHub release syncing. #93
Upgrade notes
- Deploy the v0.11.0 web client and API together. The server accepts only sync protocol v4. Older clients must update before they can continue syncing.
- Existing SQLite installations need no new database configuration. Back up self-hosted data before the first v0.11.0 startup because storage migrations run when databases open.
- Multi-instance deployments should configure Redis so all API processes share rate limits and sync notifications.
- The existing S3 backup worker supports SQLite only. Use Turso backups for Turso Cloud. Back up the
tursoddata directory with a separate process.
Full changelog: https://github.com/will-be-done/will-be-done/compare/v0.10.1…v0.11.0