What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether it tackles the hardest parts of git, namely submodules and large file storage.From this comment
- What concrete comparisons show this beating git, beyond a single claim about repo copies.From this comment
- Why a new system rather than building on git, and what the data model actually is.From this comment
- Why git performance would bottleneck agents, and what downloading everything or fighting worktrees means.From this comment
- What perks are agent-only, since performance gains would help any version control user.From this comment
What they doubted or pushed back on our summary
- No concrete comparison against git, just self-promotion and a gimmick reward for paying early.From this comment
- Performance is not an actual blocker in agent workflows.From this comment
- Replacing something this entrenched will be close to impossible.From this comment
- Nothing clearly explains why agents need a whole separate system rather than existing tools.From this comment
What the maker answered our summary
31 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Monorepo features are planned to address submodule pain, and no separate large-file system is needed.From this comment
- Points people to the site and offers to answer their questions directly.From this comment
- Agrees switching will be the hardest part and expects more competitors in this area.From this comment
- Says the bet is agents working faster and more parallel than people, so those speed numbers matter more.From this comment
What a builder can take from it: Lead with the core idea and a concrete comparison to the incumbent, since skepticism about differentiation and switching cost dominates. our reading
The title, taken apart our calculation
This post got 216 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 15:00 UTC. Of 4,000 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 133 (3.3%) 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