A separate task app is one more place to keep in sync. Daneshbase keeps tasks where the context already is — inside the wiki doc that explains why they exist.
Drop a markdown checkbox anywhere in any doc:
- [ ] Re-evaluate grind size on the current bag
- [ ] Descale the kettle
The indexer picks them up automatically. The dedicated tasks page lists every open box across your whole wiki, each one deep-linked back to the section it lives in. Mark it [x] in the doc, the task disappears from the list. No double-entry, no syncing.
Recurring schedules — written inline
Add a <due:...> tag on the task line and Daneshbase handles the schedule.
- [ ] Descale the kettle <due:2026-06-20 rrule:"FREQ=MONTHLY">
The format is RFC 5545 — the same standard your calendar uses. Daily, weekly, monthly, "every other Tuesday", "first Monday of the month" — all expressible as one inline string. The AI agent writes these for you when you describe a routine in plain language.
Push notifications when something is due
Reminders fire as web push notifications to every device you've installed the app on. Minute-resolution cron runs in the background, so a task due at 9:00 fires at 9:00 — not whenever you happen to open the app.
Marking done halts recurrence
For recurring tasks, [x] is the kill switch — no more reminders for that task. To pause without losing the rule, edit the rrule: instead. Everything happens in the doc body; nothing to manage in a separate UI.