Developers are terrible at keeping work journals, and great at leaving a trail in git. Headless Dayleaf lets the trail become the journal. Every evening Claude Code reads what you committed, writes two honest lines about it, and files them on today's page in a Work planner. Six months later, "what was I doing in March" has an answer.
⌨️ Setup, once
On the Mac, switch on Headless Dayleaf in Settings and attach the MCP server to Claude Code:
claude mcp add dayleaf -- npx -y dayleaf-mcpClaude now has tools like dayleaf_add_entry and dayleaf_list_entries. Entries it writes carry a via claude chip.
🌙 The evening prompt
From the repo you worked in, at the end of the day:
"Read today's git log across this repo. Write a two-sentence plain-English summary of what shipped and what is still open into my Dayleaf Work planner for today. No file names, no jargon."
A typical result: "Onboarding fix shipped · 3 PRs merged. Leaderboard API is up; the Android build is waiting on Play." Add it as a saved prompt, or put it on a schedule with a one-line script around claude -p.
🧠 Why this beats a notes file
- It lives on a calendar. The month view shows which days had shipping and which were quiet, without reading a word.
- It sits next to your life. Your own entry about a hard day is on the same page as what you shipped that day. That juxtaposition is the point of a journal.
- It is searchable by an agent.
dayleaf list --q "leaderboard" --jsonor a question to Claude pulls the history of any thread of work, across months.
Goals too
The local API also exposes daily goals. Ask Claude to tick "Ship the fix" when it sees the matching commit, and the goal checks itself off in the Day view. Small, but it is the feeling of a planner that keeps up with you.
