README file from
GithubDayTasks
A lightweight, day-first task manager for your Obsidian daily notes.

DayTasks is built for people who plan from daily notes but still want structured task cards, filtering, subtasks, dependencies, and optional detail notes. It keeps task data in Obsidian plugin storage and renders tasks inside your daily notes, so your note body stays yours.
plugin task store -> task index -> daily-note widget -> task cards
Stable TSK-xxxxxxxx IDs let cards, detail notes, subtasks, dependencies, and
project links all point at the same task without turning every task into a
Markdown file.
Status
DayTasks is under active development and is being prepared for public release. It is currently desktop-only and English-only.
API, browser extension, sync, and i18n work are out of scope until the Obsidian plugin experience is complete.
Requirements
- Obsidian
1.8.0or newer. - Desktop Obsidian. DayTasks is currently marked
isDesktopOnly.
Features
- Daily-note widget in Live Preview and reading mode.
- Task creation, editing, completion, deletion, status cycling, and priority cycling.
- Scheduled dates, due dates, tags, contexts, project links, estimates, and descriptions.
- Collapsible task cards with manual drag reorder.
- Subtasks with nested cards and progress.
- Dependencies with blocked-status behavior and cycle prevention.
- Task List view for all tasks across days, with filtering, grouping, sorting, and persisted view state.
- Optional Markdown detail notes with managed task frontmatter and a user-owned body.
- Detail-note folder templates such as
Tasks/{{year}}/{{month}}. - Theme-aware styling, visible keyboard focus, and accessible icon controls.
Screenshots
Task List view — every task across days in one place, filterable by status, tag, context, and project, then grouped and sorted however you work.

Create and edit tasks — one dialog for scheduling, priority, due date, estimate, tags, contexts, project links, subtasks, and dependencies.

Commands — open the Task List or create a task for the current daily note straight from the command palette.

Detail notes — an optional Markdown note per task. DayTasks manages the task frontmatter and injects an interactive subtasks widget; the note body stays yours.


Settings — daily-note detection, which fields the widget shows, and the defaults applied to new tasks.

Install
DayTasks is not yet listed in Obsidian Community Plugins.
For local testing, build and install into the bundled test vault:
npm run build:test
To install into another vault:
npm run build
npm run install-plugin -- /path/to/Vault
The plugin is installed to:
<vault>/.obsidian/plugins/daytasks/
When GitHub releases are available, install by copying the release assets
manifest.json, main.js, and styles.css into that same folder.
Usage
- Enable DayTasks in Obsidian.
- Open a daily note named with a
YYYY-MM-DDprefix, such as2026-06-25.md. - Use the daily-note widget or the
Create task for current daily notecommand to create a task. - Open the Task List view from the ribbon icon or the
Open task listcommand to review tasks across days.
See Features, Settings, and Troubleshooting for the full workflow.
Support
- Bug or feature request? Open an issue — the bug form asks for your DayTasks/Obsidian versions, steps to reproduce, and any console errors so it can be fixed quickly.
- Question, idea, or want to share your setup? Use Discussions.
When reporting a bug, the console log helps most: open the developer console with
Ctrl/Cmd+Shift+I, reproduce the issue, and paste any DayTasks errors.
Data Model
DayTasks stores tasks in Obsidian plugin data, not in daily-note bodies. Optional detail notes are normal Markdown files in your vault. DayTasks manages their task frontmatter and leaves the note body untouched.
See Core concepts and Privacy for details.
Documentation
- Documentation index
- Core concepts
- Features
- Settings
- Roadmap
- Architecture
- Testing
- Security and data safety
Development
Install dependencies, then run the local gate:
npm install
npm run check
Useful commands:
npm run check
npm run lint
npm run lint:md
npm run build
npm run build:test
To install the built plugin into a vault:
npm run install-plugin -- /path/to/Vault
Release
Bump and tag locally, then push — GitHub Actions builds, attests build provenance, and publishes the release with the assets attached.
npm run release -- patch # bump, check, build, roll notes, commit, tag
npm run release:publish # push the tag -> CI builds, attests, publishes
See Release process for details.