DailyBrief

AI 每日新闻简报 · GitHub 热门 + X 热门文章 + 行情技术分析 · 23 个数据源聚合 + LLM 中文摘要 · 本地或 GitHub Actions 部署

Runs with mockssource: GitHubhomepageTypeScriptMITcommit 75e24a62e11c

TypeScript, MIT licensed. The project labels itself: ai, claude code, claude skills, daily digest, llm, news aggregator, rss aggregator and self hosted.

DailyBrief runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2.1 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Full pipeline runs end-to-end: 549 articles fetched from 23 sources, LLM enrichment mocked with deterministic JSON for all 5 enrichment categories + trading commentary + daily digest, report written to daily_reports/2026-10-23 as JSON+HTML+articles cache.

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.47 (measured)
recorded runs
1
last tested
stars
393
forks
224
open issues
2
watchers
0
size
19 MB
created
last push

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.

Time lost to each failure while testing DailyBrief, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • No LLM credentials available — all 6 backends need an API key2.8 minutes
  • Node.js 18 too old — cheerio + undici require >=20.18.11.2 minutes
  • Mock response selector matched GH enrichment before digest because digest systemPrompt mentions 'GitHub Trending' in rules0.5 minutes
Install time
2 minutes
Cold machine to finish
34 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
npm run daily exited 0 producing valid JSON with hero_headline=Global Markets Steady as Tech Sector Sees AI Advances, 4 tech briefs, 3 finance briefs, 2 politics briefs, 21 tickers, 4 trading watchlist picks, 841-char market overview, 127KB valid HTML output
Model tokens used
203,773
Exact commit tested
75e24a62e11c
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

| Component | Result |
|---|---|
| Source fetching | 549 articles from 23 sources |
| GH Trending enrichment | 9/9 matched |
| Trending papers enrichment | 20/20 matched |
| X viral posts enrichment | 5/5 matched |
| Trading analysis | 21 tickers, F&G index, BTC dominance |
| Trading commentary | 4 watchlist picks with market overview |
| Daily digest | 4 tech briefs, 3 finance, 2 politics, 7 keywords |
| Output files | `2026-10-23.json` (valid JSON), `2026-10-23.html` (127KB, valid HTML), `2026-10-23…
**All npm scripts verified working**: `dry-run`, `daily`, `render`, `regen-trading`, `sources`, `so…
**Remaining issue**: The `Exclude<LlmBackendId, "claude-cli">` type in `validateBackendCredentials`…

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

  • Installed in 2.1 minutes, faster than the median of the 236 comparable projects Argusic has measured.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 237 ai projects Argusic has installed and timed, DailyBrief was the 79th fastest to reach a running state, and 168 of 237 reached one at all.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.47

Topics (from GitHub)

aiclaude-codeclaude-skillsdaily-digestllmnews-aggregatorrss-aggregatorself-hosted

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/DailyBrief.svg)](https://argusic.com/subject/dailybrief)

Questions

Does DailyBrief run?
DailyBrief runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test DailyBrief?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 75e24a62e11c. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test DailyBrief?
The run that produced this verdict cost $0.47: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does DailyBrief take to install?
2.1 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 DailyBrief need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing DailyBrief?
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 DailyBrief compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, DailyBrief was the 79th fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for DailyBrief?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion