It's inspired by a moment a few years ago when I realized I had no history of what I had worked on in the past.

It let's you quickly get answers to questions like:

- What did I work on last week? - What was that one hacker new post about compiler optimization that I forgot to bookmark last week?

And it has MCP support so it plays well with Claude.

I've used it recently to target specific job applications by adjusting my resume based on what the job application is looking for and what I've worked on in the past... Claude one shots this (because it has context from Memex). And it feels amazing!

Also, the name Memex comes from Vannevar Bush's 1945 article "As We May Think". He originally thought of as a device in which individuals would compress and store all of their books, records, and communications, "mechanized so that it may be consulted with exceeding speed and flexibility". The individual was supposed to use the memex as an automatic personal filing system, making the memex "an enlarged intimate supplement to his memory".

And he created a word - memex - which is a portmanteau of "memory" and "index".

The wikipeida entry here has more information: https://en.wikipedia.org/wiki/Memex

It's been a slow start for me. But now, between the cli interface and the MCP connection with Claude I find that I'm starting to use it instead of:

- Bookmarks - Lists / Bug Tracking

And even more exciting it's unlocking capabilities that I didn't have before:

- Can ask Claude to review the last week of work and remind me of things that I might still need to do - Can prevent randomization when someone asks me how to configure a server that I set up a month ago. Now I just ask claude and it checks in Memex. And I can send over a nice .md file

Comments URL: https://news.ycombinator.com/item?id=45588291

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=45236104

Points: 3

# Comments: 0

Is anyone using LLMs to enforce coding best practices?

Ex: A preference for named enums rather than Integers.

Imagined workflow is commenting on a github PR to add another rul or re-run existing rules on the patch.

Comments URL: https://news.ycombinator.com/item?id=41102792

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=40469540

Points: 2

# Comments: 0

I’ve built a lot of software in the past the no one has used. Trying to get feedback before writing a line of code.

Does a status update tool sound useful?

It’d capture a screenshot each hour on the hour while you work. Use OCR to convert the screenshot to text. And then use an LLM to convert the text into a daily summary

You could share it on slack, etc. and later on I’d build a slack intervention

Open to any and all feedback

Comments URL: https://news.ycombinator.com/item?id=40097086

Points: 1

# Comments: 0

1. Screenshot captured each minute 2. OCR extracts text 3. LLM converts text to a summary of what you were working on at that exact moment 4. LLM Summarizes the summation of the summaries into a daily update 5. Slack integration so you can decide to share the update or not on Slack

Tech stack: MacOS & Apple Silicon Privacy: Screenshots stay on device, OCR text is sent to OpenAI model for summarization Workflow: Install the app, approve Slack integration, set time for daily update, and wait to get your daily summary (as a DM in Slack), you can edit / approve the message

Open to any / all feedback. Thanks! :)

Comments URL: https://news.ycombinator.com/item?id=40082419

Points: 1

# Comments: 1

-- For now, you can 'Cmd' + Drag the item out of the toolbar to remove it.

I'm also taking a look at the state change bug.

Taking a look at using a dmg for download + notarizing the DMG so that there isn't a warning.

And then will look at fixing the bug you mentioned RE clicking on the icon and not seeing any changes.

Lastly, planning on adding in Sparkle so that updates can be sent out automatically.

Comments URL: https://news.ycombinator.com/item?id=40068580

Points: 1

# Comments: 5

Comments URL: https://news.ycombinator.com/item?id=37838402

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=37268506

Points: 1

# Comments: 0

I've built an early version of a searchable screen history tool. Please watch the loom and if you're interested in trying the product let me know.

Requirement: Availability on Monday 8/30 for a video onboarding between noon and 5pm EST.

Loom: https://www.loom.com/share/2b757626d6d6424192039e0df7daf718

Comments URL: https://news.ycombinator.com/item?id=37268447

Points: 1

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=37249910

Points: 2

# Comments: 0

Would love to chat more about this. Feel free to send me an email at: joenewbry@gmail.com

New(ish) poster here. Wondering what tools you recommend for a searchable + sharable history of my computer screen.

I'd like something that takes a screenshot every second and then allows me to semantically search to find things.

Use Case:

1. Bug fix - I'd like to be able to describe a bug and then see any screenshots related to similar issues I've run into the past. [Easy] 2. Post hoc workflow sharing - Someone ask my workflow a week after I've done something. [Hard] 3. Daily updates - a summary of work done each day. [Hardest]

Thanks for the suggestions!

Comments URL: https://news.ycombinator.com/item?id=36463407

Points: 2

# Comments: 4