What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the benchmark tests single retrieval accuracy or how well a coding agent responds overall.From this comment
- How the tool performs on non-coding material like API documentation or agent memory files.From this comment
- Whether real agent benchmarks exist, since models trained on grep may distrust other tools and retry, losing savings.From this comment
- Why the command-line tool was written in Python instead of a faster, more portable language like Go or Rust.From this comment
- How it compares with other established tools such as context-mode, serina, colgrep, or LSP-based approaches.From this comment
What they doubted or pushed back on our summary
- Grep uses no tokens, so claiming a large percentage fewer than it makes little sense.From this comment
- Models heavily trained on grep may distrust other tools and retry, wiping out any token savings.From this comment
- Unlike grep it searches probabilistically, so it may fail to surface something important.From this comment
- On small codebases, dumping the whole directory into context may be cheaper than searching.From this comment
What the maker answered our summary
22 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Proper agent benchmarks are being worked on but are hard and costly across harnesses and models.From this comment
- Many harnesses default to grep plus reading files, a gap they expect providers to address eventually.From this comment
- Getting the agent to prefer the tool is mostly handled through the prompt, though still being evaluated.From this comment
- Another tool caused an agent loop it could not escape, so the maker uninstalled it.From this comment
What a builder can take from it: Builders should expect trained habits and harness defaults to decide whether a new tool is adopted, so measuring real agent outcomes matters more than retrieval savings alone. our reading
The title, taken apart our calculation
This post got 445 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 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 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