The owner sends anything useful from reels, threads and YouTube to a ‘message to myself’ chat. The trouble is that it ends there. Sent, then never found again.
What the owner said
I send things and can never find them. I want to press Share and have the rest read, sorted and brought back when I need it.
So here is what I did
- First checked whether the ‘message to myself’ chat could be read at all — it could not (the connected tool only sends). So the inbox moved to a Telegram bot
- Telegram keeps unfetched messages for only 24 hours → the mailbox lives online so nothing is lost when the PC is off
- At 11 pm Claude reads each pending link, checks whether the claim holds, and writes a card including where it could be used in our own work
- The page reads the store directly, so new cards need no site redeploy
- When a question shares words with a card’s tags, a ‘related material’ note is surfaced to the AI automatically
What the owner didPressing Share · deciding where and how it is shown
What turned out different when checked
| Assumed | Actual | So |
|---|---|---|
| Read the ‘message to myself’ chat | no way to read it | switched to a Telegram bot |
| Read Instagram and Threads content | without login only the caption text is readable | spoken content only for YouTube, via captions |
| The bot keeps what it receives | unfetched messages vanish after 24 hours | saved to the store on arrival |
Two things the review caught
- A route for private notes to leak. Cards made from posts sent without a link are now forced private on save. The owner’s own notes never enter the public table.
- Names ending up on cards. If a person’s name slips into the text it is replaced just before saving, and there is a test for it.
When building a public page, write down what could leak before deciding what to show — especially when a system writes text on its own.
What we learned
- Check that the thing is readable before designing around it. Finding out the chat was unreadable early let the design change.
- Don’t process everything at once. The 30-per-day cap is there so cost and errors can’t blow up together.
- Retrieval is half the job. An inbox that only collects is the same as the chat it replaced.