AIHOT
一个自己找热点、自己写日报的网站框架。把信源和精选标准换成你的,它就是你的行业热点站。
Runssource: GitHubhomepageTypeScriptMITcommit 589f79eff094
TypeScript, MIT licensed. The project labels itself: ai, chinese, content curation, daily digest, docker compose, llm, mcp and news aggregator.
AIHOT runs. An Argusic agent installed it in 17 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The API (port 3001) and web server (port 3000) start and serve pages; all 139 tests pass; the homepage, all/hot/daily pages, admin, RSS, sitemap, llms.txt, robots.txt, and OpenAPI spec all return 200.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- PostgreSQL not installed and no root to apt install5 minutes
- Node.js 18 installed but project requires >=24.112 minutes
- DATABASE_URL with ?host=/tmp caused PostgreSQL to reject 'host' config parameter1 minute
- Install time
- 17 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test exited 0 (128 passed); node --test apps/web/tests/*.test.ts exited 0 (11 passed); curl -s -o /dev/null -w %{http_code} localhost:3000 returned 200
- Model tokens used
- 69,160
- Exact commit tested
- 589f79eff094
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Tests**: - `npm test` — **128 tests passed**, 0 failed, 39193ms - Web tests — **11 tests passed**, 0 failed, 3109ms **Server startup**: API starts on port 3001, web on port 3000. **Endpoints verified**: - `http://localhost:3000/` — **200** (root page with full HTML) - `/all`, `/hot`, `/daily` — **200** - `/admin` — **302** (redirects to login) - `/agent`, `/llms.txt`, `/robots.txt` — **200** - `http://localhost:3001/openapi-v1.json` — **200** - `/api/mcp` — **405** (method not allowed on GET, expected) - `/api/site/timeline` — **200** with valid JSON response
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 17 minutes to install, slower than the median of the 234 comparable projects Argusic has measured.
Of the 235 ai projects Argusic has installed and timed, AIHOT was the 194th fastest to reach a running state, and 166 of 235 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
aichinesecontent-curationdaily-digestdocker-composellmmcpnews-aggregatorpostgresqlrssself-hostedtypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/aihot)Questions
- Does AIHOT run?
- Yes. AIHOT runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test AIHOT?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 589f79eff094. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test AIHOT?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does AIHOT take to install?
- 17 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does AIHOT need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing AIHOT?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does AIHOT compare with the alternatives?
- Of the 235 ai projects Argusic has installed and timed, AIHOT was the 194th fastest to reach a running state, and 166 of 235 reached one at all.
- Where is the evidence for AIHOT?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.