xiaozhi-esp32-server
本项目为xiaozhi-esp32提供后端服务，帮助您快速搭建ESP32设备控制服务器。Backend service for xiaozhi-esp32, helps you quickly build an ESP32 device control server.
Runs with mockssource: GitHubhomepageJavaScriptMITcommit 788f5301fdd6
JavaScript, MIT licensed. The project labels itself: dify, esp32, mcp server, xiaozhi, xiaozhi ai, xiaozhi esp32 and xiaozhi server.
xiaozhi-esp32-server runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Python xiaozhi-server installs and runs on ports 8000/8003 with 59/64 pytest tests passing (5 skipped due to placeholder API keys), manager-web Vue UI installs and passes all 62 tests (9 contract + 53 unit), Java manager-api cannot be built (no JDK).
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
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.
- anyio pytest plugin conflicts with pytest-asyncio, causing AttributeError on async test collection1 minute
- Empty data/.config.yaml causes NoneType error when loader calls .get() on yaml.safe_load result1 minute
- Java 21 and Maven not installed; manager-api Java component cannot build
- Install time
- 7 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest tests/ returned 59 passed, npm test returned 9+53 passed, curl against OTA endpoint returned HTTP 200, curl against WS endpoint returned HTTP 200
- Model tokens used
- 191,450
- Exact commit tested
- 788f5301fdd6
- 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.
# fail 0
✓ tests/featureManager.test.mjs (7 tests) 6ms
✓ tests/date.test.mjs (15 tests) 7ms
✓ tests/deviceTime.test.mjs (22 tests) 25ms
✓ tests/format.test.mjs (9 tests) 6ms
Test Files 4 passed (4)
Tests 53 passed (53)
Duration 1.53s (transform 163ms, setup 0ms, collect 303ms, tests 44ms, environment 1.91s, prepa…
Everything is working. Here's the final report:
tokens used
191,450
Everything is working. Here's the final report: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 7 minutes.
- 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.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.04 |
Topics (from GitHub)
difyesp32mcp-serverxiaozhixiaozhi-aixiaozhi-esp32xiaozhi-server
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/xiaozhi-esp32-server)Questions
- Does xiaozhi-esp32-server run?
- xiaozhi-esp32-server runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test xiaozhi-esp32-server?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 788f5301fdd6. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test xiaozhi-esp32-server?
- 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 xiaozhi-esp32-server take to install?
- 7 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 xiaozhi-esp32-server need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing xiaozhi-esp32-server?
- 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.
- Where is the evidence for xiaozhi-esp32-server?
- 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.