Tasks helpers — sorting, read deadlines and Caught review

What it is

Small helpers that were already built into Tasks and are now switched on. They save you from setting dates, groups and follow-ups by hand, and they help the Caught list get reviewed the same day instead of going stale.

Where to find it

• Groups: the chip on any task row once you rate its importance or urgency, and ⋯ More → Sort tasks by urgent & important in the Tasks header.
• Read deadlines: a dimmed Looks due … chip on the task row, and Looks due: on the Today list.
• Meeting items, keep marks: the Caught list.
• Caught review: the evening close-out dialog (Close out my day on Today, or the automatic evening prompt).

How it behaves

Every AI helper reads what Tasks learned about you

The notes in ⋯ More → About you now reach every Tasks AI helper: the daily check-in and its follow-up replies, Plan my day, Arrange, plan chat, "do this next" and Break it down. Each note is marked as something you told Tasks or something it guessed from your activity. A note you write yourself is used right away, even before Tasks has three days of history. With Tasks memory turned off, no helper sees any note.

Urgent and important groups

When you set a task's importance or urgency, Tasks puts it in an urgent/important group: Do first (important and urgent), Plan (important, not urgent), Delegate (urgent, not important) or Drop (neither). The group chip on the row updates when you change the dials. Pick a different group from the chip and Tasks never changes your choice again. To sort every open task at once, open ⋯ More → Sort tasks by urgent & important. Sorting is free and makes no AI call.

Deadlines read from a task's wording

When a task's text states a deadline ("send the invoice by Friday", "report due Oct 28", "deadline: Monday") and you haven't set a due date, Tasks shows a dimmed Looks due … chip on the row. Click it to make that day the real due date (5 PM). Only deadline words count (by, due, before, until, deadline, no later than), so "notes from Monday's call" is left alone, and past dates are ignored. The suggestion is read on your computer when you add or edit a task, with no AI call. On the Today list it reads Looks due: … so you can tell it from a date you set. It also counts toward "due soon" and the "do this next" pick.

Meeting action items in Caught

When Omniscio writes a meeting's AI notes, each action item that isn't checked off appears in Caught marked "from meeting name". Keep it to make it a task, or dismiss it. Regenerating the notes doesn't add the same item twice, switching templates adds nothing, and nothing is added while Caught is turned off. This uses no extra AI: the items come from the notes you already made.

"You usually keep these"

Once you have kept or dismissed enough suggestions, Caught notices patterns you nearly always keep: a word, a list, or a kind of suggestion. Matching suggestions show You usually keep these; hover it for the reason, such as "You kept 9 of 10 suggestions mentioning 'invoice'". Keep all N matching (or press M in the list) keeps those in one go. Nothing is ever kept without your click, and "looks done" suggestions are never included, because keeping one would check off a real task.

Caught review in the evening close-out

When Caught has suggestions waiting, the evening close-out lists up to five of them, "looks done" ones first, each with Keep (or Check off) and Dismiss, plus Open Caught for the rest. It's optional: Confirm & rest works the same whether or not you touch them, and opening the close-out never changes anything by itself.

For agents

• The urgent/important group is derived when a task is read, from its dials, whenever the task is AI-sourced or never classified and has a dial of at least Low; a user pick (aiClassSource: 'user') is returned unchanged. The sort-all pass is the existing deterministic POST /tasks-v2/classify.
• The read deadline is stored in aiDueAt (a local YYYY-MM-DD) on create and on every text edit; dueAt always wins wherever a deadline is read.
• Meeting items are staged with the provenance meeting:<title> only after a fresh (non-cached) notes generation, gated by the Tasks feature and tasksV2CatchesEnabled.
• GET /tasks-v2/caught/rules returns the mined keep rules and the pending catches they match; it is read-only.
• The close-out section reads and writes Caught only through the existing keep, confirm and dismiss actions, so the close-out summary read stays free and side-effect-free.

Related

• Tasks (markdown outliner, in development) — the overview and every other part.
• Tasks part 12 — About you, classification provenance and the close-out.
• Meetings — where the meeting notes and action items come from.