What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Can users adjust the context graph and approve background tasks themselves?From this comment
- How is this different from an existing fact-extraction knowledge graph tool?From this comment
- How do they limit context size and handle stale or conflicting information?From this comment
- How are entities clustered and deduplicated across sources?From this comment
- Does it work by simply pointing it at an existing notes vault?From this comment
What they doubted or pushed back on our summary
- A graph may add no real value over a plain database, so the term feels like marketing.From this comment
- Lack of sandboxing is worrying when it ingests text and runs code constantly.From this comment
- Using a big provider's mail and letting an agent have shell access seems unsafe and data-hungry.From this comment
- Relying on prompting is a barrier because average users don't know what to ask.From this comment
What the maker answered our summary
19 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Notes live as editable Markdown files on disk, and an assistant skill schedules background tasks.From this comment
- The graph updates continuously as work happens rather than being curated by hand first.From this comment
- Only relevant notes are retrieved through the graph, keeping context bounded instead of dumping history.From this comment
- Markdown was chosen so each node stays human-readable and manually editable.From this comment
What a builder can take from it: Builders should ship a clear landing page and editable plain-file storage, but must address sandboxing and explain why a graph beats simpler search. our reading
The title, taken apart our calculation
This post got 205 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
Tuesday at 16:00 UTC. Of 3,565 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 146 (4.1%) reached 50 points; on Tuesdays it was 2.8% of 8,995. 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