What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the tool also handles desktop applications or only web development work.From this comment
- How the tool would work with mobile apps on iOS simulators or Android emulators.From this comment
- What this offers that an existing browser automation command line tool does not.From this comment
- Whether screen access could use accessibility APIs instead of screenshots, and scale to other systems.From this comment
- Whether a local option could replace the dependency on a third-party hosted service.From this comment
What they doubted or pushed back on our summary
- Capturing screenshots and video is not the same as actually seeing or judging a screen.From this comment
- Coding agents are poor at spotting user experience problems, and the person still has to judge taste.From this comment
- Similar functionality already ships natively in other agent tools and editors.From this comment
What the maker answered our summary
21 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- It is web only for now, running headless Chromium, with desktop and mobile the top requested additions.From this comment
- The tool targets agents needing only shell commands, bundling video, screenshots, console errors and logs.From this comment
- It runs locally as a command line tool and local daemon, so there is no cloud hosting dependency.From this comment
- A before-and-after pull request comparison is exactly what one of its commands was built for.From this comment
What a builder can take from it: Giving agents a way to verify what they built and bundle the evidence answers a real review pain, but expect questions about scope, existing alternatives and true visual judgment. our reading
The title, taken apart our calculation
This post got 161 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 07:00 UTC. Of 1,349 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 18 (1.3%) 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