What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- How does this actually work when the model has so little context to begin with?From this comment
- What does this offer over summarizing or compacting previous sessions?From this comment
- What is the data retention and deletion policy, and will self-hosting be offered?From this comment
- How does this differ from an existing memory tool people already use?From this comment
- Have you looked at other similar projects out there?From this comment
What they doubted or pushed back on our summary
- Our team cannot send proprietary code to third-party servers, so this is ruled out.From this comment
- Many of these memory tools already exist, and a simple version-controlled file setup may suffice.From this comment
- Adding memory abstractions fights how models were trained, and built-in compaction is already improving.From this comment
- Quiet errors in a memory layer can quietly degrade downstream output over time.From this comment
What the maker answered our summary
21 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Memories live in a small embedded database, and each request triggers a semantic search weighted by time.From this comment
- Unlike summaries, which drop edge cases and drift, this lets you return days later and reorient.From this comment
- A self-hosted option has been requested by several people; the product is alpha and feedback shapes it.From this comment
- The amnesia problem applies across agents, and replies to concerns about trust and pricing.From this comment
What a builder can take from it: Builders should expect pointed questions about data handling, existing alternatives, and why a new memory layer beats simpler options. our reading
The title, taken apart our calculation
This post got 202 points; the median for all 1442 posts is 112. In AI and agents (352 posts) the median is 108 points and 49 comments.
When it was posted our calculation
Monday at 22:00 UTC. Of 1,600 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 46 (2.9%) reached 50 points; on Mondays it was 3.1% of 7,396. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More AI and agents teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with