Mindwtr: A Local-First GTD App That Refuses Weak Sync

What Mindwtr Fixes and Who It Serves

Mindwtr targets people who have tried to keep a to-do list and ended up with 80 items they avoid opening. The project applies the Getting Things Done method end to end: capture, clarify, organize, engage, and reflect. The specific pain points in the README are familiar: you think you will remember something and you do not, a task like 'Plan Mom's birthday' sits for weeks because it has no next step, and delegated items get forgotten because nobody tracks them. The app is for individuals, not teams. It runs on Windows, macOS, Linux, iPhone, Android, and as an offline-capable web app. The audience is someone who wants a structured personal productivity system without creating an account or paying a subscription.

The Core Loop: Capture, Sort, Do, Reset

The workflow has four steps. First, capture: a global hotkey on desktop, a widget and share sheet on mobile, plus voice input, drop items into an Inbox. Second, sort: a guided pass over the Inbox applies the two-minute rule, schedules dated tasks, tracks delegated items, and shelves maybes into Someday/Maybe. Third, do: the Focus view shows only today's schedule and next actions, hiding everything else. Fourth, reset: a weekly review wizard catches loose ends. This is not a novel mechanism. It is a faithful implementation of GTD, but the guided aspect matters. The README says if you do not know GTD, the app walks you through each step. That is a real difference from a bare task manager that assumes you already know how to organize.

Data Storage and the Strict Sync Gate

Mindwtr is local-first. Your data lives on your device, and sync is optional. You choose the backend: iCloud on Apple devices, Dropbox, a shared folder, your own server, or WebDAV. The interesting part is the verification step. The README states that WebDAV servers must return strong ETags and enforce conditional writes. During connection setup, Mindwtr verifies create-only writes, exact replacements, stale-write rejection, and conditional cleanup. Providers that cannot prevent one device from overwriting another device's generation are refused. That is a concrete, testable requirement. It means you cannot just point the app at any WebDAV endpoint. If your provider is sloppy about ETags, the app will reject it. This is a design choice that favors data integrity over convenience, and it is worth checking before you rely on a particular server.

Getting It Running: Platforms and Setup

Mindwtr is distributed through official app stores: Microsoft Store, Google Play, Apple App Store, Flathub, F-Droid, IzzyOnDroid, and Snapcraft. There is also a web app that works offline. The README does not give a command-line installation method for desktop, but the presence of a local REST API, a CLI, and an MCP server suggests developers can interact with it programmatically. For sync, you configure a connection to one of the supported backends. The docs linked in the README cover cloud deployment, which implies you can self-host the sync component. No specific setup commands appear in the provided material, so if you want exact steps, you need to consult the docs at docs.mindwtr.app.

Limitations and Failure Modes

The most obvious limitation is the sync requirement. If you use a WebDAV provider that does not support strong ETags or conditional writes, the app will refuse to connect. That is a hard constraint, not a warning. Another limitation: the app is designed for a single user. There is no mention of team collaboration, shared projects, or assignment of tasks to others beyond the 'Waiting For' context, which tracks that you asked someone for something. The AI helper is optional and off by default, but it requires you to bring your own OpenAI, Gemini, or Claude account, or run a private model. That is not a limitation per se, but it means the AI features do not work out of the box. The README also mentions that the web app works offline, but it does not say how offline sync conflicts are resolved beyond the strict WebDAV checks.

Alternatives and How They Differ

A common alternative is Todoist, a cloud-based task manager that syncs through its own servers. Todoist does not require you to configure WebDAV or think about ETags; you just create an account. The trade-off is that your data lives on a third-party server, and you cannot self-host. Another alternative is a plain text system like Todo.txt, which stores tasks in a flat file and syncs via Dropbox or Git. Todo.txt has no GTD structure, no Inbox processing wizard, and no weekly review. Mindwtr sits between these: it gives you the full GTD workflow and local control, but it demands a sync backend that meets strict concurrency rules. If you want zero setup and are fine with cloud storage, Todoist wins. If you want maximum simplicity and are willing to manage your own file sync, Todo.txt wins. Mindwtr is for people who want structure and local control, and who have a compatible sync target.

Maintenance, License, and Upgrade Cost

Mindwtr is licensed under AGPL-3.0. That means if you modify and distribute it, you must share your source code under the same license. For personal use, this is not a problem. If you plan to deploy it as a service, the AGPL has network-use implications, so you should understand that before building on it. The repository has recent releases, with v1.2.5-rc.2 pushed in August 2026, so development appears active. Upgrade cost depends on how you install it. If you use an app store, updates are handled by the store. If you self-host the sync server, you will need to update that component separately. The README mentions a local REST API and a CLI, which are developer-facing surfaces that could change between versions. Before you automate anything against those interfaces, check the changelog for breaking changes.

Editorial conclusion

Adopt Mindwtr if you want a GTD workflow that stays local by default, with optional sync you control, and if you are comfortable with AGPL-3.0. Do not adopt it if you need a multi-user team task manager or if you rely on a sync provider that does not support strong ETags and conditional writes. Before committing, verify that your chosen sync backend passes Mindwtr's connection tests, and check the current state of the MCP server and CLI if you plan to automate tasks.

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes