Tasks (markdown outliner, in development) (part 4)
Tasks doesn't just show deadlines and snoozes on the row — it tells you when they come up. A quiet background check (running whenever Tasks is on) raises one Inbox alert the moment: a task's deadline arrives (its due date/time passes), or a snoozed task comes back (its snooze runs out).
On this page
What it is
This is part 4 of the Tasks (markdown outliner, in development) page. It carries the next stretch of the material on that page, moved here because a single page is capped at 40,000 characters.
Where to find it
Reach this part through Tasks (markdown outliner, in development) — it lists every part and explains where the feature lives in the product. Everything below is reached from the same place.
How it behaves
Everything below is the behaviour, detail and edge cases that belong to this stretch of the Tasks (markdown outliner, in development) page.
Deadline & snooze reminders
Tasks doesn't just show deadlines and snoozes on the row — it tells you when they come up. A quiet background check (running whenever Tasks is on) raises one Inbox alert the moment:
- a task's deadline arrives (its due date/time passes),
- a task's deadline is coming up soon (within the Tasks "due soon" window, 24 hours by default; set it to 0 to turn these off), or
- a snoozed task comes back (its snooze runs out).
The "due soon" card follows the window you set, in both directions: narrow the window (or push a deadline further out) and a card that no longer fits is cleared rather than left standing, and the task is re-armed so the card is raised again when the deadline does come inside the new window. It is cleared, not cancelled — you get one card per deadline, at the right time.
Each alert shows the item and where it lives in your project — the project name on its own line at the top, then any parent tasks stacked beneath it as an indented outline, so you see the full path down to the item — plus two buttons: Open in Tasks (opens that task in its own list, highlighted and scrolled to the middle — and on a phone it also switches you to the Tasks screen; it always lands on the Tasks tab, returning the panel from its Sessions tab and closing any chat or interview you had open there) and Drop task (files the task away and clears the alert). The four reminder kinds share one Turn off these alerts switch: turning it off on any of their cards mutes all four — due, due soon, back from snooze and follow-up — and the email, text and phone reminders with them. Turn it back on in Settings → Notifications → Alert types. The cards Tasks sends with Send to inbox carry an Open in Tasks button too. Each kind of alert gets its own card key, so two kinds of alert for the same task never merge into one card; the button reads the task id back out of that key when you click it.
Snoozing any of these cards
re-snoozes the whole task until the time you pick and clears the card: a deadline, due-soon,
back-from-snooze or follow-up reminder, a card from Send to inbox, and a card a trickle
delivered. It genuinely defers the task instead of only hiding the notice, which is why it no
longer just comes right back, and Undo puts both back. A card that is not about one task (the
evening close-out, a launch or service warning), a trickle card whose task was archived when it
arrived, and a snooze an inbox rule makes only hide the card. Each reminder fires once per
event (re-scheduling a deadline re-arms it for the new date), it's free (no AI), and a big
backlog of already-due / already-back items trickles in a few a minute rather than flooding you.
Finishing, filing away or deleting a task tidies up after it: its deadline card clears and the
deadline is re-armed, so reopening an overdue task reminds you again; a snooze on the task itself
is switched off (Undo puts it back), so restoring it later never raises a stale "back from
snooze" card; and an AI draft is ready card for it clears too. Snoozing a card for a task
that is already finished just clears the card. (reconcileTasksV2ReminderAlerts in
tasks-v2-reminder-reconcile.ts; disarmRootSnooze in named-tx-tasks-v2-lifecycle.ts.)
The reminders appear in their own Tasks section of your Inbox, not the shared Alerts pile, with the project name shown inside; clicking the section header opens Tasks.
Omniscio has to be open. Reminders come from the Omniscio desktop app, so they only fire while it is running. If it was closed or your computer was asleep when something came due, the deadline, due-soon and back-from-snooze reminders arrive as soon as you open it again (a few a minute if there are many), overdue deadlines first and a backlog of "due soon" cards behind them, and follow-up reminders about a minute later. Meeting alarms are different: one that is more than 30 minutes late by then is skipped rather than ringing late.
Reminders by email, text and phone
The same four reminders (due, due-soon, snoozed-task-is-back and follow-up), and every meeting heads-up, can also reach you away from your computer. Each channel has its own switch on the Tasks settings page (search Settings for it), and the reminder always lands in your Inbox too:
- Email me task reminders — default off. Sends the reminder to your agent email address, so you need to be signed in and have one set.
- Text me task reminders — default off. Texts your alert phone number through Twilio, so Twilio has to be set up first.
- Send task reminders to my phone — default on, and it only does anything once a phone is paired or a browser has turned on notifications through Web Access. The phone buzzes with the task's reminder (with content-free phone notifications on, the default, the phone app shows only "A task needs you", while a browser notification still shows the task's own text). Tapping it in the web app opens Tasks on that task, whether the app was already open or not. Two different tasks that come due together both buzz; the same reminder never buzzes twice. A browser that subscribed to notifications through Web Access counts as a phone here too, so it gets the reminder even when no phone app is paired.
A reminder only goes to phones your own account paired. Each phone pairing remembers the Omniscio account that was signed in on the computer when the phone turned on notifications, and a task reminder is sent only to that account's phones. A phone that turned on notifications before pairings remembered their account has no account on record, so it stops getting task reminders. The first time such a phone opens the web app, it shows a one-time notice at the top: "Re-pair this phone to keep getting task reminders." Tapping Re-pair sends that phone's own notification subscription again, so it is saved under the account signed in on the computer, and the notice goes away. It shows once per phone: a phone that dismisses it, or opens the app again later, is not asked again, and a phone whose pairing already has an account never sees it. Nothing attaches an account to a pairing unless someone taps Re-pair on that phone. If the re-pair cannot be confirmed (for example the connection dropped), the notice stays up with a Try again button. The notice lives in the web app, so it reaches phones that get notifications through Web Access; a native phone-app pairing made before the change has no screen here to show it.
The same switch also sends three Tasks cards to the phone, and only to the phone (never email or text):
- An AI draft is ready — when a "Do it for me" draft comes back. Tapping it in the web app opens Tasks on that task with its Review draft panel already open, so you can read it and accept or discard it right there.
- A draft didn't finish — when a "Do it for me" draft fails: it ran out of time, its session ended before a draft, or the finished draft could not be saved.
- Task agents keep failing to start — when three agents in a row fail to start. It buzzes once when the card appears, not again on each later failure, and tapping it opens the app.
Quiet hours and Do Not Disturb keep the phone silent, and email and text follow quiet hours, repeat suppression and the hourly send caps like every other off-screen alert. If you have set a channel for one specific reminder type in the alert channel settings, that choice wins over these switches. Apart from the three cards above, failure cards — Drip and heal cards among them — never leave the screen.
If the card reached your Inbox but the email, text or phone buzz never came, the troubleshooting table on the Tasks page has the log lines to search and the switches to check.
Waiting on someone — the follow-up clock
Some tasks aren't blocked on you — they're waiting on someone else (a reply, a delivery, a sign-off). Tasks lets you mark that, then quietly reminds you to chase it so it doesn't slip:
- The ⏳ "waiting" toggle sits with the row's other action icons on the right and appears when you hover the row, so a resting row stays clean — just its number + text (it's shown plainly on the focused row, and on the focused row on a phone). Click it to open a clean centered popup (the same style as the Snooze popup): type who or what you're waiting on — and the people and things you've waited on before drop down as a clickable list from the name box (it appears when you click into or type in the box, and floats over the popup instead of pushing it bigger) to fill it in — optionally type when to be reminded to chase it in plain language ("in 2 days", "next friday", or a quick preset — the same smart date box the due-date field uses, with a live preview of the exact date), and confirm — or just press Enter to mark it waiting without a name. Marking it starts a follow-up timer at the reminder time you picked, or 2 days out by default if you left it blank, saved on the task so it holds even if you never reopen it. The name's first word is capitalized automatically — like your task titles, "sarah" is saved as "Sarah". Once a task is waiting, the same ⏳ popup shows the current reminder and lets you edit who, set a new reminder time (which re-schedules the chase), or Clear waiting — and a time it can't read is refused with a small hint rather than saved wrong.
- A waiting task tucks into a "Waiting" section — exactly like Snoozed. The moment you mark it,
the task leaves the main list and collects under a single collapsible ⏳ Waiting (N) row
pinned at the bottom (below the Snoozed section), so your list stays focused on what you can act
on now. Open the section to see your waiting tasks grouped under the person or thing you're
waiting on (see the next point), each rendered just like a regular numbered task row with a
calm waiting chip (or a gentle amber follow up once the follow-up date passes — a nudge,
not an alarm; amber "Needs You", never red) and a "+N sub-tasks" count. A chase date shows as a
short weekday (e.g. "Fri") only within the coming week; a week or more away, or already past, it
shows its short month/day instead — a bare weekday can't tell you which week, and the follow-up
instant is a full UTC moment that is first projected onto your LOCAL calendar day, so an evening
west of UTC never reads a day late. To drop one back into your
list, open the row's ⋯ menu and choose Clear waiting — the old always-on button is gone, so
the rows stay calm and read like any other task. The same menu's Open details (or a click on
the row) opens that waiting task's details panel, and it stays open: the highlight is placed on the
waiting row itself, and only a row that actually LEAVES the list (snoozed or marked waiting while
highlighted) moves the highlight on to its neighbor. Snoozed rows behave the same way. This works in your per-project lists and the
All Projects view (one section per project); the Today plate keeps waiting tasks inline
(they show the full
waiting · <who>/follow up · <who>chip on the row). A task that's both snoozed and waiting shows under Snoozed only. - The section always groups by who — each person/thing a numbered top-level row. Every person or thing you're waiting on becomes its own numbered top-level row (1. Dana, 2. Alex) with a count and a collapse chevron, and the tasks you're waiting on nest beneath it, numbered one level down (A., B.) — so you see who you're chasing at a glance. The person you most need to chase floats to the top (any overdue follow-up leads). This happens even for a single person — one numbered group, not a flat list; anything with no name set collects in a muted "No one specified" group at the bottom. Because the person is named at the top, the tasks beneath drop the redundant "· <who>" and just read waiting / follow up. Applies in your per-project lists and the All Projects view alike.
- You can also name who you're waiting on (and change the follow-up date) in the task's details pane — the same fields the ⏳ popup writes; leave the date empty for a calm reminder with no nudge.
- If that date passes while you're not looking at Tasks, a one-time inbox reminder appears,
titled
<task> — follow up with <who>, with Open in Tasks and Archive. It fires once per horizon — moving the follow-up date re-arms it — and, because Tasks works on your phone, the nudge reaches mobile too. - Your daily check-in also learns who you're waiting on and who's overdue to chase, so it can gently remind you to follow up.
This mirrors the Tasks follow-up clock: while Tasks is on, a background scan runs about once a minute over the waiting tasks whose follow-up time has come, and each one raises a chase card in your Inbox — with Open in Tasks and Archive buttons, and no passing toast, so it waits for you. Each task is chased once, not on every scan.
Always-on outline numbers
Every visible row carries an outline number — the same size and weight as your task text, with a
trailing period — just to the right of its checkbox: top level 1. / 2. / 3., children
A. / B., grandchildren roman i. / ii., great-grandchildren a. / b., then the
marker style keeps cycling by depth (1. → A. → i. → a., then repeats).
Each row shows only its own marker (a child reads A, not 2A) — the indentation shows
which parent it belongs to, like a classic outline: a sub-item is indented so its own marker
lines up under the start of its parent's text (each nesting level steps in by the parent's
marker gutter, not a token amount). It is always on and follows whatever
sort/filter you're viewing (and a drilled-in view renumbers from 1), so the number always
matches what's on screen. You see the numbers in both the default "All Projects" view
(where each project is numbered on its own, starting from 1) and a single-project view.
The labels are computed purely from the visible rows and rendered as
a number the same size and weight as your task text, with a trailing period (1. / A. / i.),
in a gutter kept out of the task's own markdown — so a row whose text is itself a markdown
list never clashes with its number. The checkbox sits to the left of the number, and the
number sits on the row's first line beside the text (it never floats above the text like a
superscript); on a task that wraps onto several lines it stays beside that first line.
Visual skin — Liquid Glass
Tasks renders in a Liquid Glass skin: frosted panels, soft refraction edges, and a restrained accent glow. It is theme-aware and accent-derived — the glass fills track the surface palette and the tint/glow track the user's accent (--accent-rgb), so it follows the active light/dark theme and chosen accent rather than a fixed dark/teal look. backdrop-filter blur runs on the big panels only (the list rail, the master-context card, the menus); the row "bubble" (fill + border + sheen, no per-row blur) rides only on the active row — the one you're focused on or have multi-selected — so the rest of the list renders flat and long lists stay smooth, and the blur drops on mobile and under reduced-motion.
The skin is isolated to Tasks — none of its styling or class names reach another screen.
The only desktop right pane the list can show is the M4 Break-it-down interview (interviewTaskId), and no button opens it now: Break it down starts a session in the Sessions tab instead (see part 8). The per-task agent chat has no Tasks-tab pane: it lives in the Sessions tab (see Per-task agent chat); on a narrow screen an explicitly-opened chat still takes over the full screen. Context attachments still live in the modal context pane.
Your tasks and your account
Tasks always works on the tasks of the Omniscio account that is signed in, and it never mixes one account's tasks into another's. A few things you may see happen only because of that:
- On a computer more than one account uses, nothing is taken over silently. Tasks made while nobody was signed in are not handed to whoever signs in next. Instead one inbox card asks whether they are that account's: Yes, they are mine gives every one of those tasks to the account and shows it, and No, not mine changes nothing, so they wait for whoever they really belong to. A "No" is not asked again for that account while the number of those tasks stays the same.
- Signing into another account in the middle of an AI call saves nothing. Plan my day, the daily check-in and the overnight learning pass each read your tasks, wait for the AI, then write. If a different account signs in during that wait, nothing is written: Plan my day and the check-in say "Your account changed while this was loading, so nothing was saved. Open it again to start fresh.", and the learning pass simply runs again later. The new account never picks up the old account's answer.
- An approval for paid Tasks work belongs to the account that asked for it. When an agent asks to launch a task agent, run a check-in, arrange your day or open a plan, the approval card records who was signed in. Answering it while a different account is signed in is refused — "This approval was queued by a different account. Sign in to that account to approve it." — and so is an approval that recorded no account at all. A click never spends for someone else.
Related
The overview, the other parts, and everything else worth reading next all sit on Tasks (markdown outliner, in development).
Last verified 2026-10-24