Master caution
When the work outgrows the day, the readout turns red at 9am rather than at 6pm. You still choose what gives — it will not quietly reshuffle your list to make the arithmetic work.
macOS · iOS · local first
Founder's cockpit for the day.
A native scheduler that reads two markdown files and tells you what today actually looks like: what fits, what does not, and when the wheels come down. No accounts required, no cloud required, no web view.
Your tasks
todos.mdA task is one line of text. That is the whole format.
No database, no export button, no proprietary anything. Open the file in any editor and the app follows along as you type.
- [ ] Draft the metrics section | project: Northwind | effort: 45m | deadline: 2026-09-04 | priority: 1- effort
- How long you think it takes. This is what makes a finish time possible.
- deadline
- Sorts ahead of everything else as the date closes in.
- priority
- 1, 2 or 3. Beats the project's own priority when they disagree.
- project
- Carries the weight you set once in
memory.md.
Two more tokens do the unglamorous work: defer: 2026-09-01
pushes a task out of today without deleting it, and carried: 4
counts how many times you have hauled it forward. Four is usually the app
telling you something.
Your day
14:30Wheels down is a time, not a wish.
Add up the effort left, drop it into the hours you actually work, and the deck tells you when today runs out. It moves as you clear things.
Calibration
Every finished task is logged with the time you finished it. Guess 30m on a project you reliably spend an hour on, and the estimate gets multiplied before it reaches the clock.
Your agent
14 toolsNothing to install. It is already connected.
Daymetric carries its own MCP server and registers it with Claude Code, Claude Desktop, Cursor and Codex the first time you open the app. Then you say this:
“what's on my deck in daymetric?”
list_tasksget_taskadd_taskupdate_task_notescomplete_taskuncomplete_taskremove_taskadd_idearead_memoryread_done_logupdate_memoryset_capacityset_projectwrite_briefing
Proposals, not surprises
Anything it thinks of by itself arrives as
- [?] and waits. Accept or reject it in the app. Your
agent cannot put work on your day without you seeing it first.
Turn it off and nothing breaks
The scheduler is plain Swift with no network calls in it. Your agent writes the same markdown you do, so the app behaves identically with no agent attached at all.
Ready when you are