Finish time
Add up what's left, drop it into the hours you actually work, and you get the time today runs out. When the work outgrows the day the readout turns red at 9am, not at 6pm, and the list is still yours to cut.
A text file is the whole database
The day planner that wires itself into your agents.
todos.md and memory.md are the whole
database. Daymetric tells you what fits today and when you're
done. Claude, Cursor and Codex read and write the same files, and
anything they think of on their own arrives as a proposal you
approve. Your folder stays yours.
Today
one windowOne window, and it already knows when you're done.
Every reading on the board comes from two markdown files. Keep scrolling and the board says what each one is.
- 01 · Done by When today's remaining work runs out, not a guess. It moves as you clear things.
- 02 · The day note One sentence a day, derived from the files and nothing else.
- 03 · From Claude A proposal waits for your ACCEPT. Nothing reaches the day unseen.
- 04 · Effort on every line Thirty minutes here, an hour there. It is what makes a finish time possible.
Your agents
21 toolsIt finds your agents and wires itself in, so you don't have to.
Daymetric ships its own MCP server, native Swift, no Node, nothing to paste into a config file. Say yes once and every agent it finds on your Mac gets the same 21 tools, plus a page of instructions on how to behave inside somebody's day.
Registered at first launch in each agent's own config, removed the same way from Settings. Move the app and the next launch repoints them.
Claude Code
wired
Claude Desktop
wired
~/scheduler/todos.md
Cursor
wired
Codex
wired
- you what's on my list in daymetric?
-
claude
list_tasks - Five today, three tomorrow, three in the backlog. You're done by 17:32.
- you the board call moved to three. propose what has to give
-
claude
add_taskproposed - Proposed “Review Q3 pricing before the board call”, 30m under Northwind. It's waiting in the app.
-
claude
start_task -
claude
complete_task - Done and logged at 14:52. Finish time moved to 17:02.
- [ ] Rewrite the pricing page | project: Atlas | effort: 1h | block: deep
- [ ] Draft the metrics section | project: Northwind | effort: 45m | deadline: 2026-09-25 | priority: 1
- [ ] Ship the onboarding copy | project: Northwind | effort: 30m
- [?] Review Q3 pricing before the board call | project: Northwind | effort: 30m | by: claude | started: 2026-09-22
proposed · from claude
Accept
Reject
- [x] Review Q3 pricing before the board call | at: 14:52-
01
It reads
todos.mdandmemory.md, the same files you edit, through the same parsers the app uses. -
02
Anything it thinks of on its own lands as
- [?], taggedby: claude, with its reasoning in the notes. Only a task you asked for by name goes in as- [ ]. -
03
You accept or reject it in the app. Nothing reaches your day unseen.
-
04
It arrives already knowing the house rules: proposals, not surprises; always set an effort; defer, don't delete. Six thousand characters of instructions ship inside the app and are re-read every time an agent connects.
list_tasksget_taskadd_taskupdate_task_notescomplete_taskuncomplete_taskremove_taskstart_taskunstart_taskset_blockset_projectset_capacityread_memoryupdate_memoryread_done_logwrite_briefingadd_ideaadd_learningread_learnedlist_peersassign_task
The loop
done.md → memory.mdEvery task you close teaches the next estimate.
The log keeps the time you finished. When a project keeps running
long, memory.md gets a multiplier, and the finish time
uses it before you would have. Your agent reads the same
calibration and the same learned.md before it
proposes anything, so the scheduler gets better and the agent gets
better from one set of files.
Today
done by 17:32
done.md
at: 14:52 on every closed task
Your agent
reads learned.md before it proposes
memory.md
## Calibration · Atlas: 1.4
Calibration
Guess 30m on a project you reliably spend an hour on and the estimate is multiplied before it reaches the clock. The briefing can say so out loud: “Atlas has run 1.4x your estimates for six weeks.”
The day note
One plain sentence a day, derived from the files and nothing else: “You've moved ‘Call the accountant back’ 6 times.” Four is usually the app telling you something.
Your day
05:00 → 22:00The lamp beside the date knows what time it is.
Coffee at seven, noodles at noon, a moon after dinner. Sixteen pixels a side, drawn with code and baked into the app, and the one place the panel is allowed a colour that isn't the burn. Each one plays its entrance once and then holds still. A lamp, not a screensaver.
The menubar carries the same finish time all day, so the window can stay closed. On the phone the same files are the deck you carry: swipe right to clear, swipe left to defer.
Your tasks
todos.mdA task is one line of text. That's the whole format.
No database, no export button, no proprietary format. 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-25 | priority: 1- project
- Carries the weight you set once in
memory.md. - 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.
A few more tokens do the unglamorous work. defer: 2026-10-01
pushes a task out of today without deleting it. repeat: weekdays
re-arms it after every completion, one live line forever.
block: deep pins it to your deep-work hours, and
carried: 4 counts how many times you've hauled it
forward.
Your files
no lock-inNobody can revoke a text file.
Everything Daymetric reads and writes is plain markdown in a folder you already control.
Durable
Opens in TextEdit today. Opens in TextEdit in ten years.
Private
No analytics, no tracker, no crash SDK. The scheduler never asks the network to plan your day.
Independent
If Daymetric disappeared tomorrow, your day wouldn't.
Your account carries the same files to your phone. Nothing about the format changes on the way, and the folder auto-commits to a local git repo, so last week is one command away.
Your plan
one priceFourteen days, everything on. Then £6 a month.
No free tier and nothing held back during the trial. A crippled trial tells you nothing about the app. When the fourteen days end, Daymetric becomes a reader: it still opens, still shows your day and your log, and still exports everything. It just stops writing until you subscribe.
Daymetric
£6a month
£49a year
- Mac and iPhone apps
- The vault, the scheduler, the log
- Claude, Cursor and Codex, through the built-in connection
- Sync between your devices
- Coworkers and handoffs
- Recurring tasks
Pay once
£89once
- The same app, paid once, never renews
- Buy now, sign in later: it attaches to the email you pay with
Your files are yours whether you pay or not: reading and export never stop, and the folder opens in TextEdit with every server we run gone. Cancel any time. The refund policy is one paragraph.