danghuangshang

Open-source multi-agent collaboration system inspired by Chinese governance, deploy and coordinate specialized AI agents with OpenClaw.

Runssource: GitHubhomepageTypeScriptMITcommit acea185a9a1a

TypeScript, MIT licensed. The project labels itself: ai, ai agents, ai collaboration, ai court, ai orchestration, ancient china, autonomous agents and clawdbot.

danghuangshang runs. An Argusic agent installed it in 1 minute and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Project installs (npm install), 19 Jest tests pass, 11 manual unit tests pass, GUI Express server launches and responds on all 40+ authenticated API endpoints, and all project media files decode cleanly; the GUI frontend (React/Vite) cannot build due to Node v18 in the container vs required >=v20, but the server runs independently

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.03 (measured)
recorded runs
2
last tested
stars
2,719
forks
259
open issues
38
watchers
14
size
4 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 danghuangshang, 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.

  • Manual test test-context-compressor.js called non-existent APIs (compressConversation, estimateTokens, generateSummary) that were removed in v2.0.03 minutes
  • GUI frontend (React/Vite + @tailwindcss/oxide) build requires Node >=20.19.0 but container has Node v18.19.1
Install time
1 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm test exited 0, 19 passed across 2 suites; npm run test:manual exited 0 (7 task-store + 4 context-compressor tests); GUI server started on port 18795 and curl -H 'Authorization: Bearer testtoken123' http://localhost:18795/api/health returned 200 with {'status':'healthy','gateway':'connected','endpoints':41}; curl /api/system/metrics, /api/dashboard/summary, /api/status all returned valid JSON; all 7 PNG and 1 JPEG image files verified decode via ffmpeg -v error -i FILE -f null
Model tokens used
84,510
Exact commit tested
acea185a9a1a
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 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. 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.

exec
/bin/sh -lc 'cd /work/repo && echo "=== computing install minutes ===" && echo "start: $(date -d @0…
 succeeded in 0ms:
=== computing install minutes ===
start: Thu Jan  1 00:00:00 UTC 1970
I have all the data I need. Here's my report:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":1,"errors":…
2026-11-11T01:19:37.431011Z ERROR codex_core::session: failed to record rollout items: thread 01a1c…
tokens used
84,510
I have all the data I need. Here's my report:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":1,"errors":…

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 1 minute, faster than the median of the 234 comparable projects Argusic has measured.
  • Recovered from all 2 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 235 ai projects Argusic has installed and timed, danghuangshang was the 35th 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.
  • A quick evaluation: it was running 1 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.03
Argusic Runner1/3Runs with mocks92.000.04

Topics (from GitHub)

aiai-agentsai-collaborationai-courtai-orchestrationancient-chinaautonomous-agentsclawdbotdiscorddiscord-botimperial-chinaliu-bu-zhillmming-dynastymulti-agentopenclawsan-sheng-liu-busix-ministriestutorialworkflow-automation

Embed the badge

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

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

Questions

Does danghuangshang run?
Yes. danghuangshang runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test danghuangshang?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit acea185a9a1a. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test danghuangshang?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does danghuangshang take to install?
1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does danghuangshang need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing danghuangshang?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does danghuangshang compare with the alternatives?
Of the 235 ai projects Argusic has installed and timed, danghuangshang was the 35th fastest to reach a running state, and 166 of 235 reached one at all.
Where is the evidence for danghuangshang?
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