LiveStream-Agent-Studio

面向抖音直播电商的 Windows 本地 AI Agent Studio,贯通主播发现、直播洞察、直播复盘与短视频内容编导的统一智能工作流。

Runssource: GitHubPythonMITcommit 1614dfa166f7

Python, MIT licensed. The project labels itself: ai agent, douyin, livestream and speech to text.

LiveStream-Agent-Studio runs. An Argusic agent installed it in 12 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Frontend builds and serves HTTP 200 on port 4173, all 61 tests pass across the frontend and 3 Python agent packages, and the local gateway starts successfully.

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

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
2,053
forks
270
open issues
12
watchers
208
size
1 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 LiveStream-Agent-Studio, 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.

  • Node.js v18.19.1 below project minimum v22.13.05 minutes
  • pip install blocked by PEP 668 externally-managed-environment1 minute
  • pytest not installed in venv0.5 minutes
Install time
12 minutes
Cold machine to finish
3 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
npm test passed (2/2), vinext build succeeded, vinext start returned HTTP 200 serving the full LiveAgent Studio page, all 4 Python agent suites passed (59/59 pytest tests), local_gateway.py started successfully on port 8785
Model tokens used
163,798
Exact commit tested
1614dfa166f7
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.

- **Frontend server** (`vinext start` on port 4173): HTTP **200**, serves the full LiveAgent Studio…
- **Local gateway** (`local_gateway.py` on port 8785): Starts successfully
### Issues Encountered & Fixed
| Error | Fix | Time |
|---|---|---|
| Node.js v18.19.1 (required >=22.13.0) | Installed v22.23.5 via `n` with `N_PREFIX` in user space …
| `pip install` blocked by PEP 668 (externally-managed-environment) | Created Python venv with `pyt…
| Missing `pytest` | Installed via `pip install pytest` in venv | ~0.5 min |
| `sh` doesn't support `source` | Used `. venv/bin/activate` instead | ~0 min |
### One-time notes
- The `cgi` module deprecation warning in `local_gateway.py` (Python 3.13 slated) — non-functional,…
- No third-party API keys needed for the frontend build, test suite, or local gateway startup. Real…

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 12 minutes to install, slower than the median of the 83 comparable projects Argusic has measured.

Of the 84 ai-agent projects Argusic has installed and timed, LiveStream-Agent-Studio was the 62nd fastest to reach a running state, and 58 of 84 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.04
Argusic Runner1/3Runs with mocks92.000.76

Topics (from GitHub)

ai-agentdouyinlivestreamspeech-to-text

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/LiveStream-Agent-Studio.svg)](https://argusic.com/subject/livestream-agent-studio)

Questions

Does LiveStream-Agent-Studio run?
Yes. LiveStream-Agent-Studio runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test LiveStream-Agent-Studio?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1614dfa166f7. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test LiveStream-Agent-Studio?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does LiveStream-Agent-Studio take to install?
12 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 LiveStream-Agent-Studio need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing LiveStream-Agent-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 LiveStream-Agent-Studio compare with the alternatives?
Of the 84 ai-agent projects Argusic has installed and timed, LiveStream-Agent-Studio was the 62nd fastest to reach a running state, and 58 of 84 reached one at all.
Where is the evidence for LiveStream-Agent-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.

Discussion