Six status views, one composer, and labels that cut across everything. A task is an issue — nothing more to learn.
A task is one GitHub issue. Its title is the issue title, its notes are the issue body, and completing it closes the issue. Everything below is a way of looking at that one fact.
The six views
Section titled “The six views”| View | What belongs there |
|---|---|
| Inbox | Anything captured without a decision yet. |
| Today | Due today, or picked by you for today. |
| Upcoming | Has a due date, later. |
| Anytime | Ready whenever you are. No date. |
| Someday | Maybe. Out of sight, not out of reach. |
| Logbook | Done. Closed issues, newest first. |
The view a task lands in follows its due date. Give a task a date and it moves on its own; clear the date and it returns to Anytime.
Capture
Section titled “Capture”The composer sits at the top of every list. Type, press ↵, keep going. The task appears immediately and syncs to GitHub in the background — a row dimmed with a soft pulse is still in flight, and a red cloud marker means the write failed and will be retried.
An area is a GitHub label, and it cuts across every view: Work, Personal, Health, Finance, Learning. Pick one on a task, or filter a list by it with the chips under the page title.
Areas are a facet — a task has one, and it travels with it everywhere. Projects are a place. That is the whole difference.
Due dates and overdue
Section titled “Due dates and overdue”A due date can carry a time. When a task is past due and still open, its row takes a red edge, its title turns red, and the date is replaced by a single Overdue label — one clear signal instead of three.
Completing a task
Section titled “Completing a task”Click the circle, or press ⌘ ↵ on the focused row. The task closes on GitHub and appears in your Logbook. Nothing is deleted, and the history stays readable in the repository forever.