What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the project is a harness, a tuned model, or both, and if other models can be used.From this comment
- Whether an existing editor could add anchored edits as a feature instead of a new tool.From this comment
- How it compares to another agent and how it does on everyday coding beyond benchmarks.From this comment
- Whether plan and act mode from the original fork are still present.From this comment
- Which benchmark numbers came from which model, and whether results generalize to other model families.From this comment
What they doubted or pushed back on our summary
- Earlier static analysis assistants felt underwhelming, with complaints firing mid-edit and cached results getting stuck.From this comment
- The tool fails with an API error when used with one particular model provider.From this comment
- Why build a separate harness when an existing one already supports such extensions.From this comment
- Performance shown on one model may be overfit rather than general, so another family should be tested.From this comment
What the maker answered our summary
29 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- The default model was one specific Gemini version, and the fork supports many models including open ones.From this comment
- Language parsing uses bundled parsers with a symbols database stored in the workspace to keep things fast.From this comment
- An eval of eight tasks across seven agents is published, and the fork began as frustration with a slow tool.From this comment
- Attempts to benchmark open models keep hitting strict task timeouts, and the readme was updated to name the model.From this comment
What a builder can take from it: A builder can learn that the surrounding harness, not just the model, drives benchmark gains, and that claims should name the model and be tested across several. our reading
The title, taken apart our calculation
This post got 393 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 12:00 UTC. Of 3,017 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 80 (2.7%) 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