The deck
Today, in the order it should happen
Tasks are sorted by deadline, then priority, then effort, and packed into your energy blocks: deep work in the morning, lighter work after lunch, admin in the evening. The blocks are yours to set.
macOS · iOS · local first
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.
The deck
Tasks are sorted by deadline, then priority, then effort, and packed into your energy blocks: deep work in the morning, lighter work after lunch, admin in the evening. The blocks are yours to set.
Master caution
Every task carries an effort estimate. When the total runs past your capacity or pushes the finish past your admin block, the readout goes red before you have wasted the morning finding out.
Wheels down
The headline number is when you are done, recalculated as you clear work. Estimates get calibrated against what actually took how long, per project, so the number gets more honest over time.
Your files
todos.md and memory.md, in a folder on your
disk. Readable, greppable, diffable, and version controlled locally.
Nothing is trapped in a database you cannot open.
Daymetric bundles its own MCP server and registers it with Claude Code, Claude Desktop, Cursor and Codex when it launches. No Node to install, no config file to edit, no keys to paste. Open the app and ask your agent what is on your deck.
The scheduler itself is plain Swift with no network calls. Judgment comes from your agent writing to the same markdown files you do, which means the app still works exactly the same with the agent turned off.
Proposals, not surprises
Anything your agent thinks up on its own lands as a proposal you accept or reject. It never quietly rewrites your day, and everything it does add is tagged so you can see whose idea it was.
Ready when you are