Meridian finished as the #1 Product of the Day on Product Hunt. 🎉

by•

We spent three months building an open-source, local-first AI work journal that captures daily activity and turns it into clear timelines, worklogs, and updates. Yesterday, the Product Hunt community helped it reach the top position.

Thank you to everyone who supported the launch, shared their experience, left a comment, or recommended Meridian to someone else. The launch is over, but the work continues. We are reviewing what people shared and improving the onboarding, activity timeline, and drafted updates.

If you have tried Meridian, we would value hearing honestly what worked well and what still feels unclear.
GitHub:

Product Hunt:

75 views

Add a comment

Replies

Best

Local-first is interesting. I’m curious how Meridian handles days when some activity isn’t captured.

 Meridian shows gaps in the timeline when activity is not captured, so users can review the day and manually add any missing context. We are also improving the timeline to make incomplete periods easier to identify and correct.

 Yeah, that makes sense. Being able to see the gaps and add the missing context manually sounds pretty useful.

   the part I'd watch for is people backfilling a cleaner version of the day than what actually happened once they're typing it in manually, not just filling gaps but editing the story

   That is a valid concern. Manual additions should preserve the distinction between captured activity and user-provided context, rather than rewriting the original timeline. Clear labels and an edit history would help keep the record transparent.

I’d probably test it through a normal workday first, then compare the captured timeline with what I actually remember doing.

 That is a useful way to evaluate it. Comparing Meridian’s timeline with your own recollection should quickly reveal what it captured accurately and where context is missing. If you try it, I’d value hearing about the gaps you notice.

 Yeah, that’s what I was thinking too. I’d be more interested in seeing where it misses things during a normal workday than just how much it captures.

 That would be the most useful test. If you notice any missing context during a normal workday, please share the specific gaps so we can improve the capture and timeline.