Tasks
Updated 10/7/2026
Tasks
Tasks gathers the to-dos written in your documents into one agenda: what is overdue, what is due today and what is coming up this week. A task is an ordinary checklist line in any document you own — there is no separate task list to keep in sync.
Turn it on from Settings → Extensions (see guide:extensions-and-settings). A Tasks icon then appears in the sidebar.
Writing a task
Any checklist line is a task:
- [ ] Send the invoice
Give it a date and it shows up in the agenda. On a task line, type @ and
pick a date — Today, Tomorrow, Next week, a weekday — or keep
typing: @oct 12, @fri 3pm, @in 3 days. The date becomes a small chip in
the line:
- [ ] Send the invoice :due[2026-10-02]
That :due[…] text is what the chip stands for, and it is what you would see
in the Markdown source or an export. Click a chip to pick a different date, or
clear it with the date picker's own clear button.
Priority
Use a task's ? ? Priority menu to choose High, Medium, Low, or No priority. You can also write it directly:
- [ ] Send the invoice :priority[high] :due[2026-10-02]
Priority appears as a chip in the editor and reading view, and as a badge in workspace task lists. Tasks with the same due date and time sort high, medium, low, then tasks without priority. A priority does not give an undated task a date.
Repeating tasks
Choose ? ? Repeat for daily, weekly, monthly, yearly or every two weeks. You can also write a custom interval in Source, with a number from 1 to 365:
- [ ] Weekly review :due[2026-10-06] :repeat[weekly]
- [ ] Water plants :repeat[after 3 days]
- [ ] Review finances :due[2026-10-31] :repeat[every 2 months]
With Tasks enabled, completing through a checkbox or a task control keeps the
completed occurrence and creates one new task after it. Fixed schedules use the
old due date and skip missed dates; after intervals use the day you complete
it. Undated recurrences start from the completion day. Monthly/yearly rules
remember the intended day and use a month's last day when needed. Vault records
that intent as monthly on 31 or yearly on 02-29 in the next occurrence.
Notes and subtasks carry forward. Completed subtasks reset in the new checklist; unfinished work moves forward, with its old copies cancelled so it does not appear twice. Already-cancelled subtasks stay cancelled. A recurring parent controls its whole checklist's cadence, including children with repeat rules.
Choose Does not repeat on the active occurrence to stop the series. Archived
occurrences have their repeat fields removed, so ticking history again does
not create extra tasks. Typing x in Source, or ticking with Tasks disabled,
only changes the checkbox; it does not create a new occurrence.
Four states
| Box | Meaning |
|---|---|
[ ] | open |
[/] | in progress |
[x] | done |
[-] | cancelled |
Click a box in the editor to tick it or untick it. With Tasks on, ticking also
records the day you finished it, as :done[…].
In Read mode, editors can also tick boxes, including nested tasks and tasks
inside a region. Readers without edit access cannot tick boxes.
The agenda
The Tasks sidebar lists:
- Overdue — open tasks whose date has passed.
- Today — tasks due today, plus anything you ticked off today.
- Next 7 days — what is coming up.
- Inbox — tasks in your Inbox that have no date yet.
Click a task to open its document at that line. Tick its box to complete it, or use the ⋯ menu to move it to today, tomorrow or next week, pick a date, clear the date, set a priority, mark it in progress, or cancel it. Every change is written back into the document itself, so collaborators see it straight away.
Undated tasks in your other documents stay out of the agenda on purpose; otherwise every old checklist would crowd it. Give a task a date to schedule it.
Only documents you own feed your agenda. Tasks in documents others have shared with you are not included.
Tasks around the workspace
- Home page. The new-tab page shows a Today section — overdue tasks and tasks due today — that you can tick off without opening anything.
- Document side panel. Each document's side panel has a Tasks section: how many are open, the next due date, and the open tasks with their subtask progress. Click one to jump to it.
- Subtask progress. A task with nested subtasks shows how many are done,
such as
2/4, in both the editor and the reading view.
Task lists inside a document
Type /tasks to insert a live task list, or write the block yourself:
:::tasks{due=week}
| Option | Values | Default |
|---|---|---|
scope | doc (this document's tasks), all (your tasks everywhere) | doc |
due | any, overdue, today, week, month, none | any |
status | open, done, all | open |
tag | a document tag | — |
title | a heading for the block, in quotes | — |
week and month include anything already overdue. A scope=all block always
shows the reader's own tasks, never yours: share a "My week" document and
each person sees their own week. On a public page it shows a short note
instead.
Capturing a task quickly
Type into Add task… at the top of the Tasks sidebar, or press
Ctrl/Cmd+K and type /task followed by the task:
/task send invoice friday
/task call Sam tomorrow at 9am
/task pay rent @oct 1
The task is added to your selected capture document, with the date taken from the end
of what you typed. Only clear dates are picked up — "call Tom" stays "call Tom"
rather than becoming a task for tomorrow; put @ in front of a date to make it
explicit. A confirmation appears with an Undo button.
Under Settings → Tasks → Quick capture destination, choose Inbox or
Daily note. Daily note capture reuses your root-level document titled with
today's local date (such as 2026-10-06), creating one if needed. An undated
task captured there gets :due[today] so it appears in Today's agenda; an
explicit date in the task stays as you entered it.
The Inbox is an ordinary document, created the first time you capture something. Rename it or move it into a folder as you like; if you delete it, the next capture starts a new one.
To capture into a different document you own, open Settings → Tasks and choose it under Inbox document. Choosing Create an Inbox automatically clears the pointer; the next capture creates a fresh Inbox document.