What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether routing loses prompt caching and how it affects money while developing.From this comment
- Whether switching between different models actually saves money or burns more overall.From this comment
- How this differs from another editor's automatic model selection mode.From this comment
- Whether routing across models costs more than sticking with one cached model.From this comment
- Whether it uses a subscription plan or always charges per-token API billing.From this comment
What they doubted or pushed back on our summary
- Prompts are already tailored to a specific model, so routing on style may pick wrong.From this comment
- Many doubt it helps, since working through a subscription CLI directly may be cheaper.From this comment
- The claim about rewarding the router on task success sounds far too simplified.From this comment
- Privacy worries arise because prompts and code pass through a third-party proxy.From this comment
What the maker answered our summary
41 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Router is cache aware and raises the bar for switching once a model is in use.From this comment
- Small models can handle whole sessions, and subagents with fresh context can go cheap.From this comment
- Stateless per-request routing would cost more, so switching needs a high threshold.From this comment
- It uses existing subscriptions first and falls back to API billing only when needed.From this comment
What a builder can take from it: Cache awareness and subscription handling decide whether a multi-model router saves money, so builders should test switching costs against real sessions. 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
Friday 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 Fridays it was 2.7% of 6,422. 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