![\"My](\"docs/screens/icon.png\"){kind=icon}
\n\n# My Day\n\n**A private record of what you worked on, kept on your Mac.**\n\nIt writes a short note every ten minutes. Weeks later you can ask it what you were doing, and\nso can your AI assistant.\n\n\n\n# My Day\n\n**A private record of what you worked on, kept on your Mac.**\n\nIt writes a short note every ten minutes. Weeks later you can ask it what you were doing, and\nso can your AI assistant.\n\n![\"The](\"docs/screens/today.jpg\")
\n\n---\n\n## The problem\n\nYou finish a week and cannot account for it. Your manager asks what you shipped. You open a\nhalf-finished document and spend ten minutes reconstructing why you opened it. You read\nsomething useful in March and cannot find it in August.\n\nMeanwhile your AI assistant starts every conversation knowing nothing. You re-explain the\nproject, the file, the thing you already tried, every single time.\n\nYour computer knew all of it and wrote none of it down.\n\n## What it writes\n\nEvery ten minutes, one small Markdown file:\n\n```markdown\n---\nstart: 09:10\nend: 09:20\ntitle: Tracing the webhook retry loop\nsummary: You read Stripe idempotency docs, then edited retry.ts.\napps: Visual Studio Code, Google Chrome\nsites: stripe.com, github.com\nproject: payments-api\n---\n- Reading Stripe's idempotency-key docs on retried deliveries\n- Editing retry.ts, focused on the key-reuse path\n```\n\nThat is the whole storage format. About forty files a day. No database, no account, no\nupload. You can `grep` it, edit one, or delete a file you would rather not keep.\n\nThree sources feed it, each a separate switch: which app is in front, the pages your browser\nalready recorded, and your Claude Code sessions. Reading your browsing is a different\ndecision from reading your terminal work, so they are different switches.\n\n---\n\n## The timeline\n\n![\"The](\"docs/screens/timeline.jpg\")
\n\nYour day in order. Every note names the applications by their real icons and links the pages\nyou actually opened, so a morning you half-remember becomes a list you can click through.\n\nClaude Code sessions sit on the same rail as everything else, because a session and the\nbrowsing around it are usually the same piece of work. Each one carries a **resume** button\nthat copies the command to reopen that exact conversation.\n\nFilter the day by an app, a site, or a word, and the rail narrows to the slots that match.\n\n## Threads\n\n![\"Threads:](\"docs/screens/threads.jpg\")
\n\nTime-per-app is a fact about software: you spent 1h55m in Slack. A thread is a fact about\nwork: the checkout migration ran across six days and has been quiet for three.\n\nNothing is declared. There is no project field to fill in, no tags, no setup step, because\nthe people who would keep tags current do not need the tool.\n\nGetting there took two failed attempts, both instructive. Clustering on window titles looked\nrich and turned out to be the worst available signal: a terminal title reads the same for six\nhours, so its words bind every unrelated note in the day. Clustering on the summaries failed\nthe opposite way, paraphrasing the specific thing away until two notes about the same customer\nnever met.\n\nWhat works is identifiers. The file you edited, the repository you were in, the exact page,\nbyte-identical every time you touch the same thing and absent when you do not. Features that\nturn up nearly everywhere get dropped, and a note has to resemble a cluster's centre rather\nthan any single member, so one shared word cannot chain everything together.\n\nEach thread carries a state: today, yesterday, this week, quiet. The ones you picked up and\nput down surface first, because work you dropped is the reason to open the view.\n\n## People\n\n![\"People:](\"docs/screens/people.jpg\")
\n\nA personal CRM you never fill in. Dex and Clay and Monica all make you log each interaction\nby hand; this reads the names off your meeting, chat and mail window titles, and counts.\n\nFor each person you get how often you were in contact, when you last were, a rising, fading\nor cold trend, and the documents you had open together. The list leads with who is going\ncold: someone you were in regular contact with, then a week of nothing. Nothing else here\nsurfaces that, and it is the thing a manager actually misses.\n\nThe names are filtered so the list is people, not products. A stop list removes feature and\ndocument vocabulary, and your own name, detected from the account it appears under.\n\n## What you read\n\n![\"Content:](\"docs/screens/content.jpg\")
\n\nEverything you read, across every app rather than only the browser. A Word document, a Notion\npage, a PDF in Preview, a ticket in your tracker all land in one list, ranked by the time and\nthe days they drew, each linking back to the page.\n\nThe bar is deliberately low, so a spec you opened for two minutes still shows. What gets\nstripped is news fronts, entertainment, social feeds, search-result pages and sign-in\nplumbing, because those are glances rather than reading. When it is unsure, it keeps.\n\nReading the body of a page, not just its title, is an optional source: it uses the same\nAccessibility grant window titles need, takes no screenshot, and stores no image. With it on,\na note can say what a page said rather than only that you had it open. It is the most\nsensitive thing here, so it is off until you turn it on.\n\n## Friction\n\nRecurring costs, counted rather than asserted: signing in to the same host 29 times a week,\nthe same search typed on 13 separate days, a page you open daily and never bookmarked. Each\nfinding shows how many times and across how many days. Available from `myday friction`.\n\n---\n\n## Your AI assistant can read it\n\nMy Day ships an MCP server, so any assistant that speaks MCP can look up what you did instead\nof asking you.\n\n**Claude Code**, in `~/.claude.json`:\n\n```jsonc\n{ \"mcpServers\": { \"myday\": { \"command\": \"myday-mcp\" } } }\n```\n\n**Cursor**, in `.cursor/mcp.json`. **Windsurf, Zed, Continue** and anything else with MCP\nsupport take the same two lines.\n\nThen, mid-task:\n\n> **You:** pick up where I left off\n>\n> **Claude:** You were tracing a double-fire in the webhook retry loop. You'd read Stripe's\n> idempotency docs and edited `retry.ts`, and `retry.test.ts` was still failing on the\n> duplicate-delivery case (2026-08-14 15:30).\n\nFour tools: `history_search`, `history_window`, `history_resume`, `history_time_by`.\n\nNotes are built from web page titles, which are text other people control. A page titled\n*\"ignore previous instructions\"* would otherwise reach an assistant that can run commands.\nEvery response comes back inside a fenced envelope with the brackets escaped, so the payload\ncannot close it, and the rule is restated on every single response.\n\n---\n\n## Install\n\n**[Download My Day.dmg](https://github.com/abhitsian/myday/releases/latest)** → drag into\nApplications → **right-click and choose Open** the first time. Nothing else to install; a\nNode runtime ships inside the app. Five screens explain what it reads before it reads\nanything, and it lives in the menu bar from then on.\n\nRemoving it takes everything with it: **Delete Everything and Quit** in the menu bar, or\n`myday uninstall`.\n\n| ask \"\"\nmyday sources | permissions | clear | backfill\nmyday build-content # optional: read on-screen text, off by default\nmyday view # the app, in a browser\n```\n\n## What it does not do yet\n\n- **Window titles need Accessibility**, so without it a note names the app and not the document.\n- **macOS only.** The sampler and the helper are both AppKit.\n- **Git and calendar are planned**, not built. The source registry already lists them.\n- **No sync.** One machine, one history, by design.\n\n## License\n\nMIT\n","readmeFilename":"README.md"}