DaymetricDaymetric
£6a month
£49a year
- Mac and iPhone apps
- The files, the scheduler, the log
- Claude, Codex and Cursor, wired in
- Sync between your devices
- Coworkers and handoffs
- Recurring tasks
A task manager you share with Claude or Codex.
Your day lives in two markdown files. Daymetric packs it into the hours you have and tells you when you'll be done. Claude, Codex and Cursor read and write the same files, and anything they come up with on their own waits for your yes.
Fourteen days free, everything onVersion 1.45.2 for macOS 14 or laterApple Silicon and InteliPhone on TestFlight
Done by
You've moved “Call the accountant back” 6 times.
Proposed while you slept
Fix the flaky checkout test
Reply to Ledger about the renewal date
Today
3h 30mRewrite the pricing page
Draft the metrics section
Prep the board update
Ship the onboarding copy
Call the accountant back
Tomorrow
2h 15mAnswer the design review
Review the Q3 forecast
Write the changelog
Backlog
2h 50mMove the docs off Notion
Chase the Ledger renewal
Plan the offsite
A demo board. Tick a task, or accept what came in overnight, and watch the finish time move.
It already knows when you'll be done.
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 you find out at nine, not at six, while the list is still yours to cut. The menubar carries the same time all day, so the window can stay closed.
It finds your agents and wires itself in.
Daymetric ships its own MCP server. 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. One switch in Settings takes it out again.
Claude Code
Claude Desktop
Daymetric
Cursor
Codex
- 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 | 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-23
Proposed by Claude
Accept
Reject
- [x] Review Q3 pricing before the board call | at: 14:52
Anything an agent thinks of on its own lands as
- [?], tagged by: claude, with its
reasons in the notes. Only a task you asked for by name goes
in as - [ ].
It arrives knowing the house rules: proposals, not surprises; always set an effort; defer, don't delete. Nearly six thousand characters of instructions ship inside the app.
The 21 tools
list_tasksget_taskadd_taskupdate_task_notescomplete_taskuncomplete_taskremove_taskstart_taskunstart_taskset_blockset_projectset_capacityread_memoryupdate_memoryread_done_logwrite_briefingadd_ideaadd_learningread_learnedlist_peersassign_task
A task is one line of text.
No database to export from and no format to learn. Open
todos.md 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. It 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 do the unglamorous work. defer: 2026-10-01
keeps 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.
Time a task, and the next estimate learns from it.
Press start on a task and the log keeps what it took. After five timed tasks Daymetric knows your pace, and the finish time uses it before you would have. A project with five of its own gets its own number. Nothing is guessed: it learns only from what you time.
- [x] Tighten the Atlas signup flow | project: Atlas | effort: 30m | spent: 42m | at: 14:52Your agent reads the same number before it proposes: “Atlas runs 1.4×, so that 30m lands near 42m.” It still writes 30m, so the scheduler multiplies once. Agents are timed on a clock of their own, shown beside yours and never mixed in.
It tells you when the day ends. Then it does.
The finish time moved all day: later when you accepted what came in overnight, earlier each time you ticked something off, around the meetings on your calendar. Now it's 17:32 and the list is empty. Tomorrow is already packed.
And one plain sentence a day, worked out from the files and nothing else: “You've moved ‘Call the accountant back’ 6 times.” By the fourth time, it's the app telling you something.
Close the day.
Fourteen days with everything on, then £6 a month. There's no free tier and nothing held back in the trial. When the fourteen days end Daymetric becomes a reader: it still opens, still shows your day and your log, and still exports everything. It stops writing until you subscribe.
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. Everything Daymetric reads and writes is plain markdown in a folder you control. It opens in TextEdit today and in ten years, it opens with every server we run gone, and the folder commits itself to a local git repo, so last week is one command away.
No analytics, no tracker, no crash SDK. The scheduler never asks the network to plan your day. Cancel any time; the refund policy is one paragraph.