ai-trend-studio
Local-first AI trend radar and live-session distillation
Runssource: GitHubPythonMITcommit a0600e01e766
Python, MIT licensed. The project labels itself: ai, bilibili, douyin, knowledge management, local first, summarization and trends.
ai-trend-studio runs. An Argusic agent installed it in 0.5 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 app installs in a venv, the server answers 200 on /api/health, / and /api/export, refresh collects real AI-relevant trends from all four public sources, and the live-session create/event/finish flow completes with a local summary, with tests 8/8 passing.
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 60 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.
- System pip rejects editable install on this Debian container (PEP 668 externally-managed-environment)0.5 minutes
- run.sh and the project quick-start invoke ./run.sh but the file has no executable bit, so a fresh checkout gives Permission denied0.1 minutes
- POST /api/imports runs compact_space before the SRT/VTT timestamp check, so a real SRT payload is stored with timestamps and content_source=manual instead of cleaned subtitle content0.1 minutes
- Install time
- under a minute
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- curl 127.0.0.1:8765/api/health returned 200; curl POST /api/refresh returned 200 with all four sources ok; curl POST /api/live/sessions + /events + /finish returned 201/201/200 with status finished and local summary; curl GET /api/export returned 200; curl POST /api/settings returned 200 and masked api_key as ********; python3 -m unittest discover -s tests ran 8 tests, OK
- Model tokens used
- 316,137
- Exact commit tested
- a0600e01e766
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- App: `./run.sh` → `Permission denied` (`run.sh` committed without executable bit); `sh run.sh` → … - Live (real network, no mock): `/api/refresh` → 200, sources all `ok` (bilibili 50, zhihu 30, weib… - Repo hygiene: `data/db.json` runtime artifact cleaned, no diff left in the repo. **One product bug to be aware of** (I did not alter the code): the SRT/VTT import doesn't strip tim… No third-party keys are required — everything verified against the app's own behavior and real publ… exec /bin/sh -lc 'date -u +%FT%TZ; git -C /work/repo status --porcelain; echo "final-clean"' in /work/re… succeeded in 0ms: 2026-10-28T13:29:30Z final-clean tokens used 316,137
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.
- Installed in 0.5 minutes, faster than the median of the 217 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.
- 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.
Of the 218 ai projects Argusic has installed and timed, ai-trend-studio was the 14th fastest to reach a running state, and 142 of 218 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.
- A quick evaluation: it was running 0.5 minutes after the clone.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.06 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.03 |
Topics (from GitHub)
aibilibilidouyinknowledge-managementlocal-firstsummarizationtrends
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ai-trend-studio)Questions
- Does ai-trend-studio run?
- Yes. ai-trend-studio runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test ai-trend-studio?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a0600e01e766. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ai-trend-studio?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ai-trend-studio take to install?
- 0.5 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 ai-trend-studio need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ai-trend-studio?
- 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 ai-trend-studio compare with the alternatives?
- Of the 218 ai projects Argusic has installed and timed, ai-trend-studio was the 14th fastest to reach a running state, and 142 of 218 reached one at all.
- Where is the evidence for ai-trend-studio?
- 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.