What Mindwtr is
Mindwtr manages the commitments and actions in your personal life, using David Allen's Getting Things Done method. This page describes what sits at the center of the product, so you can judge whether it fits the way you work.
GTD-native
Inbox, Projects, Contexts, Waiting For, Someday, and Review are first-class parts of Mindwtr. They are how the app is built, not labels bolted onto a generic task list. When you capture something, clarify it, and file it, you are running the GTD loop directly. The GTD overview explains the method, and the GTD workflow shows how each step maps to a screen.
Notes support the work
You can attach notes and files to tasks and projects, so the context you need sits next to the work. Mindwtr stops there. It is not a knowledge base and does not try to become one. When your reference material wants a real home, keep it in a tool built for that. The Obsidian integration exists for exactly this reason: your notes stay in your vault, and Mindwtr reads the tasks out of them.
Personal, not team
Mindwtr holds one person's commitments: yours. There are no shared workspaces, no assigning tasks to teammates, no comment threads, and no activity feed. Waiting For tracks what you are owed by other people, which is a personal record rather than a collaboration channel.
Simple by default, powerful when needed
The daily loop is capture, clarify, review, and everything you need for it is visible without configuration. The heavier features (AI, the local API, the MCP server, boards, Pomodoro) stay out of the way until you turn them on, and turning them on never makes the basic loop harder. The project README puts it plainly:
Don't show me a cockpit when I just want to ride a bike.
Automatic beats manual
Where a sensible default exists, Mindwtr picks it instead of asking. It reads platform conventions and the channel you installed from rather than adding a setting for each choice. Fewer switches leave less to maintain and less to get wrong.