Fran1 downloadsTasks and periodic notes for Obsidian: schedule plain Markdown tasks into day, week, month, quarter and year notes.
Tasks and journal notes for Obsidian. Your tasks stay plain Markdown checkboxes in your own notes: type > to schedule one, and it shows up in that day's, week's, month's or year's note.
Requires Obsidian 1.13.0 or newer.
i-am-fran/obsidian-klaar in the BRAT plugin and enable Klaar.main.js, manifest.json and styles.css from the latest release into <vault>/.obsidian/plugins/klaar/, then enable Klaar in Settings → Community plugins. To check the files were built from this repository: gh attestation verify main.js --repo i-am-fran/obsidian-klaar.Klaar reads the Markdown files in your vault, on your device, to find tasks. It makes no network requests. Found a bug? Please report it.
>. On a task line, type > and pick Today, Tomorrow, a weekday, a week, a month, a quarter or a year. Klaar writes a link like >[[2026-10-23]] or >[[2026-W43]]. "Move task to…" does the same from the command palette or right-click menu.#p1, #p2, #p3 and #bugs (or your own tags) become coloured pills. Commands cycle priority and toggle in progress.>[[2026-10-23]] reads as Fri 23 Oct, Today or Week 43, red when overdue.
| Line | Meaning |
|---|---|
- [ ] text |
open |
- [x] text |
done (Klaar can add (@done [[YYYY-MM-DD]])) |
- [/] text |
in progress |
- [>] text |
next |
- [<] text |
someday |
- [-] text |
cancelled |
Schedule keys: 2026-10-19 (day), 2026-W43 (ISO week, Monday start), 2026-10 (month), 2026-Q4 (quarter), 2026 (year). A task written in a journal note without a > link belongs to that note's period. Any other marker, such as [!], isn't a Klaar task and is left alone.
Journal notes folder (default Daily), which period types are on (quarterly is off by default), the completed date stamp, the [/], [>] and [<] markers, tag colours and roles, and how date chips look.
Klaar is free. If it helps you, you can buy me a coffee:
npm install
npm run dev # watch build to main.js
npm run build # type-check and production build
npm test # vitest
npm run lint # eslint
To release, bump the version with npm version <version> --no-git-tag-version and add a ## <version> section to CHANGELOG.md. When that reaches main, the Release workflow tags it and publishes the release.
MIT licensed.