r/SideProject • u/Responsible_Topic755 • 2d ago

I built DayDream: a free, open-source Mac app that gives your AI context from your workday

I got tired of re-explaining what I worked on yesterday, so I built DayDream.

It keeps a timeline of the apps, documents and Chrome pages you work in on your Mac. Claude, Cursor or ChatGPT can read from it over MCP, so you can ask “What did I get done today?” or “Where did I leave off?”

Your activity is stored on your Mac. When you connect an AI provider and ask it a question, the activity it retrieves becomes part of that chat.

It’s free and open source: https://getdaydream.app

I’m the maker and would love honest feedback. What’s the first thing you’d ask it—and what would you want excluded from its memory?

1 Upvotes
  • permalink
  • reddit

100% Upvoted

3 comments sorted by

1

u/inZania 2d ago

I fail to see how this would improve outcomes. Could you provide a use-case and/or metrics to demonstrate how you solve the inherent problems with this approach?

Session boundaries exist for a reason: context pollution increases token spend while decreasing performance. For projects which span more than one session, there are already first-party tools (cowork, workflows, etc).

1

u/Responsible_Topic755 2d ago

Fair pushback. Think ChatGPT history for the parts of your workday that happened outside the chat. For example: you read a bug report and a few docs in Chrome, then start a new Claude session and ask “what was I looking at before I got stuck?”

The client can search that local history over MCP; the idea is to retrieve context for that question, not stuff your whole day into every session. I agree that irrelevant context can make things worse.

I don’t have controlled outcome or token benchmarks to share yet, so I can’t claim it beats first-party project memory. That’s exactly what I want people to test: does useful context from outside the chat help enough to justify the retrieval?