Disclaimer
Is this plugin open source? Yes
Is this plugin completely free? Yes
Is this plugin vibe-coded beyond the author’s ability to comprehend how it works? No
Community Directory:[Task Wheel](https://community.obsidian.md/plugins/task-wheel)
Task Wheel - see every open task once, on purpose - feedback welcome!
Your task list has outgrown you. This gives it a shape that has an end.
You know the feeling: you open the list for your weekly review, you scroll, you lose your place, and somewhere around the third screen reviewing quietly turns into skimming. And skimming is how things slip. The problem is not that you lack a task manager … you probably have one or more of those. The problem is that a list of five thousand items has no end you can reach, so “I have been through everything” is a feeling rather than a fact.
Task Wheel gives your open tasks a shape that does have an end: one visual overview of everything still open, drawn as a circle. Every task is a stop on a wheel you turn. The angle is the part of your life it belongs to; the distance from the centre is how deep it sits in your notes. You turn, each task comes past a fixed reading wedge at the top, and the circle closes. Made for weekly review, or any moment you need certainty rather than speed.
The wheel over a whole vault. Domains are wedges, tasks are stops, and the reading wedge sits at the top to indicate the active task. The card at the bottom displays the full task and options to mark it as done, cancel it, postpone, move it etc.
Try it in 60 seconds — free, everything local
- Install & enable: Community plugins → search for Task Wheel.
- Open it: the ribbon icon, or the command Open the wheel. Your top-level folders become the wedges; no setup, no format to learn.
- Turn it. Drag, scroll, or ← →. Each stop is one task, on the card in front of you. When the circle closes, you are done, and you know it.
No account, no API key, nothing ever leaves your machine.
Why a circle, and not a better list
Two properties make the round mean something, and both are enforced rather than hoped for:
- Position is stable. Every domain gets a fixed slice that does not move with the number of tasks in it. Work grows into its own wedge; empty space is allowed to stay empty. That is what lets spatial memory build up - the client work lives at two o’clock - which is half the value of the idea.
- Nothing disappears silently. A folded branch stays as a stump with a counter. When a filter is on, the wheel says so, and says how much it is leaving out. The wheel may show you less than everything; it may never be quiet about it.
What you get
- It reads the checkboxes you already have. Plain Obsidian Tasks syntax: dates, priorities, recurrence, tags. No format of its own. The Tasks plugin is not required, but when it is installed, ticking off goes through it, so recurring tasks roll over exactly as Tasks would do it.
- A reading card at every stop: where the task sits, what it says, its dates and priority, and the review actions: tick off, mark in progress, cancel, push a week out, raise or lower priority, open the note. The two status buttons are toggles, so a mis-tap on a phone has a way back.
- The same drawing at any size. Two hundred tasks and twenty thousand produce the same amount of drawing: what is under the reading wedge swells and shows its deeper rings, the far side recedes to a silhouette, and the rest folds into stumps that carry counters. Turn towards a stump and it opens.
- A filter that admits what it hides: by words, status, date, priority or tag, in its own panel, with a badge that says how much sits outside the round even when the panel is closed. Changing the filter starts a new round, because a round is a round of that selection.
- A wheel over one folder or one note. Right-click it in the file list (long-press on a phone). Inside a folder the subfolders become the wedges; inside a note its headings do — the wheel is that note’s outline, empty headings included, so “phase 3 has nothing in it” is something you can see rather than something that is simply missing.
- Structure editing where it belongs. In a note’s own wheel you can move a task among its siblings, send it to another heading (typing a name that does not exist offers to make it), add one, or rename it. Prose stays in the note; the wheel does structure.
- Carrying work into another note: copy or move a task, or a whole heading with everything under it, into another note, and the category travels with it: a task under
Werk › Klantenlands underWerk › Klantenover there, writing whatever part of that path is missing. - Not every checkbox is a task. A list of acceptance criteria in a template is a document’s checklist, not work on your plate. Tell the wheel once: by note
typein the front matter, or by heading name, both with*patterns. There is also a command that shows you exactly what those rules take out, so a silent rule is still a debuggable one. - Thirteen languages in the help panel, following Obsidian’s own language setting.
What Task Wheel is not
A review instrument first, not a task manager. The point is being able to say with certainty that you have seen everything; ticking a task off is possible, but it is not what the wheel is for. So, deliberately: no external task services, no task syntax of its own, no time blocking or calendar, no multi-user collaboration, and no full task editor. Splitting a task or rewriting it belongs in the note which is what open the note is for.
Privacy
Nothing leaves your machine. The wheel reads your vault through Obsidian’s own APIs and writes back to your notes when you ask it to: no network calls, no telemetry, no account. Desktop and mobile. Every release asset carries a build-provenance attestation proving it was built from the published source.
Feedback welcome!
In the last couple of weeks I’ve been developing and refining the current version and I think it is ready for review by others. So … I’d love to hear how it works for you, especially:
- Does the angle = domain, radius = depth grammar match how your vault is actually organised? Folder, tag namespace and front-matter property are all offered as the source of the angle. Is one of those missing for you?
- After a full round, do you believe you saw everything? That is the one claim the whole thing rests on. How does zooming in and out work and clicking through on a domain?
- Is the wheel readable on your phone, and does turning feel right there?
- Where does it get in your way: too many stops, too few, a wedge that is too small to use?
- Any bugs or rough edges you run into?
Feel free to open issues on GitHub or reply here. Task Wheel is free and GPL-3.0; if it changed how you review your work, you can buy me a coffee.
