Module guide
Inbox triage
Keyboard-only GTD flow, one card at a time.
Overview
Picks tasks that need a decision (no assignee, schedule, or priority, or a recent capture) and shows them one at a time. Keybinds apply a deterministic outcome: E for today, W for this week, L to snooze 2 weeks, X to archive, and Space to skip.
Highlights
The capabilities worth knowing before you dive in.
- pickTriageCandidates() in shared-types is pure
- A progress bar tracks toward inbox zero
- No network call on skip; real outcomes hit the PATCH, snooze, and archive endpoints
Important to know
Limits, permissions, and sharp edges to keep in mind.
- Triage is opt-in; nothing changes unless you hit one of the decision keys.
- Skipped cards come back next session, so skip is not the same as dismiss.
How to use it
The primary workflow, start to finish.
- Open /inbox/triage after a capture or a long break.
- Decide each card with one key. Done.
FAQ
- Does triage change anything if I just look at it?
- No. Triage is opt-in and nothing moves until you press one of the decision keys. Opening the screen and closing it again leaves every task exactly as it was.
- What is the difference between skipping and dismissing?
- Skipping is not a decision. A skipped card returns in the next session, which is deliberate: it lets you pass over something you are not ready to judge without losing it. Archiving is the decision that takes it off the list.
- Which tasks does triage choose to show me?
- The ones that need a decision: no assignee, no schedule or no priority, plus anything captured recently. The selection is a pure function, so the same inbox produces the same queue.
Automate this module
Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
Was this page helpful?