Phil Palmieri702 downloadsAggregate your native markdown tasks into one fast dashboard, organized by their Projects, People, and Areas context. No separate database, no special files, no rules to adopt.
Task management that works the way you already work.
Taskgregator isn't another task system to adopt. It reads the plain markdown checkboxes you already write, wherever you already write them, and gives you fast, focused views of your work without asking you to change a thing.
No separate database. No special task files. No syntax to learn. No rules to follow. Your notes stay exactly as they are, and your tasks stay on the lines where you typed them. Taskgregator just aggregates, organizes, and surfaces them so you can see everything from different angles and act on it in place.
Think Things, Todoist, or TickTick, but pointed at the notes you already have instead of a silo you have to feed.

Most task plugins make you pick a side: adopt a whole new system, or scatter each task into its own document with its own metadata block. Both make your notes serve the tool.
Taskgregator flips that. The tool serves your notes.
- [ ] thing, you're already using it.Projects/Website Redesign.md belongs to that project. A task that mentions [[People/Alex]] belongs to Alex too. You don't tag it; the location and links already say it.
Everything reads from one shared index, so a selection you make in one place is reflected everywhere.
A search box at the top of the navigator filters tasks as you type. It scopes to whatever is selected, so you can search within a single project or across everything by picking All first. A Searching 'foo' in callout with a clear action stays on the list, and the filter persists as you switch between lists so you can carry the same query around. Clear it with the × in the field or Esc.
Group by project, sort by whatever you care about, and jump straight back to the source note from any card (shown above). Sort and Group are two rows of small pills; Sort pills are tri-state (click to cycle ascending → descending → off, back to the default priority order), and Group is single-select. Right-click any row for the same quick actions you get in the editor: priority, dates, #today, detail note, or cancel.

While you're writing a note, the right sidebar shows that note's tasks, so you never lose track of what a page owns. A subtle All · Overdue · Today · Soon due filter sits above the scope tabs and narrows the current scope by due window (windows with nothing in them are dimmed). Your scope and filter choices stick for the session.

Page shows the tasks written on the note in front of you.

Reference shows tasks living elsewhere that link to this note, so inbound work surfaces too.

Section rolls up a whole subtree. On a folder note (a file named after its folder), you get every open task beneath it in one list.

Because Taskgregator understands your task lines, you get a context menu on any task line in the normal editor, not just inside the plugin panel. Set priority, add a due date, toggle #today, open a detail note, or reveal the task in the task list.

Projects, People, Areas). Files become sub-nodes; parent nodes aggregate everything beneath them.[[People/Alex]] appears under Alex's node even though it was authored elsewhere.
[priority:: high] fields, so it stays compatible with whatever you already use.[due:: ], [priority:: ], etc.), so every smart list, filter, sort, and grouping works no matter how a task was written. When it writes back it follows your Task metadata format setting (Auto follows the Tasks plugin) and keeps each existing line in its own format.^id) only when you enrich it, and the sidecar backlinks to the source line. The raw id is hidden on the page: it shows as a small 📝 note icon in both Reading view and Live Preview (click to open; put your cursor on the line to reveal the id). A 📝 chip on the card opens it too.Taskgregator reads standard markdown checkboxes and Tasks-plugin emoji metadata. Nothing here is required; add only what's useful to you:
- [ ] Open task
- [/] In progress
- [x] Done ✅ 2026-06-30
- [-] Cancelled ❌ 2026-06-30
- [ ] With metadata 📅 2026-07-01 🛫 2026-06-25 🔼 #followup
- [ ] Linked to a person [[People/Alex]] and a project [[Projects/Website Redesign]]
Recognized signifiers:
| Signifier | Meaning |
|---|---|
📅 YYYY-MM-DD |
Due date |
🛫 YYYY-MM-DD |
Start date |
⏳ YYYY-MM-DD |
Scheduled |
➕ YYYY-MM-DD |
Created |
✅ YYYY-MM-DD |
Completed |
❌ YYYY-MM-DD |
Cancelled |
🔺 ⏫ 🔼 🔽 ⏬ |
Priority (highest → lowest) |
#tag |
Smart-list membership |
[[link]] |
Cross-index target |
^blockid |
Stable identity, added lazily when you attach a note (hidden on the page, shown as a 📝 icon) |
If you (or the Tasks plugin) write metadata as Dataview inline fields instead of emoji, Taskgregator reads those too, so both styles work interchangeably in every list, filter, sort, and grouping:
- [ ] With dataview metadata [due:: 2026-07-01] [start:: 2026-06-25] [priority:: medium] #followup
- [x] Done [completion:: 2026-06-30]
Recognized fields: [due:: ], [start:: ], [scheduled:: ], [created:: ], [completion:: ] (done date), [cancelled:: ], [repeat:: ], and [priority:: highest|high|medium|low|lowest].
When Taskgregator writes a date or priority, the Task metadata format setting decides the style: Auto (default) follows the Tasks plugin's own configured format, falling back to emoji when Tasks isn't installed; you can also force Emoji or Dataview. Either way, a line that already carries metadata keeps its existing format, so the two styles never get mixed on one line.
⋯ menu (or right-click) for dates/detail-note/cancel, a chip to jump to its source, or the 📝 chip to open its detail note.Projects, People, Areas).Dailies).p1, p2, p3).Name:tag pairs).Taskgregator/tasksData).
Taskgregator only reads markdown files inside the folders you configure as bucket roots and inbox roots (by default Projects, People, Areas, and Dailies). It walks those folders directly rather than enumerating your whole vault, so files outside your configured roots are never opened. It does not make network requests, and it only writes back to the specific task lines and optional per-task detail notes you act on.
MIT © Phil Palmieri