What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- How does this improve on keeping a session-specific README file?From this comment
- Is this better than just asking the assistant to do the same work?From this comment
- Are there benchmarks or evaluations proving it reduces waste?From this comment
- How is this different from simply using a resume?From this comment
- How does this differ from another similar memory project?From this comment
What they doubted or pushed back on our summary
- An existing project instructions file plus a ticketing system already covers this need.From this comment
- They never had to explain their project, so this optimizes a problem they don't have.From this comment
- Keeping a local copy of past context is problematic; versioned instruction files work better.From this comment
- The repository looks like it was generated by an AI rather than written by a person.From this comment
What the maker answered our summary
2 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- There is currently no way to handle stale memory, and the teammates angle was not considered.From this comment
- The plugin was submitted to the official directory and published, with easier install docs coming.From this comment
What a builder can take from it: Builders should check whether existing instruction files and workflows already solve the problem before shipping another memory tool. our reading
The title, taken apart our calculation
This post got 138 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
Sunday at 21:00 UTC. Of 1,956 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 55 (2.8%) reached 50 points; on Sundays it was 3.4% of 5,343. 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