Define the action
Add the outcome, priority, schedule, tags, and optional project.
← All features
Tasks
Action with enough context to finish.
Plan work with priorities, dates, status, projects, dependencies, reminders, people, goals, notes, and reusable encrypted files.
Purpose
Why Tasks exists.
Tasks turn intent into an executable system. Multiple views help you choose by time, status, priority, or project without splitting work across tools.
PRODUCTIVITY EFFECTMake next actions visible, expose blocked work, and keep supporting context beside the thing that needs doing.
How you will use it
Useful from the first action to the next.
Connect the context
Attach Notes, Files, People, Goals, and Reminders or define dependencies.
Work from your view
Use List, board, My Day, Upcoming, Overdue, or filtered views to execute.
In real work
Different roles. A specific advantage.
These examples show how the same feature can remove a different kind of friction depending on the work around it.
Engineer
Track dependent implementation work with project files and decision context.
Freelancer
Separate client deliverables while keeping deadlines visible together.
Student
Break assignments into scheduled actions and see overdue work immediately.
Data & privacy
What it uses. What it stores. Where the boundary sits.
Task content, relationships, schedule, status, and ordering choices.
Authored fields are encrypted. Required dates, lifecycle, relationship IDs, and quota metadata remain operational.
Task plaintext is read in the unlocked client; AI sees a task only after explicit attachment or permission.
Connected system
Tasks becomes more useful beside…
Make it part of one system
Start with Tasks. Connect the rest when it helps.
No imported complexity. No privacy compromise.