Most of what people write in a journal is never read again, because reading a year of entries takes a weekend. An agent reads it in a second. Dayleaf 2.5.0 gives your assistant a search tool over your own words, so the journal stops being write-only.
💬 Questions that actually get answered
- "When did I first mention the knee pain, and how often since?"
- "What did I decide about the job offer, and what were my reasons at the time?"
- "Summarise my week in three lines and put it in my Reflections planner."
- "Which days this month did I write about feeling rested?"
Every answer comes with the dates, so you can open the page and read the original.
🔧 How the reading works
On the Mac, the MCP server exposes dayleaf_list_entries with a date range, a planner and a text query, plus dayleaf_get_day for a whole page. Any MCP client can call them. From Claude Desktop the config is six lines; from Claude Code it is one command. The same tools are available to hosted agents through the cloud door, which is how Muse answers from your phone.
dayleaf list --from -90 --q "knee" --jsonThat is the command behind the first question above, if you want to run it yourself.
📅 A weekly review that writes itself
Sunday evening, one prompt: "Read my entries from the last seven days. Write a short review: what went well, what I avoided, one thing to carry into next week. Save it to today's page in Reflections." You still do the thinking when you read it; the agent does the collecting. Dayleaf's own Year in Review does the numbers; this does the words.
🔒 Who can read what
Reading happens where the data is. On the Mac, the local API only answers on your machine. Through the cloud door, Dayleaf keeps a text-only copy of entries so an agent you authorised can search it with the key you created; photos, voice notes and videos are never part of it. Revoke the key and the reading stops; switch the door off and the copy is deleted.
