Obsidian Tasks Plugin: Setup, Queries, Due Dates & Project Workflows

The Obsidian Tasks plugin turns Markdown checkboxes into queryable tasks. It can find open work across a vault, filter by dates, tags, paths, and priorities, and update the source task when you complete it from a query view.

Tasks is not a project database. It answers “which actions match this filter?” A project note, meeting note, or daily note still supplies the context behind each action. This guide shows the smallest useful setup, copy-paste query patterns, recurring-task behavior, and the point where a dedicated project or daily-planning view becomes more useful than another query block.

Quick answer: is Tasks the right tool?

Use the core Markdown checkbox when you only need a short list in one note. Add Tasks when you need the same actions surfaced across notes with dates, priorities, recurrence, or filters. Use a project note for scope and decisions, then link its actions into Tasks queries.

Need	Best starting point	Why
A short checklist in one note	Markdown checkbox	No plugin or metadata required
Open work across daily, project, and meeting notes	Tasks	Queries read task metadata stored in Markdown
Milestones, decisions, and project context	A linked project note	A task query cannot explain the project outcome
Cross-project execution and review	Obsibrain daily planning	Surfaces work without building every dashboard yourself
Structured project organization	Obsibrain smart projects	Keeps project context connected to active work

Install and create the first task

Install Tasks from Settings → Community plugins → Browse, then search for “Tasks” and enable it. The official repository is the source for the current installation guidance and release links.

Create a task in any Markdown note:

- [ ] Send the project brief 📅 2026-08-07 ⏫ #project/website

The checkbox is the task. The emoji markers add metadata that Tasks can query: 📅 for a due date, ⏳ for a scheduled date, 🛫 for a start date, priority markers such as ⏫, and 🔁 for recurrence. Tags and paths are conventions you choose, so keep them consistent across notes.

Start with one task format and one naming convention. Do not create a separate dashboard, tag taxonomy, and automation layer before you have a real question that needs one.

Four query starters

The examples below are documentation-verified against the Tasks query examples and filter reference. Replace Meetings, Inbox, and #project/website with names from your vault.

Open tasks due today

not done
due today
sort by priority
sort by due

Overdue and due today

not done
due before tomorrow
sort by due
limit 50

Open actions from meeting notes

not done
path includes Meetings
sort by due
group by filename

Open work for one project tag

not done
tags include #project/website
sort by due

Tasks query instructions are line-based. When you combine alternative conditions, use parentheses so the result matches the question you meant to ask:

not done
(due after yesterday) AND (due before in two weeks)
(tags include #inbox) OR (path includes Inbox)

The official guide documents more filters for dates, descriptions, headings, paths, tags, statuses, and file properties. Narrow a query with a path, tag, date range, grouping, or limit when it returns more work than you can review.

Recurring tasks and dates

Recurring tasks use 🔁 followed by a rule beginning with every:

- [ ] Review active projects 🔁 every Friday 📅 2026-08-07

When you complete a recurring task, Tasks keeps the completed occurrence and creates the next one. The official recurrence guide also documents when done, which calculates the next occurrence from the completion date rather than the original task date.

Monthly recurrence deserves care. every month and every month on the last do not express the same rule when months have different lengths. Use the explicit rule that matches the work, and check the resulting date before relying on it for a deadline.

A practical project workflow

Tasks works best as the retrieval layer around notes that hold context:

1. Capture the action where it occurs: a daily note, meeting note, project note, or research note.
2. Write one clear next action. Add only metadata you will query, such as a due date, priority, tag, or recurrence rule.
3. Link the task’s source to the relevant project or person instead of copying its context into every dashboard.
4. Review one focused query each day and clean stale dates during a weekly review.

For a broader Obsidian setup, see task management in Obsidian and Obsidian project management. Those pages cover system structure; this page focuses on the Tasks plugin itself.

Troubleshooting checklist

Symptom	Check first	Practical fix
Query returns no tasks	The source line starts with - [ ] or - [x]	Add one simple checkbox in a test note, then broaden the query
Project query is empty	path includes and tags include match the vault	Copy the folder name or tag from an existing task; test one filter at a time
Recurring task gets an unexpected date	Original-date behavior versus when done	Choose the recurrence rule deliberately; use an explicit monthly rule when needed
Query logic is too broad	AND and OR grouping	Add parentheses and verify each clause separately
Task list is overwhelming	Query scope is too wide	Add a path, tag, date range, grouping, or limit
A query behaves differently after an update	Plugin version and release notes	Reopen the vault, check the current documentation, and reproduce the smallest failing query

Community reports show why these checks matter. Users often want meeting actions, project subtasks, assignees, and energy-based views in one dashboard, but those conventions still need to be designed in the vault. Tasks can filter the Markdown metadata you add; it does not infer project ownership or meeting context for you. The Tasks GitHub repository and its user guide should take precedence over older tutorials when syntax changes.

Keep the system maintainable

Tasks is useful when it reduces the cost of finding and updating work. It becomes another maintenance project when every note uses a different tag scheme, query style, and recurrence convention.

• Start with one task format and one project convention.
• Keep task context in the source note; use queries for retrieval, not duplicate documentation.
• Keep one daily execution view and one weekly review view.
• Update one plugin at a time and keep a backup before workflows that rewrite notes.
• Add complexity after real work exposes a gap, not because another plugin list recommends it.

For a ready-made local-first workflow around capture, projects, daily planning, and reviews, explore Obsibrain and its periodic reviews. The useful question is whether the system helps you act on captured work, not whether it has the most query blocks.

Sources and current documentation

• Tasks User Guide — installation, task syntax, queries, filters, and recurrence.
• Tasks query examples — due-date, path, tag, sorting, grouping, and limit examples.
• Tasks filter reference — date, text, status, path, and property filters.
• Tasks GitHub repository — current feature scope and release links.
• Obsidian community plugins — official installation directory.

This article separates documentation-verified behavior from workflow recommendations. Plugin behavior can change; check the linked documentation when a query or recurrence rule is important to your work.