MeMex gives your Mac a private visual memory. It turns screen activity into an organized timeline of real work moments, then lets you ask plain-English questions and return to matching screen evidence. Daily and weekly reports summarize work you already did, while Pattern Insights spots repeated workflows worth automating. Recordings stay local in a location you control; AI analysis is optional and uses your own provider or compatible local endpoint.
No reviews yetBe the first to leave a review for MeMex
tried it for an afternoon and the timeline view feels genuinely useful, scrolling back to find that one design file i lost track of. like that the recordings stay on my machine by default.
Report
Maker
Thanks Sinem! That “one design file I lost track of” moment is exactly the kind of context gap MeMex is meant to close. I wanted the timeline to feel like continuity, not another folder full of screenshots. I’m glad the local recording model felt right too. When you found the file, did you get there by scrolling the timeline or by asking the Assistant? That distinction would help me decide which retrieval path to improve first.
Report
the local-only storage with optional AI processing is a really thoughtful split, it means you actually own your screen history without locking yourself out of useful analysis. nice to see a tool that respects privacy without gutting the feature set.
Report
Maker
Thanks Pınar! That balance is exactly the design principle: screen history should remain a user-owned local library, while analysis is an explicit layer you can add, change, or remove. Recording and timeline browsing still work without AI. A compatible local endpoint can keep the processing local; a hosted provider is optional and receives the disclosed analysis data only after consent. I’m glad that tradeoff came through. Would you personally lean toward a local model, or a hosted provider for better model quality?
Report
The timeline view is genuinely useful for finding that one thing I worked on last Tuesday without digging through screenshots. Local-only storage is a nice touch too, makes it feel less invasive than other activity trackers I have tried.
Report
Maker
@ensar90917 Thanks Ensar! That “I know I worked on it last Tuesday, but where was it?” moment is exactly why I built MeMex. I’m especially glad the local-first approach makes it feel less invasive.
Report
Tried it for a day and the natural language search worked way better than expected. I asked "show me when I was working on the pricing page" and it pulled up the right window. Local storage is a nice touch.
Report
Maker
Thanks Hediye! “Show me when I was working on the pricing page” is exactly the kind of ordinary, fuzzy memory query I wanted MeMex to handle. I’m glad it connected your wording to the right window after a full day of use. When it surfaced the result, was the timeline context enough to confirm it immediately, or did you still need to replay the clip? That would help me improve the result view.
Report
The "You did the work. But the details? Already gone." message really resonated with me.
I think forgetting context is a much bigger problem than people realize. Turning work history into something searchable feels like a very natural direction.
Congrats and good luck today! 👏
Report
Maker
@new_user___1802026258df93399c32311 Thank you, Lyra! That line came directly from my own frustration: I could remember completing the work, but not the path, sources, or decisions behind it.
MeMex is meant to make that context recoverable without requiring you to document everything manually. What kind of context do you find yourself losing most often: tabs and files, past decisions, or troubleshooting steps?
tried it for an afternoon and the timeline view feels genuinely useful, scrolling back to find that one design file i lost track of. like that the recordings stay on my machine by default.
Thanks Sinem! That “one design file I lost track of” moment is exactly the kind of context gap MeMex is meant to close. I wanted the timeline to feel like continuity, not another folder full of screenshots. I’m glad the local recording model felt right too. When you found the file, did you get there by scrolling the timeline or by asking the Assistant? That distinction would help me decide which retrieval path to improve first.
the local-only storage with optional AI processing is a really thoughtful split, it means you actually own your screen history without locking yourself out of useful analysis. nice to see a tool that respects privacy without gutting the feature set.
Thanks Pınar! That balance is exactly the design principle: screen history should remain a user-owned local library, while analysis is an explicit layer you can add, change, or remove. Recording and timeline browsing still work without AI. A compatible local endpoint can keep the processing local; a hosted provider is optional and receives the disclosed analysis data only after consent. I’m glad that tradeoff came through. Would you personally lean toward a local model, or a hosted provider for better model quality?
The timeline view is genuinely useful for finding that one thing I worked on last Tuesday without digging through screenshots. Local-only storage is a nice touch too, makes it feel less invasive than other activity trackers I have tried.
@ensar90917 Thanks Ensar! That “I know I worked on it last Tuesday, but where was it?” moment is exactly why I built MeMex. I’m especially glad the local-first approach makes it feel less invasive.
Tried it for a day and the natural language search worked way better than expected. I asked "show me when I was working on the pricing page" and it pulled up the right window. Local storage is a nice touch.
Thanks Hediye! “Show me when I was working on the pricing page” is exactly the kind of ordinary, fuzzy memory query I wanted MeMex to handle. I’m glad it connected your wording to the right window after a full day of use. When it surfaced the result, was the timeline context enough to confirm it immediately, or did you still need to replay the clip? That would help me improve the result view.
@new_user___1802026258df93399c32311 Thank you, Lyra! That line came directly from my own frustration: I could remember completing the work, but not the path, sources, or decisions behind it.
MeMex is meant to make that context recoverable without requiring you to document everything manually. What kind of context do you find yourself losing most often: tabs and files, past decisions, or troubleshooting steps?